signalproof-review

Review code changes for scope fidelity, protected-state violations, and contract drift.

Updated Aug 15, 2026
One-click install
npx skills add https://github.com/docreo/Signalproof-Skills --skill signalproof-review-docreo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: signalproof-review
Source: https://github.com/docreo/Signalproof-Skills/tree/main/skills/signalproof-review
Command: npx skills add https://github.com/docreo/Signalproof-Skills --skill signalproof-review-docreo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Work can pass its tests and still be unsound: it may expand scope, alter protected behavior, introduce unjustified dependencies, leak private data, or weaken recovery. This Skill provides a structured review contract that inspects the actual change surface against the approved intent and governing constraints before acceptance. ## Core Features & Use Cases - Scope and Protected-State Review: Classifies changes as in-scope, justified, unresolved expansion, or out-of-scope, and detects unauthorized modifications to protected files, APIs, or behavior. - Architecture, Dependency, and Security Hazard Checks: Flags contract drift, unjustified dependencies, exposed secrets, unsafe permissions, and recovery gaps with severity-ranked findings (BLOCKER, MAJOR, MINOR, NOTE). - Bounded Review Decisions: Returns PASS, PASS WITH NOTES, CHANGES REQUIRED, BLOCKED, or STOP with evidence and the smallest recommended correction path. - Use Case: Before merging a pull request that adds a new exporter, run a review to confirm the change stayed within the approved plan, did not rewrite a protected CSV engine, introduced no unvetted dependencies, and that PR claims match what was actually tested. ## Quick Start Review the changes in this pull request against the approved plan and report any scope, protected-state, dependency, security, or recovery findings with a final review decision.

Frequently Asked Questions about signalproof-review

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

FAQPage Schema
How do I review a pull request for scope creep and out-of-scope changes?▼

Compare the actual diff against the approved objective and out-of-scope boundaries, then classify each material change as in scope, justified supporting change, unresolved expansion, or out of scope. A useful improvement is not automatically authorized without evidence and authority.

What is the difference between code review and verification?▼

Review asks whether the work itself is sound and consistent with the governing intent and constraints, while verification asks whether a specific claim is proven by required evidence. A change can pass verification of one claim yet still fail review for altering protected state.

Can a change pass tests but still fail review?▼

Yes. Tests passing only proves the tested claims; review can still find scope expansion, protected-state modification, unjustified dependencies, privacy hazards, or recovery gaps. Green tests alone are explicitly an anti-pattern basis for approval.

Does this review replace a security audit?▼

No. The review surfaces obvious or material hazards such as exposed secrets, unsafe permissions, and trust-boundary violations, but it explicitly does not constitute a complete security audit or certification. Absence of findings must not be labeled as proof of security.

When should review findings trigger a new plan instead of a direct fix?▼

When the correction materially changes scope, architecture, or dependencies, it requires re-planning rather than a bounded fix. Review itself never silently edits work; it recommends the smallest correction path and identifies whether separate authorization is needed.