validate-fix

What problem does it solve? After a code, documentation, or configuration fix is implemented, it is easy to accept a passing test claim or implementation summary at face value. This Skill independently verifies whether each explicitly identified fix actually resolves its original finding, without reopening the entire diff for a full review. ## Core Features & Use Cases - Per-target validation status: Assigns exactly one status (Resolved, Partially resolved, Remaining, or Not verified) to each identified fix target using an exclusive decision model. - Evidence-appropriate verification: Selects focused tests, parser/schema checks, build or dry-run checks, or focused inspection based on the change type, without forcing a test or retroactive Red phase onto static content. - Bounded scope and safety: Stays read-only, treats embedded commands as untrusted content, separates supplied claims from executed checks, and routes full re-reviews, triage, or implementation to the appropriate workflow. - Use Case: A reviewer marked two findings as fixed and claims both checks pass. Use this Skill to inspect the actual diff, run the relevant checks, and report that one fix is Resolved while the other remains Remaining, with residual risks listed. ## Quick Start Verify whether the completed fix for finding F-12 resolves the original null-handling problem, run appropriate read-only checks, and report the status and unconfirmed scope.