patch

Generate inert diffs for verified security findings from TRIAGE.json or VULN-FINDINGS.json inputs.

5|1|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/air-gapped/skills --skill patch-air-gapped
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: patch
Source: https://github.com/air-gapped/skills/tree/main/.claude/skills/patch
Command: npx skills add https://github.com/air-gapped/skills --skill patch-air-gapped

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Generates candidate patches for verified security findings without applying changes to the target repository, providing inert diffs for human review.

Core Features & Use Cases

  • Supports TRIAGE.json, VULN-FINDINGS.json, or execution-harness results as input.
  • Produces PATCHES/bug_NN/{patch.diff,patch_result.json}, PATCHES.md, and PATCHES.json for review and traceability.
  • Operates in static review mode or execution-verified mode via vuln-pipeline, wiring output into PATCHES and PATCHES.json / PATCHES.md.

Quick Start

Execute /patch TRIAGE.json with a read-only repository to generate candidate patches for verified findings.

Frequently Asked Questions about patch

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

FAQPage Schema
How do I generate security patches from triage findings without modifying the target repository?

You can generate candidate patches from verified security findings by ingesting TRIAGE.json or VULN-FINDINGS.json with a read-only repository path. The process outputs inert diffs for human review without applying changes to the target repository.

What is the best way to automate creating diffs for verified vulnerability findings?

Automating candidate patch generation for vulnerabilities involves processing execution-harness results or VULN-FINDINGS.json. The system outputs inert diffs in PATCHES/bug_NN directories alongside PATCHES.md and PATCHES.json for complete review traceability.

Can I filter which security findings get patches generated for them?

Yes, you can filter findings when generating patches by specifying either a top N number or a specific fNNN id. This allows targeted patch generation from your TRIAGE.json or VULN-FINDINGS.json inputs.

Does the patch generation process support execution-verified modes?

Yes, execution-verified mode is supported by delegating to vuln-pipeline and copying the resulting patch.diff into PATCHES/bug_NN. This complements static review mode, which writes PATCHES.json and PATCHES.md alongside patch files without execution validation.

What formats do the generated vulnerability patch files use?

Generated vulnerability patches are output as inert diffs within PATCHES/bug_NN directories, accompanied by PATCHES.json and PATCHES.md. This format ensures all candidate patches remain unapplied and fully traceable for human review.

When should I use static review mode instead of execution-verified mode for patch generation?

Use static review mode when you need candidate patches as inert diffs written to PATCHES.json and PATCHES.md without execution. Use execution-verified mode when you need patches validated by delegating to vuln-pipeline before copying results into PATCHES/bug_NN.