repo-review-code

Review multi-agent repository code for correctness and maintainability risks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bounded, findings-first code reviews that identify correctness, maintainability, and API-use risks in multi-agent repositories, without taking over security, docs, tests, or synthesis tasks.

Core Features & Use Cases

  • Bounded, findings-only review for API misuse, state machine issues, concurrency bugs, and implementation drift.
  • Produces clear findings with file references, severity, and trigger scenarios, ready for synthesis or remediation planning.
  • Emits review artifacts in a standardized packet for integration with downstream specialists.

Quick Start

Identify the highest-risk surfaces in the target repository and generate a complete findings-first review packet.

Frequently Asked Questions about repo-review-code

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

FAQPage Schema
How do I review code for concurrency and state machine issues in a multi-agent repository?

Review multi-agent repositories for concurrency and state machine issues using a bounded, findings-first analysis of core runtime modules and stateful logic. This generates actionable findings with file references, severity levels, and trigger scenarios for remediation.

What is a findings-only code review and how does it work for API misuse detection?

A findings-only code review identifies correctness, maintainability, and API misuse risks without handling security, docs, or tests. It analyzes high-risk implementation surfaces and outputs a standardized packet containing file references and severity for downstream synthesis.

Can I use static analysis to find implementation drift in multi-agent systems?

Static analysis can detect implementation drift in multi-agent systems by bounding the review to manifests, entry points, and core runtime modules. It outputs a review artifact detailing specific trigger scenarios and severity levels for identified drift.

What is the best way to prepare a code review packet for multi-agent repository synthesis?

Prepare a review packet for multi-agent synthesis by generating a bounded, findings-first review of maintainability and correctness risks. The packet must include file references, severity, and trigger scenarios before handing the artifact to a synthesis specialist.

When should I not use a bounded findings-first approach for code review?

Avoid a bounded findings-first approach when you need comprehensive security audits, documentation generation, test coverage analysis, or final report synthesis, as this review strictly focuses on correctness, maintainability, and API-use risk detection.