verify-fix
Verify Fix
When to Use
Invoke this skill only for an explicit request to verify a security fix, including a direct $verify-fix invocation. A request to implement a fix or run its tests does not by itself request this skill. For other tasks, follow the user's requested workflow and response format.
Objective
Determine whether each supplied security finding has been fixed in the current checkout. Operate in standalone verification-only mode; do not create, modify, or delete repository files, apply patches, commit changes, write artifacts, or modify issue trackers.
Assessment Method
Use ../../references/static-finding-assessment.md to identify the original attacker-controlled source, security control, sensitive sink, reachable path, trust boundary, counterevidence, and proof gaps. If the caller already supplied that reference in the prompt, use the supplied contents without reading it again.
Use standard verification unless the caller explicitly selects verificationMode: static. In static mode, assess the current source and diff, the original exploit path and plausible bypasses, and legitimate behavior through callers and existing tests read as source. Do not install dependencies or run builds, tests, reproducers, or the application, including when validation instructions request them. Repository-reading tools remain available. State in the evidence that this is a static assessment and runtime checks were not performed; do not count them as passed or require them for this assessment. Missing runtime tooling alone does not make the result inconclusive, but a material gap in the source evidence does.