Generate candidate fixes for verified security findings. Consumes TRIAGE.json (preferred), VULN-FINDINGS.json, INCIDENTS.json, or a vuln-pipeline results directory. Pipeline input is delegated to the execution-verified `vuln-pipeline patch` ladder; static-analysis input gets a per-finding patch subagent + independent reviewer and is written as inert diffs for human review. Writes PATCHES/bug_NN/{patch.diff,patch_result.json}, PATCHES.md, and PATCHES.json. Use when asked to "fix the findings", "patch these vulns", "generate fixes", or "close the loop on triage".
Security
1 high severity finding. You should review these findings carefully before considering using this skill.
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
The skill requires subagents to Read repository files and emit unified diffs verbatim (and the reviewer sees raw diff bytes), so any secrets present in source (API keys, tokens, passwords) would be read and included verbatim in generated output, enabling exfiltration.
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The required workflow ingests `findings_path` inputs such as `VULN-FINDINGS.json`, `INCIDENTS.json`, or pipeline `results/<target>/<ts>/` files at runtime (Phase 1 ingest / Phase 2 static delegate), and those are outsider-authored arbitrary free-text fields (e.g., `description`/`rationale`/`body` equivalents) that are then placed into the subagent prompt context.
d3bea6b
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.