fix-quality
Diagnose and repair a failing quality gate at its root instead of suppressing the finding.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-10
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- fix-quality
- description
- Diagnose and repair a failing quality gate at its root instead of suppressing the finding.
03 SKILL.md 正文
Fix a failing gate
- Read
AGENTS.md, then reproduce with the narrowest recipe rather than the whole gate.just checknames the recipe that failed; run that one alone. - Dispatch on which gate failed:
fmt-checkortoml-check— runjust fix; never hand-format to match.clippy— fix the code. A lint that is wrong for one item gets#[expect(lint, reason = "...")]on that item; a lint that is wrong for the crate is changed in the workspace lint table inCargo.tomlwith a comment saying why, never disabled at the call site withallow.featuresorwasm-check— astdpath, or a feature that does not compile alone. The fix iscfg,coreandalloc; a target is never dropped.coveragebelow the floor — add the missing test. Never lowercoverage_floorin theJustfile.doc— a missing doc comment or a broken intra-doc link;missing_docsis on and warnings are errors there.denyordeps-unused— a licence, a ban or an unused dependency; a new dependency is a decision recorded per decision 0007, andjust fixrunscargo shear --fix.check-docs— a frontmatter list that disagrees withdocs/manifest.ymlis usually list order; the comparison is order-sensitive.check-agents— a bridge under.claude/or.codex/has grown content, or a managed file is missing from the inventory.check-specsoranalyse-specs— hand to thespec-changeskill; a diagnostic is a regression and a finding cannot be waived.lock-check— runjust lock, and read the lockfile diff before accepting it.
- Distinguish an unreachable branch from an untested one. Defensive code no input can reach should be removed, not covered by a contrived test.
- Never disable a gate to make a run green. A suppression is a last resort: one rule, one line, with a stated reason.
- If a recipe changed the worktree, that is a defect in the recipe — checks are read-only. Fix the recipe.
- Run the narrow recipe, then
just checkto confirm nothing else moved.
04 同仓库更多 Skills
witness
Independently witness that an Allium loop's convergence claim is true and was reached honestly. Use when the user wants to verify a loop's self-report, confirm tests really pass and no generated test was weakened, produce a convergence certificate or witness record, gate CI on a trustworthy signal, or check that an autonomous run did not cheat its way to green.
weed
Weed the Allium garden. Find where Allium specifications and implementation code have diverged, and help resolve the divergences. Use when the user wants to check spec-code alignment, compare specs against implementation, audit for spec drift or violations, sync specs with code or code with specs, or verify whether the implementation matches what the spec says.
tend
Tend the Allium garden. Use when the user wants to write, edit, update, add to, improve, clarify, refine, restructure, fix or migrate Allium specs. Covers adding entities, rules, triggers, surfaces and contracts, fixing syntax or validation errors, renaming or refactoring within specs, migrating specs to a new language version, and translating requirements into well-formed specifications. Pushes back on vague requirements.
spec-change
Change an Allium specification and carry the change through the tests and the implementation.
rust-change
Implement or review a change to the engine with the trait boundary, no_std, tests and documentation evidence the invariants require.
review-docs
Add or revise a handbook page so it satisfies the documentation contract and stays reachable.