speckit-security-review-branch

Review branch diffs for security vulnerabilities with OWASP-aligned severity rankings.

2|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-security-review-branch-numu-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-security-review-branch
Source: https://github.com/NUMU-IO/NUMU-api/tree/main/.agents/skills/speckit-security-review-branch
Command: npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-security-review-branch-numu-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you review only the code changed in a branch or pull request so you can find security issues without wasting time on unchanged code.

Core Features & Use Cases

  • Diff-scoped security analysis: Focuses on the files and hunks introduced by a feature branch, merge request, or PR.
  • Targeted vulnerability coverage: Checks for injection flaws, access control gaps, secret leaks, weak crypto, misconfiguration, insecure data handling, and risky dependencies.
  • Actionable reporting: Produces severity-ranked findings with locations, OWASP categories, remediation guidance, and a prioritized fix plan.

Quick Start

Ask this Skill to review the security risks in the specified branch diff and summarize only the findings introduced by the changed files.

Frequently Asked Questions about speckit-security-review-branch

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

FAQPage Schema
How do I run a security review on a pull request diff?

A pull request security review scopes analysis to only modified files and hunks in the branch diff, then classifies injection and access control vulnerabilities by OWASP severity to produce targeted remediation guidance.

What security vulnerabilities are checked during a branch diff code audit?

A branch diff code audit checks changed code for injection flaws, access control gaps, secret leaks, weak crypto, misconfiguration, insecure data handling, and risky dependencies introduced by the feature branch.

Can I scope a vulnerability analysis to only changed files in a feature branch?

Yes, you can scope vulnerability analysis to only changed files by using branch-aware diff scoping, which targets feature branch comparisons and merge requests to audit introduced code without reviewing unchanged files.

What is the best way to prioritize security fixes in a pull request?

The best way to prioritize pull request security fixes is to use severity-ranked findings with OWASP categories, exact locations, and remediation guidance to generate a prioritized action plan for the modified code.

Does a branch diff security review check for leaked secrets and risky dependencies?

Yes, a branch diff security review checks modified code for leaked secrets and risky dependencies, alongside authentication flaws, weak crypto, and insecure data handling introduced in the pull request.