deep-test

Run end-to-end quality gates and verify spec compliance from test receipts.

10|1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/Sungmin-Cho/claude-deep-work --skill deep-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-test
Source: https://github.com/Sungmin-Cho/claude-deep-work/tree/main/skills/deep-test
Command: npx skills add https://github.com/Sungmin-Cho/claude-deep-work --skill deep-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep-test enforces rigorous, evidence-driven verification of implemented slices by running end-to-end test and quality gates, detecting design drift, and ensuring receipts demonstrate spec compliance so that delivered changes meet project expectations without premature completion claims.

Core Features & Use Cases

  • Receipt completeness checks: Verifies every slice has a complete receipt and passing TDD evidence before accepting changes.
  • Drift detection & baseline diffing: Determines a baseline commit, computes diffs, and surfaces implemented vs. not-implemented items and design drift.
  • Automated verification pipeline: Auto-detects project test commands, runs sequential quality gates (cross-slice review, sensor clean, coverage, mutation where available), and produces structured reports and artifacts.
  • Retry orchestration: On failures, increments retry counters, moves the session back to implement for targeted TDD cycles, and re-runs full verification up to configurable limits.
  • Use Case: Final verification pass in the deep-work workflow to certify per-slice TDD evidence, generate test-results and reports, and either mark the test phase passed or orchestrate controlled retries.

Quick Start

Run the deep-test phase for the active session to execute all quality and verification gates, generate test-results.md and reports, and automatically retry failing slices within configured retry limits.

Frequently Asked Questions about deep-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify code changes and test receipts for spec compliance?

Comprehensive test verification runs end-to-end quality gates, validates receipt completeness, and detects design drift against baseline diffs to confirm implemented code slices meet spec compliance before project completion.

How does drift detection work during test verification?

Drift detection determines a baseline commit, computes git diffs, and surfaces implemented versus not-implemented items to identify design drift and ensure delivered changes match original project specifications.

What is the best way to automate retry orchestration for failing TDD cycles?

Automating retry orchestration for failing TDD cycles increments retry counters, moves session state back to implement for targeted fixes, and re-runs full verification up to configurable limits until all quality gates pass.

Can I use automated quality gates with my existing project test commands?

Yes, automated quality gates auto-detect existing project test commands and run sequential verification steps including cross-slice review, sensor clean, coverage, and mutation testing where available to produce structured reports and artifacts.

Do I need the deep-work workflow to run cross-slice reviews and quality gates?

Yes, cross-slice reviews and quality gates require projects using the deep-work Brainsearch to Test workflow with per-slice TDD, access to session state and receipts, git history for baseline diffs, and evaluator models for automated analysis.

Why does test verification fail even when individual test cases pass?

Test verification can fail despite passing individual test cases because the pipeline checks receipt completeness, validates TDD evidence per slice, runs cross-slice reviews, and detects design drift that individual tests may not surface.