add-test
Skill1 starsChanged 24 days agoApache-2.0View on GitHub
Add or improve tests for requested code or meaningful coverage gaps.
18 other projects use a version of this.
Adopted by
Most recently taken up by
- microsoft/veronatheir own version, first seen Nov 8, 2026
- flavien-ia/hypervibe-crafttheir own version, first seen Oct 25, 2026
- flavien-ia/hypervibe-harnesstheir own version, first seen Oct 23, 2026
- WhatIfWeDigDeeper/claude-code-courseratheir own version, first seen Oct 20, 2026
- nativewind/react-native-csstheir own version, first seen Oct 9, 2026
- osmandapp/webtheir own version, first seen Oct 9, 2026
Used with
Projects with it also use review-pr, triage and 1 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.
DockerSkillreview-pr
Review one or more incoming Docker documentation pull requests as a maintainer. Independently validate technical claims, assess editorial fit and information architecture, choose a verdict, and draft exact inline or PR-wide feedback behind a confirmation gate. Use for requests such as "review PR 123", "is this PR correct?", "does this information belong here?", "validate this PR", or "help review backlog PRs". Do not use to maintain or fix a PR you own; use maintain-pr for that.
Also in 3 projects that use this
Google CloudSkilltriage
Gather context on a change or bug and plan the implementation.
Also in 3 projects that use this
SentrySkillreview
Fixture review skill.
Also in 3 projects that use this
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- gitkraken/vscode-gitlens★ 10ksame name
- nativewind/nativewind★ 8.1ksame name
- microsoft/verona★ 3.7ksame name
- The-OpenROAD-Project/OpenROAD★ 3.3ksame name
- OpenAEV-Platform/openaev★ 1.8ksame name
- DexForce/EmbodiChain★ 240same name
- fpindej/netrock★ 234same name
- nativewind/react-native-css★ 167same name
- osmandapp/web★ 63same name
- flavien-ia/hypervibe-craft★ 50same name
8 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 repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- audit-fixissuesSkill
- autoresearchSkill
- benchmark-optimizeSkill
- circleci-job-resultsSkill
- citation-verifierSkill
- cli-designSkill
- codebase-auditSkill
- code-cleanupSkill
- deep-code-cleanupSkill
- doc-updateSkill
- emendSkill
- fix-issueSkill
- git-github-workflowSkill
- goal-modeSkill
- inspect-datasetSkill
- manage-pr-lifecycleSkill
- medcognetics-brandSkill
- notify-wakeSkill
- repo-maintenanceSkill
- review-fix-loopSkill
- standardize-ciSkill
- token-file-authSkill
- whats-nextSkill
- yeetSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 17 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Use existing fixtures and test utilities.
- Distinctive: line 19
Run affected tests and applicable repository gates.
“Common” is measured: kept by at least 6 in 10 of the 17 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
Add Test Coverage
Accept $add-test with optional paths or functions. Use explicit targets first,
then changed files. With neither, choose a concrete gap in critical or bug-prone
behavior. Report a no-op when no useful gap exists.
Preserve production behavior. Production changes require scope that includes them. Continue independent test work if another target needs a scope decision.
Use existing fixtures and test utilities. Cover observable behavior, failure modes, and boundaries that existing assertions miss. Avoid tests that merely repeat the implementation or add unstable timing and network dependencies.
Run affected tests and applicable repository gates. For a reported bug, confirm the regression fails on the baseline before fixing it. Characterization tests for correct behavior should pass before and after a refactor.
Report the coverage gained, validation results, and any remaining gap.
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.