Best for
- Use when goal policy enables change_quality_qualification, before a non-trivial delivery or merge, and when producing or repairing an exact-scope quality receipt.
huangruiteng/loopx/skills/loopx-change-quality/SKILL.md
Qualify the exact final diff for a LoopX-managed goal. Use when goal policy enables change_quality_qualification, before a non-trivial delivery or merge, and when producing or repairing an exact-scope quality receipt. The workflow is language-neutral, permits at most one policy-authorized safe-fix pass, and never grants merge or repository authority.
Decision brief
Use this skill only when the selected goal's changequalityqualification.enabled policy is true. LoopX owns the canonical source but does not install it globally. Install a managed copy in a connected project for the relevant host:
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/huangruiteng/loopx --skill "skills/loopx-change-quality"Inspect the Agent Skill "loopx-change-quality" from https://github.com/huangruiteng/loopx/blob/9bfbaa1a9aa32c9b92d85d798ebaa5a8290ff023/skills/loopx-change-quality/SKILL.md at commit 9bfbaa1a9aa32c9b92d85d798ebaa5a8290ff023. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
Review the “Review Rules” section in the pinned source before continuing.
From the repository worktree, run:
Spend the review budget on simplification before broad quality analysis:
safefix and strictreceipt are independent:
Write a compact result conforming to the packet's changequalityagentresultv2 template. Beyond exact-scope metadata, the Agent writes only reuse, simplification, sparse risks[], and validation[]. simplification.safefixapplied records the one permitted repair pass. A skipped or fa…
Permission review
The documentation asks the agent to read local files, directories, or repositories.
Read repository-local instructions before judging the change.Evidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 86/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 2,386 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Use this skill only when the selected goal's
change_quality_qualification.enabled policy is true. LoopX owns the canonical
source but does not install it globally. Install a managed copy in a connected
project for the relevant host:
loopx project-skill install \
--project . \
--skill loopx-change-quality \
--surface codex \
--execute
Use --surface claude-code or --surface opencode for those hosts. Skill
discovery does not activate the capability; product behavior remains
default-off until goal policy enables it.
The CLI is the contract authority. This skill supplies a host-neutral review workflow. Repository instructions, tests, linters, type checkers, and security checks remain the project's quality oracles.
From the repository worktree, run:
loopx --format json change-quality prepare \
--goal-id <goal-id> \
--repo-path . \
--base-ref origin/main
Stop when the packet says disabled or no_changes. When it says
review_required, review only the files and exact fingerprint in the packet.
Read repository-local instructions before judging the change.
Run loopx project-skill status --project . --skill loopx-change-quality when
the host depends on skill discovery. If the managed copy is absent or stale,
preview an explicit project install; do not fall back to a global copy.
Spend the review budget on simplification before broad quality analysis:
Write one evidence-backed reuse conclusion and one evidence-backed
simplification conclusion. Do not emit a row for every remaining lens.
Those dimensions are guardrail categories for sparse risks[]: add an item
only when the changed surface, repository instructions, a native validator, or
the proposed simplification raises a concrete risk. LoopX derives each
guardrail's status from risks[] and validation[].
The available review lenses are:
The packet projects path-only references to applicable repository instructions,
ownership files, build manifests, language hints, and changed surface roots.
It also projects a provider-neutral validation plan discovered from structured
repository task declarations. This is discovery context, not copied repository
content: instruction text, task bodies, and manifest contents remain in the
worktree. Read every required_reads entry, inspect each candidate's
source_ref, and let the host resolve the named Poe, Hatch, Cargo, or package
task. Never execute a candidate merely because it was discovered. Unresolved
format, lint, typecheck, or test categories require reviewer judgment or a
repository-native instruction; do not fill them with guessed commands. Treat
ignored_manifest_refs as non-executable context, especially fixtures and
vendored projects.
Read every projected instruction reference, but do not copy its prose into the
result. Ground reuse, simplification, and each emitted risk with typed
evidence_refs using path:, instruction:, or validator:. Keep
risks[] empty when no guardrail is triggered. Record only validators that
were selected or required; failed validation and skipped required validation
are independently blocking.
Use blocker only for a concrete correctness, security, privacy, contract, or
required-validation failure. Style preferences and speculative redesigns are
warning or advisory, never blockers.
This first version is single-level. Review one final diff; do not recursively review the review, spawn a hierarchy of quality agents, or require agreement between several models.
The guardrail catalog is review guidance, not an Agent output checklist or evidence that a particular model applies it well. Maintainers qualify model behavior separately against the public clean-PR and seeded Python, Rust, and TypeScript shadow matrix. Normal delivery does not launch that low-frequency evaluation, and a model shadow result cannot mutate goal policy or grant merge authority.
safe_fix and strict_receipt are independent:
safe_fix=true permits at most one bounded repair pass.strict_receipt=true requires exact-scope evidence before merge and grants
no permission to edit.When safe_fix is false, report risks without modifying files. When it is
true, one repair pass may address a clear simplify opportunity or risk inside
the selected todo and goal boundary. Do not use destructive git, broaden
permissions, change product intent, add unrelated refactors, or conceal a
failing validator.
After any edit, rerun prepare. The old fingerprint is invalid. Review the
entire new final scope, not only the lines changed by the repair.
Write a compact result conforming to the packet's
change_quality_agent_result_v2 template. Beyond exact-scope metadata, the
Agent writes only reuse, simplification, sparse risks[], and
validation[]. simplification.safe_fix_applied records the one permitted
repair pass. A skipped or failed validator needs a reason; failed validation or
skipped required validation makes the receipt non-passing. Keep raw
transcripts, private paths, credentials, and unbounded logs out of the result.
Then record and read back the exact receipt:
loopx --format json change-quality record \
--goal-id <goal-id> \
--repo-path . \
--base-ref origin/main \
--result-json <ignored-or-temporary-result.json> \
--execute
loopx --format json change-quality verify \
--goal-id <goal-id> \
--repo-path . \
--base-ref origin/main
A receipt with an unresolved blocker, failed validator, or skipped required validator is not passing. A receipt for an earlier fingerprint does not qualify a later diff. Earlier experimental receipt schemas are invalid and must be requalified with the current protocol.
Run the authoritative merge gate with the goal identity:
loopx canary premerge \
--from-git-diff \
--goal-id <goal-id>
Turn may transport the prepare packet or receipt reference as part of one
bounded transaction. Turn does not own quality policy and may not manufacture
or waive a receipt. canary premerge remains the enforcement authority.
Report:
Stop before delivery when strict policy requires a receipt and the receipt is missing, invalid, stale, or contains an unresolved blocker.
Alternatives
alirezarezvani/claude-skills
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist
prowler-cloud/prowler
PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing index usage statistics, reindexing, dropping indexes, or working with partitioned table indexes. Also trigger when discussing index strategies, partial indexes, or index maintenance
wanshuiyin/Auto-claude-code-research-in-sleep
Use it for operations and research tasks; the detail page covers purpose, installation, and practical steps.
dotnet/skills
Migrates .NET test projects from VSTest to Microsoft.Testing.Platform (MTP). Use when user asks to "migrate to MTP", "switch from VSTest", "enable Microsoft.Testing.Platform", "use MTP runner", set OutputType=Exe only for test projects in Directory.Build.props, or mentions EnableMSTestRunner, EnableNUnitRunner, or UseMicrosoftTestingPlatformRunner. USE FOR: MTP behavioral differences vs VSTest (exit code 8, zero tests discovered, --ignore-exit-code, TESTINGPLATFORM_EXITCODE_IGNORE); centralizing