How do I install the Deep Test skill?

Run npx skillmds@latest add kunalsuri/deep-test in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Deep Test safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Deep Test?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Deep Test free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Deep Test?

kunalsuri (@kunalsuri) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Deep Test by kunalsuri — Agent Skill

Name: Deep Test
Author: kunalsuri

Deep Test

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.

kunalsuri 6b2ad54 1.7 KB Updated Sep 17, 2026

File contents

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.

Frequently asked questions