speckit-security-review-staged

Audit staged git diffs for security vulnerabilities in source-code changes.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/B0yZ4kr14/OrthoPlus-Enterprise --skill speckit-security-review-staged
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-security-review-staged
Source: https://github.com/B0yZ4kr14/OrthoPlus-Enterprise/tree/main/.specify-backups/20260518-141826/_agents/skills/speckit-security-review-staged
Command: npx skills add https://github.com/B0yZ4kr14/OrthoPlus-Enterprise --skill speckit-security-review-staged

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you focus a security review on exactly what is going to be committed, reducing noise from unrelated parts of the codebase and making security checks faster and more actionable.

Core Features & Use Cases

  • Staged-only security review: Reviews only changes in the git index (cached/staged) instead of the entire repository.
  • Change-driven scope detection: Detects changed files via Spec-Kit’s workflow scripts to determine the audit set.
  • Security domain coverage: Evaluates diffs for injection risks, hardcoded secrets/credentials, auth/access-control gaps, insecure crypto, misconfiguration, validation failures, and dependency/supply-chain concerns.
  • Spec-Kit compatible reporting: Produces findings with severity, location, OWASP category, CWE IDs, CVSS guidance, and remediation backlogs.

Quick Start

Run the staged security review for your current commit scope so the AI audits only what you are about to push.

Frequently Asked Questions about speckit-security-review-staged

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

FAQPage Schema
How do I run a security review on staged git diffs before committing?

You can review staged source-code changes by analyzing the git diff limited to the commit index. The Skill audits injection risks, hardcoded secrets, authorization gaps, and insecure cryptography, producing structured findings with severity, CWE IDs, and remediation backlogs.

What security vulnerabilities can be detected in a pre-commit code review?

A pre-commit code review can detect injection risks, hardcoded secrets, authorization gaps, insecure cryptography, misconfiguration, input validation failures, and dependency supply-chain concerns. Findings are mapped to OWASP categories and CWE IDs with CVSS guidance.

Does this security review tool require a specific project structure?

Yes, this security review tool requires Spec-Kit project structure support. It relies on Spec-Kit's workflow scripts to detect changed files in the git index and determine the exact audit set for your staged diff.

Can I limit vulnerability analysis to only the files in my git index?

Yes, you can limit vulnerability analysis to only the files in your git index. The Skill performs a staged-only security review, which reduces noise from unrelated parts of the codebase and makes security checks faster and more actionable.

What is the best way to scan for hardcoded secrets in a pull request diff?

The best way to scan for hardcoded secrets in a pull request diff is to audit the staged source-code changes directly. This applies to pull-request workflows by evaluating diffs for credentials and producing structured findings with an optional memory capture step.