tgd-audit

Audit repository code against test-guided-design principles and generate beads for gaps.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/ChrisSteinbach/claude-skills --skill tgd-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tgd-audit
Source: https://github.com/ChrisSteinbach/claude-skills/tree/main/tgd-audit
Command: npx skills add https://github.com/ChrisSteinbach/claude-skills --skill tgd-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit the codebase against /test-guided-design principles to surface gaps between tests and design, enabling measurable improvements via actionable beads.

Core Features & Use Cases

  • Audit code against /test-guided-design principles to surface design/friction, missing-coverage, and test-style issues.
  • File beads for every gap found with verbatim findings, context for handoff, background motivation, and concrete acceptance criteria.
  • Optionally dispatch an agent team to address the identified gaps.
  • Use cases include teams seeking design-quality feedback tied to tests and a structured remediation workflow.

Quick Start

Run a baseline audit on the repository to surface test-guided-design gaps and generate beads for each finding.

Frequently Asked Questions about tgd-audit

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

FAQPage Schema
How do I audit my code for test-guided design gaps?

To audit code for test-guided design gaps, the skill analyzes your repository against test-guided design principles to surface design friction, missing coverage, and test-style issues. It generates actionable beads containing verbatim findings, context, background motivation, and acceptance criteria for each gap.

What is test-guided design and how does it improve code quality?

Test-guided design is a development principle aligning tests with software design to reduce friction. Auditing your codebase against these principles surfaces gaps between tests and design, enabling measurable improvements via structured, actionable beads for remediation.

Can I scope a code quality audit to specific directories or files?

Yes, you can scope the code quality audit to specific areas by providing file paths, directories, or globs as arguments. If no scope is provided, the audit automatically targets the project's primary source directories like src/, lib/, pkg/, or app/.

How do I automate remediation for missing test coverage and design gaps?

You can automate remediation for missing test coverage and design gaps by optionally dispatching an agent team. The skill produces beads for every gap found with verbatim findings, context, background motivation, and concrete acceptance criteria for the agents to address.

What is the best way to track code quality issues found during an audit?

The best way to track code quality issues found during an audit is through beads. The skill files a bead for every identified test-guided design gap, capturing verbatim findings, handoff context, background motivation, and concrete acceptance criteria for measurable tracking.