AGENT SKILL

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

  1. Read AGENTS.md, then reproduce with the narrowest recipe rather than the whole gate. just check names the recipe that failed; run that one alone.
  2. Dispatch on which gate failed:
    • fmt-check or toml-check — run just 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 in Cargo.toml with a comment saying why, never disabled at the call site with allow.
    • features or wasm-check — a std path, or a feature that does not compile alone. The fix is cfg, core and alloc; a target is never dropped.
    • coverage below the floor — add the missing test. Never lower coverage_floor in the Justfile.
    • doc — a missing doc comment or a broken intra-doc link; missing_docs is on and warnings are errors there.
    • deny or deps-unused — a licence, a ban or an unused dependency; a new dependency is a decision recorded per decision 0007, and just fix runs cargo shear --fix.
    • check-docs — a frontmatter list that disagrees with docs/manifest.yml is 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-specs or analyse-specs — hand to the spec-change skill; a diagnostic is a regression and a finding cannot be waived.
    • lock-check — run just lock, and read the lockfile diff before accepting it.
  3. Distinguish an unreachable branch from an untested one. Defensive code no input can reach should be removed, not covered by a contrived test.
  4. Never disable a gate to make a run green. A suppression is a last resort: one rule, one line, with a stated reason.
  5. If a recipe changed the worktree, that is a defect in the recipe — checks are read-only. Fix the recipe.
  6. Run the narrow recipe, then just check to confirm nothing else moved.

04 同仓库更多 Skills

steven-cutting
steven-cutting/libpawdoku

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.

★ 0
steven-cutting
steven-cutting/libpawdoku

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.

★ 0
steven-cutting
steven-cutting/libpawdoku

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.

★ 0
steven-cutting
steven-cutting/libpawdoku

spec-change

Change an Allium specification and carry the change through the tests and the implementation.

★ 0
steven-cutting
steven-cutting/libpawdoku

rust-change

Implement or review a change to the engine with the trait boundary, no_std, tests and documentation evidence the invariants require.

★ 0
steven-cutting
steven-cutting/libpawdoku

review-docs

Add or revise a handbook page so it satisfies the documentation contract and stays reachable.

★ 0