deep-test
Skill3 starsChanged 4 months agoApache-2.0View on GitHub
Perform a deep test of the codebase, validating functional smoke tests, claim verification, drift checks, license headers, and placeholder checks. Trigger whenever the user asks to run deep tests, check code health, or perform strict verification.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- oguzsabi/deep-skillstheir own version, first seen Nov 1, 2026
- BryanBerger98/claude-skillstheir own version, first seen Jul 17, 2026
- Deep-Process/deep-processtheir own version, first seen Mar 8, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- Deep-Process/deep-process★ 2same name
- BryanBerger98/claude-skills★ 1same name
- oguzsabi/deep-skills★ 1same name
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 repository32 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/add-feature.mdcCursor rule
- .cursor/rules/adversarial-audit.mdcCursor rule
- .cursor/rules/ai-knowledge-layer.mdcCursor rule
- .cursor/rules/check-drift.mdcCursor rule
- .cursor/rules/cold-start.mdcCursor rule
- .cursor/rules/create-feature-catalog.mdcCursor rule
- .cursor/rules/fix-bug.mdcCursor rule
- .cursor/rules/perform-feature-add-simulation.mdcCursor rule
- .cursor/rules/post-cold-start-verification.mdcCursor rule
- .cursor/rules/review-agent-config.mdcCursor rule
- .cursor/rules/review-change.mdcCursor rule
- .cursor/rules/verify-ai-readiness.mdcCursor rule
- add-featureSkill
- cold-startSkill
- fix-bugSkill
- review-changeSkill
- add-featureSkill
- adversarial-auditSkill
- check-docsSkill
- check-driftSkill
- cold-startSkill
- create-feature-catalogSkill
- fix-bugSkill
- implement-specSkill
- perform-feature-add-simulationSkill
- post-cold-start-verificationSkill
- review-agent-configSkill
- review-changeSkill
- verify-ai-readinessSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Ensure you have the required runtimes and node dependencies installed:
- Very specific: line 14
Run npm install before running tests if dependencies are updated.
- Distinctive: line 17
Run the automated deep test script via npm:
- Very specific: line 25
Document Claim verification: node install.mjs verify .
- Distinctive: line 30
If any of the checks fail, print the failures verbatim and address them before declaring success.
- Very specific: line 33
If you introduced new files, check that their paths are added to the appropriate catalog or map (e.g., ai/guide/MODULE_MAP.md) and labeled …
- Very specific: line 34
Verify the change adheres to all project rules in AGENTS.md and conventions in ai/guide/CONVENTIONS.md.
“Common” is measured: kept by at least 6 in 10 of the 3 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
<!-- Copyright (c) 2026 Kunal Suri (CEA LIST). All rights reserved. -->Deep test the codebase
This skill performs a thorough and strict verification of the codebase to guarantee that changes are clean, functional, matches Conventions, contains proper license headers, and does not leak template placeholders.
1. Prerequisites
Ensure you have the required runtimes and node dependencies installed:
- Node.js (>= 18)
- Run
npm installbefore running tests if dependencies are updated.
2. Run the Deep Test
Run the automated deep test script via npm:
npm run deep-test3. Verify Output
The script automatically tests:
- Smoke tests:
node test/run-tests.mjs - Document Claim verification:
node install.mjs verify . --strict - Structural Drift verification:
node install.mjs drift . --strict --git(falls back to--strictwithout--gitif git is not available) - License Headers check: Scans files for copyright markers.
- Unresolved template placeholders: Confirms template variables are not leaked outside of
templates/.
If any of the checks fail, print the failures verbatim and address them before declaring success.
4. Manual Verification / Check Checklist
- If you introduced new files, check that their paths are added to the appropriate catalog or map (e.g.,
ai/guide/MODULE_MAP.md) and labeled as[inferred]. - Verify the change adheres to all project rules in
AGENTS.mdand conventions inai/guide/CONVENTIONS.md.
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.

