Security patch

Diagnose, implement, and verify software security vulnerability fixes.

6|3|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/carson-sweet/sweetclaude --skill security-patch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Security patch
Source: https://github.com/carson-sweet/sweetclaude/tree/main/skills/security-patch
Command: npx skills add https://github.com/carson-sweet/sweetclaude --skill security-patch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the high-stakes challenge of patching security vulnerabilities by enforcing a rigorous, multi-phase workflow that prevents rushed or incomplete fixes.

Core Features & Use Cases

  • Hard-Gated Review: Ensures no security patch is shipped without a mandatory, documented security review.
  • Lifecycle Tracking: Manages the entire process from diagnosis and blast-radius assessment to disclosure tracking and post-ship verification.
  • Use Case: When a critical vulnerability is identified, use this skill to systematically diagnose the impact, implement a minimal fix, perform a mandatory security review, and track disclosure requirements to ensure compliance.

Quick Start

Invoke the security patch skill to begin the diagnostic phase for the identified vulnerability.

Frequently Asked Questions about Security patch

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

FAQPage Schema
How do I patch a security vulnerability while ensuring compliance with disclosure requirements?

Patch a security vulnerability using a structured workflow that includes diagnosis, minimal-scope implementation, mandatory security review, and disclosure tracking to ensure compliance. This process prevents rushed fixes by enforcing a hard-gated review before shipping.

What is the best way to manage the blast radius when fixing a critical security vulnerability?

Managing the blast radius of a security vulnerability involves a structured diagnostic phase to assess impact, followed by minimal-scope implementation and regression testing. This ensures the fix addresses the vulnerability without introducing new risks.

How do I enforce a mandatory security review before shipping a vulnerability fix?

Enforce a mandatory security review by using a hard-gated workflow that blocks any vulnerability fix from shipping without documented approval. This gate ensures all security patches undergo rigorous verification and audit trail generation.

Do I need regression testing for security patching tasks?

Regression testing is required for security patching tasks to verify the fix does not introduce new issues. The workflow mandates post-ship verification to ensure the vulnerability is resolved and system stability is maintained.

When should I use a structured workflow for software vulnerability fixes?

Use a structured workflow for software vulnerability fixes when facing critical security patches that require audit trails, disclosure management, and strict security review gates. It is designed for high-stakes patching where incomplete fixes pose significant risk.

Why does my security patch require post-ship verification and disclosure tracking?

Post-ship verification and disclosure tracking are required to maintain compliance and confirm the vulnerability fix is effective. This lifecycle management ensures the patch passes regression testing and meets all risk management and disclosure obligations.