skills.rest
SocketDev
SocketDevOFFICIAL
Explore all skills by this author →
Website𝕏@SocketSecurityGitHub

patching-findings

Generate surgical patches for verified security findings from TRIAGE.json or VULN-FINDINGS.json.

125|42|Updated May 19, 2025
Search Tags:#automation#security#triage#code-review#patching#patching-findings
One-click install
npx skills add https://github.com/SocketDev/socket-mcp --skill patching-findings
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: patching-findings
Source: https://github.com/SocketDev/socket-mcp/tree/main/.claude/skills/fleet/patching-findings
Command: npx skills add https://github.com/SocketDev/socket-mcp --skill patching-findings

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Patch verification and surgical code changes are orchestrated automatically for verified security findings, ensuring traceable, minimal edits.

Core Features & Use Cases

  • Automates patch generation for true-positive findings consuming TRIAGE.json or VULN-FINDINGS.json.
  • Enforces a blind-reviewer gate and one surgical commit per finding for safe deployment.
  • Supports selective patching via --top and --id, and provides dry-run mode for preview.

Quick Start

Provide TRIAGE.json to the skill and run it in dry-run mode to preview applied patches.

Frequently Asked Questions about patching-findings

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

FAQPage Schema
How do I automate patch generation for verified security findings?▼

Automate patch generation by providing TRIAGE.json or VULN-FINDINGS.json inputs to generate surgical code changes for true-positive vulnerabilities, ensuring traceable and minimal edits with a multi-phase workflow.

Can I preview security patches before committing them to my repository?▼

Yes, you can preview patches by running the skill in dry-run mode before applying changes, allowing you to verify automated patch generation without writing commits to your writable repository.

What is a blind-reviewer gate in automated security patching?▼

A blind-reviewer gate is an enforced validation phase within the patching workflow that reviews generated code changes before deployment, ensuring one surgical commit per finding is safe for deployment.

How do I patch specific security findings instead of all true-positives at once?▼

You can selectively patch specific security findings by using the --top flag to limit the number processed or the --id flag to target individual entries within your TRIAGE.json or VULN-FINDINGS.json files.

Do I need a writable repository to apply automated vulnerability patches?▼

Yes, a writable repository is required because the automated patching workflow creates one surgical commit per verified finding, directly applying the traceable code changes to your codebase.

Related Skills

Explore More Software Engineering Skills→
air-gappedair-gapped
5

patch

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

Official
Advanced
victorp1leonvictorp1leon

web.publish

Execute web content actions with confirmation and auditability via operation_id.

Community
Intermediate
jeremylongshorejeremylongshore
2.6k

building-cicd-pipelines

Generate CI/CD pipeline configurations for GitHub Actions, GitLab CI, and Jenkins.

Community
Intermediate
SocketDevSocketDev
125

fleet-patching-findings

Generate surgical patches for verified vulnerability findings and commit them to a code repository.

Official
Advanced