quality
Skill0 starsChanged 7 days agoMITView on GitHub
Use for the QA quality pass of a loops run, or whenever measuring changed code for CRAP (complexity x coverage), structural duplication or mutation-test survivors - runs crapper, dryer and mutator (or the pack's native mutation tool), maps each finding to its owning lane, and writes qa/quality.r<N>.md.
14 other projects use a version of this.
Adopted by
Most recently taken up by
- qualitymd/quality.mdtheir own version, first seen Nov 15, 2026
- ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tooltheir own version, first seen Nov 8, 2026
- menot-you/n-soultheir own version, first seen Nov 1, 2026
- ansvisor/ansvisortheir own version, first seen Nov 1, 2026
- DataWithBaraa/claude-code-data-engineering-skillstheir own version, first seen Nov 1, 2026
- tam159/next-roletheir own version, first seen Nov 1, 2026
Used with
Projects with it also use tasks, analyze and 3 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
genomewalkerSkilltasks
Browse and resume tasks, threads, and background jobs across sessions
Also in 3 projects that use this
AnthropicSkillanalyze
Answer data questions -- from quick lookups to full analyses. Use when looking up a single metric, investigating what's driving a trend or drop, comparing segments over time, or preparing a formal data report for stakeholders.
Also in 3 projects that use this
AnthropicSkilldebug
Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.
Also in 4 projects that use this
SentrySkillreview
Fixture review skill.
Also in 5 projects that use this
BlockSkillplan
Draft a TDD, PRD, or lightweight plan in the conversation without committing it.
Also in 3 projects that use this
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- google-gemini/gemini-cli★ 109ksame name
- H-mmer/pentest-agents★ 815same name
- boostsecurityio/poutine★ 533same name
- ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool★ 432same name
- ansvisor/ansvisor★ 241same name
- DataWithBaraa/claude-code-data-engineering-skills★ 84same name
- tam159/next-role★ 67same name
- qualitymd/quality.md★ 33same name
- ariaxhan/kernel-claude★ 15same name
- stevehansen/eidet★ 4same name
4 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository35 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- skills/work/platforms/claude.mdCLAUDE.md
- llms.txtllms.txt
- clarifySkill
- consistencySkill
- debuggingSkill
- documentationSkill
- featureSkill
- hexagonalSkill
- initSkill
- jobs-and-state-machinesSkill
- lang-clojureSkill
- lang-cppSkill
- lang-csharpSkill
- lang-elixirSkill
- lang-erlangSkill
- lang-goSkill
- lang-javaSkill
- lang-kotlinSkill
- lang-phpSkill
- lang-pythonSkill
- lang-rubySkill
- lang-rustSkill
- lang-scalaSkill
- lang-swiftSkill
- lang-typescriptSkill
- memorySkill
- parallel-workSkill
- performanceSkill
- reportSkill
- review-integrationSkill
- statusSkill
- testingSkill
- workSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Detect: Run command -v crapper dryer mutator.
- Very specific: line 48
Never delete target/mutator-backup/.
- Very specific: line 51
Write <Run dir>/qa/quality.r<N>.md from templates/QUALITY.md, at most 500 words excluding output excerpts of up to 20 lines.
- Distinctive: line 64
After the fixes, the same verifier re-runs the pass (round N+1).
“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Quality pass
The rules and bars are specs/ENGINEERING.md §12-§14; the place in the run is specs/WORKFLOW.md §2.4. This skill is the how-to. One qa-verifier runs it as Agent id qa-quality, once per QA round, after every lane is VERIFIED and before the full gate. A single pass sees duplication across lanes, and it keeps parallel runs from overwriting one another's .metrics/ output.
Load
research/language.json(the packs and their roots), the plan's waves table (each lane'sOwnsglobs), and the reports inreports/.loops:lang-<id>for each pack: itstesting.mdnames the native mutation tool, if any.
Tools
crapper, dryer and mutator cover Clojure, Java, Go, TypeScript, Rust and Python.
- Best-effort. They are young, single-maintainer projects. A tool that fails to run is recorded as such and never patched in place (Go:
specs/languages/go/RULES.md§57). - Install. Each is a checkout whose launcher creates its own
.venvon first use. Clone them side by side (mutator reads../crapper), and put each checkout directory onPATH. A symlink to the launcher breaks its.venvlookup. - Detect. Run
command -v crapper dryer mutator. A missing tool is recorded asnot installed: <tool> (install: git clone https://github.com/unclebob/<tool>)and does not block. - Run in the run's environment:
loops exec --pack <id> -- <tool> …. The tools run the project's tests and coverage, andloops execgives them the run's caches and tmp dir, never the user's. Name the pack explicitly: these tools belong to no pack, so without--packthey would run with the user's own caches. In a repo with several packs, run each tool once per pack, on that pack's changed files.
Other packs: use the project's configured native tool from skills/lang-<id>/testing.md (PIT, Stryker, Stryker.NET, cargo-mutants, mutant, Infection, Mull). Never add one to the project here: the <id>-engineer owns tool config. With no tool, record review only and apply the hollow-test rule (ENGINEERING §12) by reading the changed tests.
Lint and security are not here. Lint runs in per-lane QA (the pack's lint checks; Go: vet, staticcheck). Security tools run in the security pass (agents/security-reviewer.md).
Scope
The run's changed source files: tracked and untracked changes against the run's base. That is the set git status --porcelain shows while the run is uncommitted (loops' default), so the tools' --changed selects it. Otherwise pass the files explicitly. Test files, generated files and the pack's coverage.exclude are out of scope. Only functions the run added or changed are blocking. Read their line ranges from git diff -U0. Findings in other functions of the same files are notes.
Steps
- CRAP. Run
loops exec --pack <id> -- crapper --changed.- It regenerates coverage, prints a table (worst first) and writes
.metrics/crap.edn. - A changed function with CRAP ≥ 10 is a finding. Fix direction: split it, test the untested branches, or both.
- A flat dispatch (
switch,case,matchover cases) may stay above the bar when the owner states why. The finding then becomes a note.
- It regenerates coverage, prints a table (worst first) and writes
- Duplication. Run
loops exec --pack <id> -- dryer --changed --threshold 0.8.- It exits 0 after a report, so read the report.
- A pair with similarity ≥ 0.8 where at least one side is changed code is a finding. Fix direction: one place for the decision (ENGINEERING §1).
- A pair that crosses lanes goes to the lane whose code is newer. If both are new, it goes to the producer lane (the earlier wave).
- Mutation. Run
loops exec --pack <id> -- mutator --changed --max-workers <max_concurrent_test_runs from research/hardware.json>.- Exit 0: every executed mutant was killed. Exit 3: a mutant survived. Exit 2: the baseline tests fail, which goes to the lead as a gate failure, not a quality finding.
- Per changed function:
- survived: a finding. Name the mutation, for example
> → >=atfile:line, and the missing assertion. - uncovered: a finding: no test reaches that line.
- unreachable: code nothing calls and no test can reach is dead. Delete it.
- survived: a finding. Name the mutation, for example
- Later rounds are differential: mutator reruns survivors and changed functions only.
- Never delete
target/mutator-backup/. The next run restores from it.
- Native tools (other packs): run the configured goal scoped to the changed classes or modules, and read its report the same way.
- Map each finding to its lane with the plan's
Ownsglobs, the same lookup as a gate failure (skills/work§4, step 7). Write
<Run dir>/qa/quality.r<N>.mdfromtemplates/QUALITY.md, at most 500 words excluding output excerpts of up to 20 lines. Each finding isQ<n>with these fields:file:line;- the function;
- the lane;
- the metric and its value;
- the fix direction.
Then list the notes, the tools that did not run and why, and the verdict.
Verdict
VERIFIEDwhen there are no findings. It is alsoVERIFIEDwhen no tool could run; the file then says so, and the reflection notes it.- Otherwise
FAILED. The lead recordsloops run verdict --name quality:Q<n> --status FAILED --round N --ref qa/quality.r<N>.mdand sends each lane its findings (loopback --from qa-quality --to <id>). - After the fixes, the same verifier re-runs the pass (round N+1).
- The loop limits of WORKFLOW §4 apply, and so does ENGINEERING §11 when a finding survives two rounds.
Outputs and cleanup
The tools write .metrics/ (the crapper and mutator snapshots, which uml-viewer reads) and target/coverage/. For the six packs these are pack artifacts, so loops run end removes them when the run created them. They are never committed. Do not write anything else in the repo.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

