project-verify-code

Reviews assembled code against its plan by rerunning builds, tests, and live probes inline.

1|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/envoydev/claude-stack --skill project-verify-code-envoydev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-verify-code
Source: https://github.com/envoydev/claude-stack/tree/main/stack/skills/project-verify-code
Command: npx skills add https://github.com/envoydev/claude-stack --skill project-verify-code-envoydev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? After code is built against a plan, it is easy to trust a green test suite and miss live failures, broken consumers, or plan deviations. This Skill runs a full post-build review in a single chat without dispatching subagents, catching defects before commit. ## Core Features & Use Cases - Build and test re-verification: Reruns the build and test suite in the current session and quotes the output rather than trusting prior results. - Plan conformance and stack-trap audit: Gates the diff against the plan's tasks, decisions, and log points, then checks it against the stack's known data-access, lifecycle, and concurrency traps. - Live probing and contract tracing: Boots the app through its production composition root, probes failing inputs, and traces changed wire contracts to their consumers. - Use Case: After an implementer finishes a streamed export endpoint, run this review to discover that a malformed query parameter returns a live 500 instead of 400, and that a sibling web client still expects the old response shape. ## Quick Start Ask the AI to review the build and check the code against its plan before committing.

Frequently Asked Questions about project-verify-code

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

FAQPage Schema
How do I review code against a plan before committing?▼

Run this review after the build completes: it reruns build and tests, gates the diff against the plan's tasks and decisions, probes the live app on failing inputs, and returns a ranked punch-list keyed to file and symbol.

What is the difference between inline code review and dispatching a verifier subagent?▼

The inline review keeps all reads and build output in the current chat with zero agent dispatch and predictable cost. The verifier subagent runs the same protocol in isolation so its read volume never touches your session, which suits long sessions.

Why do tests pass but the live app still fails?▼

Test hosts wire their own providers, so a missing app-level registration ships behind a green suite. The review boots the app through its production composition root and makes one real end-to-end call to catch that class of failure.

When should I not use this code review skill?▼

Do not use it for auditing the plan itself, which happens before any code exists, or for applying fixes, since it only flags findings and hands them back. For a broad parallel-angle sweep, use a fan-out review instead.

Does the review check whether changed API contracts break consumers?▼

Yes. When the diff changes a public or wire contract such as a response shape or exported type, the review traces it to all consumers, including sibling projects listed in the related-projects context file, and flags any break.