test-coverage
Skill0 starsChanged 2 months agoApache-2.0View on GitHub
Run the test-coverage-mapper reducer subagent over the per-node enrichment sidecars + actual test files in the target repo. Verifies sidecar-claimed test files exist; surfaces uncovered behaviours as TEST-GAP-NNN candidates ranked by node criticality (anchored on concepts.yaml's security/performance aggregates); cross-references with `doc-gaps.md` for double-jeopardy findings (undocumented AND untested). Emits `lineage/{repo}/test-map.yaml`.
20 other projects use a version of this.
Adopted by
Most recently taken up by
- luongnv89/skillstheir own version, first seen Nov 6, 2026
- cognitedata/builder-skillstheir own version, first seen Nov 4, 2026
- drvoss/everything-copilot-clitheir own version, first seen Oct 26, 2026
- vhmarquez/argotheir own version, first seen Oct 15, 2026
- manastalukdar/ai-devstudiotheir own version, first seen Oct 13, 2026
- my-chiefmind/ai-maestrotheir own version, first seen Oct 13, 2026
Used with
Projects with it also use instinct-export, instinct-import and 10 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.
TheKREATORSSkillinstinct-export
Export instincts from project/global scope to a file
Also in 3 projects that use this
TheKREATORSSkillinstinct-import
Import instincts from file or URL into project/global scope
Also in 3 projects that use this
diego-tobalinaSkillbuild-fix
Fix build and compilation errors systematically. Run when build fails.
Also in 3 projects that use this
qtzx06Skilleval
Evaluate trained YOLO model accuracy with mAP metrics and per-class error analysis. Identifies failure cases for targeted improvement. Use after training.
Also in 4 projects that use this
HABUBUSSSkilleval-harness
Also in 5 projects that use this
Microsoft AzureSkilliterative-retrieval
Max-3-cycle protocol for agent sub-tasks with WHY context and coordinator validation. Use when spawning sub-agents to complete scoped work.
Also in 3 projects that use this
- +1 more from TheKREATORS
Other versions20 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 20
- cloudposse/atmos★ 1.4ksame name
- wso2/product-apim★ 1ksame name
- LedgerHQ/ledger-live★ 627same name
- luongnv89/skills★ 145same name
- drvoss/everything-copilot-cli★ 49same name
- ariadoss/superskills★ 12same name
- Montimage/skills★ 9same name
- cognitedata/builder-skills★ 6same name
- my-chiefmind/ai-maestro★ 6same name
- kartik-nighania/av_claude_code_workshop★ 4same name
10 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 repository27 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- alignSkill
- code-walkSkill
- conceptsSkill
- contributeSkill
- coverageSkill
- doc-gap-checkSkill
- enrichSkill
- enumerateSkill
- find-implicit-adrsSkill
- implementSkill
- ingest-docsSkill
- log-issueSkill
- navigateSkill
- next-batchSkill
- orientSkill
- panelSkill
- probe-defineSkill
- probe-runSkill
- probeSkill
- reflect-featureSkill
- retrieveSkill
- reviewSkill
- scanSkill
- statusSkill
- streamsSkill
- triageSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 2 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Run the test-coverage-mapper reducer to map node behaviours to test files (verifying every sidecar's test_files claim) and surface …
- Very specific: line 25
Before spawning the subagent in default (incremental) mode, the skill computes:
- Very specific: line 54
Test files: Glob per language conventions:
- Distinctive: line 83
Verify per_node, test_gaps, cross_cutting_patterns, sidecar_quality_findings sections.
- Distinctive: line 98
Verify every test_files claim: Every cited test path is Glob-checked.
- Very specific: line 100
Don't invent gaps: Every TEST-GAP-NNN traces to a sidecar's uncovered_behaviours entry.
- Very specific: line 101
Surface sidecar-quality findings separately: When a sidecar's test_files claim doesn't verify, that's a refresh signal — file in …
“Common” is measured: kept by at least 6 in 10 of the 19 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
Test coverage map (DOC-164 slice 8+)
Run the test-coverage-mapper reducer to map node behaviours to test files (verifying every sidecar's test_files claim) and surface uncovered behaviours as TEST-GAP-NNN candidates the maintainer triages when the tests pillar activates.
This is the fourth reducer in the agentic-code-ontology layer. The reducer runs alongside (or after) /find-implicit-adrs in slice 8.
Argument forms
| Form | Behaviour |
/test-coverage [<repo>] | Default. Run test-coverage-mapper in incremental mode (per playbooks/reducer-incremental-mode.md). Refreshes lineage/{repo}/test-map.yaml by appending+annotating only the sidecars whose node_id is not yet in the prior artefact's processed_node_ids. Required-default after the 2026-05-12 batch-F stream-idle-timeout (lineage/odd-platform/investigator-log.md:14-16) where the reducer's full-mode run on 7103-line prior test-map exhausted session budget. |
/test-coverage --full [<repo>] | Forces FULL mode — re-reads every sidecar and re-indexes every test file. High token cost; use only when prior map is corrupt. |
/test-coverage --show [<repo>] | Read-only. Print summary (counts per criticality + category, top-5 CRITICAL test gaps). |
/test-coverage --diff [<repo>] | Read-only. Compare existing map to a fresh run; surface the diff. |
Incremental input resolution
Before spawning the subagent in default (incremental) mode, the skill computes:
PROCESSED_NODE_IDS— read from priortest-map.yaml's frontmatterprocessed_node_ids:. Missing →--fullfallback.NEW_SIDECAR_FILES— sidecars whosenode_idis not inPROCESSED_NODE_IDS. Empty set → exit.PRIOR_HEAD— one line per existingTEST-GAP-NNNfrom priortest-map.yaml, derived via grepgap_id: TEST-GAP-+ criticality + category. Compact-head shape per the playbook.CURATED_ENTRIES— verbatim YAML of every entry flaggedmaintainer_curated: true.NEXT_AVAILABLE_ID— max existingTEST-GAP-NNN+ 1.EXISTING_SIDECAR_QUALITY_FINDINGS— verbatim from prior artefact'ssidecar_quality_findings:section; carried forward unchanged.
These get passed to the subagent in place of the legacy "full prior artefact" block.
Prerequisites
lineage/{repo}/understanding/{slug}.mdsidecars exist.lineage/{repo}/concepts.yamlexists — the reducer needs concept-level security/performance aggregates to anchor test-gap criticality.- Target repo's test files reachable (e.g.
../odd-platform/odd-platform-api/src/test/**/*.java).
Protocol
1. Orient
CLAUDE.md— quality baradrs/drafts/agentic-code-ontology.md— slice 8.claude/agents/test-coverage-mapper.md— subagent system prompt
2. Resolve inputs
- Sidecar set:
Globlineage/{repo}/understanding/*.md. - Concepts catalog: read
lineage/{repo}/concepts.yaml. - Test files:
Globper language conventions:- Java:
{repo_root}/odd-platform-api/src/test/**/*.java - TS:
{repo_root}/odd-platform-ui/**/*.{test,spec}.{ts,tsx} - Python:
{repo_root}/**/test_*.py+{repo_root}/**/*_test.py
- Java:
- Existing test-map: capture maintainer-curated entries.
- doc-gaps.md (optional): for double-jeopardy cross-reference.
3. Spawn the test-coverage-mapper subagent
Invoke via Agent tool. Construct the prompt:
REPO: <repo>
WORKSPACE_ROOT_ABS: <absolute>
REPO_ROOT_ABS: <absolute path to ../{repo}>
SIDECAR_DIR_ABS: /home/.../lineage/{repo}/understanding/
CONCEPTS_YAML_PATH: /home/.../lineage/{repo}/concepts.yaml
DOC_GAPS_PATH: /home/.../lineage/{repo}/doc-gaps.md # optional
EXISTING_TEST_MAP: <verbatim or "(none)">
SUBSTRATE_LAST_SCAN_COMMIT: <from manifest.yaml>
TARGET_PATH: lineage/{repo}/test-map.yaml
SIDECAR_COUNT: <N>Tools per frontmatter: Read, Glob, Grep, Write. Subagent verifies test_files claims, ranks gaps by criticality, and writes the map.
4. Validate
- Confirm
test-map.yamlexists; parse YAML. - Verify per_node, test_gaps, cross_cutting_patterns, sidecar_quality_findings sections.
- Spot-check 3-5 verified test_files entries — do they actually exist and contain the cited test name?
5. Report
- Report path
- Counts:
<C> CRITICAL / <H> HIGH / <M> MEDIUM / <L> LOW = <N> total test gaps - Categories: missing-unit / missing-integration / missing-edge-case / missing-security / missing-performance / sidecar-stale
- Top-5 CRITICAL test gaps (one-liners with gap IDs)
- Cross-cutting patterns count (e.g. "no integration tests exist anywhere")
- Sidecar-quality findings count (test_files claims that didn't verify)
- Double-jeopardy count (gaps that are both untested AND undocumented per doc-gaps.md)
Rules
- Verify every test_files claim. Every cited test path is Glob-checked; every cited test name is Grep-checked.
- Anchor criticality on concepts.yaml. A test gap on a node tied to a HIGH-security-aggregate concept is CRITICAL. Don't guess.
- Don't invent gaps. Every TEST-GAP-NNN traces to a sidecar's
uncovered_behavioursentry. - Surface sidecar-quality findings separately. When a sidecar's
test_filesclaim doesn't verify, that's a refresh signal — file insidecar_quality_findings, not as a test gap.
Cross-references
- Subagent:
.claude/agents/test-coverage-mapper.md - Inputs: sidecars + concepts.yaml + (optional) doc-gaps.md + actual test files
- Output:
lineage/{repo}/test-map.yaml - Future tests-pillar consumer: when
pillars/tests/activates, the TEST-GAP-NNN list seeds the pillar's backlog.
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.

