cve-patcher

Patch CVE vulnerabilities across repositories by orchestrating dependency-patcher agents.

2|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/Conava/claude-devline --skill cve-patcher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cve-patcher
Source: https://github.com/Conava/claude-devline/tree/main/skills/cve-patcher
Command: npx skills add https://github.com/Conava/claude-devline --skill cve-patcher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Patch CVE vulnerabilities across one or many repositories by researching each CVE and orchestrating dependency-patcher agents to update dependencies, verify fixes, commit changes, and push when appropriate.

Core Features & Use Cases

  • CVE research orchestration: automatically gather affected packages, ecosystems, and fixed versions for multiple CVEs.
  • Multi-repo patching: patch one or many repositories in parallel with a unified workflow.
  • Git-driven delivery: patches follow a strict git workflow (branch creation, commits) while the launcher manages delivery decisions.
  • Status reporting: per-repo patch status, skipped CVEs, and final delivery options.

Quick Start

Provide a list of CVEs and optional --repos, and the launcher will orchestrate the patch workflow across the selected repositories.

Frequently Asked Questions about cve-patcher

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

FAQPage Schema
How do I patch CVE vulnerabilities across multiple git repositories?

The skill orchestrates dependency-patcher agents to research CVEs, update affected dependencies, verify fixes, and commit changes across multiple git repositories in parallel.

What is the best way to automate security vulnerability patching in a git workflow?

Automating security vulnerability patching in a git workflow requires orchestrating agents to research fixed versions, apply dependency updates, run per-repo verification, and create dedicated git branches for commits.

Do I need git and WebSearch to automate CVE patching?

Yes, you need git and WebSearch to automate CVE patching, because the workflow requires git for branch creation and commits, and WebSearch for researching affected packages and fixed versions.

Can I apply per-repo verification settings when patching CVEs in parallel?

Yes, you can apply per-repo verification settings when patching CVEs in parallel by defining them in a local configuration file that the orchestrator reads before applying patches.

How does multi-repo CVE patching handle skipped vulnerabilities and delivery status?

Multi-repo CVE patching handles skipped vulnerabilities and delivery status by generating a per-repo status report that details skipped CVEs and final delivery options after parallel patch tasks complete.

Why are some CVEs skipped during automated dependency patching?

CVEs may be skipped during automated dependency patching if verification fails, fixed versions are unavailable, or per-repo verification settings restrict updates, with all skipped items appearing in the final status report.