agentleFS
kunalsurikunalsuri/ai-fication-kit/.agents/skills/deep-test/SKILL.md

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

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
  1. Distinctive:

    Ensure you have the required runtimes and node dependencies installed:

    line 12
  2. Very specific:

    Run npm install before running tests if dependencies are updated.

    line 14
  3. Distinctive:

    Run the automated deep test script via npm:

    line 17
  4. Very specific:

    Document Claim verification: node install.mjs verify .

    line 25
  5. Distinctive:

    If any of the checks fail, print the failures verbatim and address them before declaring success.

    line 30
  6. Very specific:

    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 …

    line 33
  7. Very specific:

    Verify the change adheres to all project rules in AGENTS.md and conventions in ai/guide/CONVENTIONS.md.

    line 34

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- 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 install before running tests if dependencies are updated.

2. Run the Deep Test

Run the automated deep test script via npm:

npm run deep-test

3. 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 --strict without --git if 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.md and conventions in ai/guide/CONVENTIONS.md.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.