security-sweep

Analyze code changes for security vulnerabilities using predefined patterns.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/kirvin/agent-dev-harness --skill security-sweep-kirvin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-sweep
Source: https://github.com/kirvin/agent-dev-harness/tree/main/plugins/kf/skills/security-sweep
Command: npx skills add https://github.com/kirvin/agent-dev-harness --skill security-sweep-kirvin

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a comprehensive security review of code changes in a pull request or branch, automatically detecting vulnerabilities and creating tasks for remediation.

Core Features & Use Cases

  • Security Analysis: Detects common security vulnerabilities across various categories like Credential Exposure, Authentication, Injection, etc.
  • Stack Identification: Automatically identifies the project stack and loads appropriate security patterns.
  • Finding and Triage: Identifies findings, classifies them by severity, and creates tasks for remediation.
  • Use Case: Use this Skill after code is written to ensure that no security issues were overlooked during the initial review.

Quick Start

Run the security-sweep skill on the current branch to scan for security vulnerabilities.

Frequently Asked Questions about security-sweep

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

FAQPage Schema
How do I automate security vulnerability scanning during a pull request review?

Automate security vulnerability scanning by running an analysis on code changes to detect issues like credential exposure and injection. It automatically identifies the project stack, loads security patterns, and creates remediation tasks.

What security patterns are checked during code review analysis?

Code review security analysis checks for common vulnerabilities across categories like Credential Exposure, Authentication, and Injection. It applies predefined patterns based on the automatically identified project stack.

Can I use security analysis to find vulnerabilities in an existing branch?

Yes, you can use security analysis on an existing branch. It scans code changes for potential vulnerabilities and classifies findings by severity to help you catch security issues overlooked during initial development.

How do I triage security findings after vulnerability scanning?

Vulnerability scanning triages findings by classifying them by severity and automatically creating tasks for remediation. This allows developers to systematically address detected security vulnerabilities.

What is the best way to secure code changes before merging a pull request?

The best way to secure code changes is to run a comprehensive security review after code is written. This automatically detects vulnerabilities, identifies the project stack, and creates remediation tasks before merging.