repo-review-tests

Identify test-coverage gaps and validation weaknesses in a repository slice.

4|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/danielbaustin/agent-design-language --skill repo-review-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-review-tests
Source: https://github.com/danielbaustin/agent-design-language/tree/main/adl/tools/skills/repo-review-tests
Command: npx skills add https://github.com/danielbaustin/agent-design-language --skill repo-review-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reviews of complex multi-agent code bases often miss coverage gaps, weak assertions, brittle fixtures, and validation gaps that permit risky behavior to slip through. This skill provides a bounded, specialist perspective to surface these issues without editing target tests, enabling teams to strengthen test quality and governance.

Core Features & Use Cases

  • Identify coverage gaps, weak assertions, brittle fixtures, and validation gaps in a repository's test suite.
  • Produce structured findings with recommended remediations and a missing-proof map for traceability.
  • Integrate with the repo-review workflow to hand off to synthesis or remediation roles while preserving non-destructive analysis.

Quick Start

Provide a bounded test-review pass for the specified repository slice and emit a structured findings packet.

Frequently Asked Questions about repo-review-tests

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

FAQPage Schema
How do I identify test coverage gaps and weak assertions in a repository?

To identify test coverage gaps, you can use a bounded test-review specialist that scans a repository slice and surfaces missing proofs, weak assertions, and brittle fixtures. It produces structured findings without editing the target tests.

What is a missing-proof map for test validation?

A missing-proof map is a structured artifact that traces validation weaknesses and coverage gaps found during a test review. It maps identified risks to missing test proofs, enabling teams to track remediation for brittle fixtures and weak assertions.

How do I review test risks in a multi-agent codebase without modifying tests?

You can review test risks non-destructively by applying a bounded test-review specialist to a concrete repo slice. It analyzes validation gaps and emits a findings packet with residual risk notes while preserving the original target tests.

Does test coverage review work on specific branches and diffs?

Yes, test coverage review works on specific branches and diffs. You apply the review to a concrete repository slice such as repo_root, target, branch, diff, or review_packet to surface validation weaknesses and missing proofs for that scope.

What is the best way to surface validation weaknesses in a test suite?

The best way to surface validation weaknesses is to run a specialist test review that checks for coverage gaps and brittle fixtures. This generates a structured findings packet with a missing-proof map and residual risk assessment for governance.

What should be included in a test review findings packet?

A test review findings packet should include structured findings, a missing-proof map, validation performed, and residual risk. This suite contract ensures traceability and enables handoff to synthesis or remediation roles for fixing test coverage gaps.