security

Review git diffs for secrets, vulnerabilities, and injections.

Updated May 25, 2025

Search Tags:#security #vulnerability #injection #risk-assessment #code-review #secret-detection #git-diff

Ready to run

npx skills add https://github.com/temple-slope/dotfiles --skill security-temple-slope

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security
Source: https://github.com/temple-slope/dotfiles/tree/main/dot_claude/skills/security
Command: npx skills add https://github.com/temple-slope/dotfiles --skill security-temple-slope

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill helps detect security risks by auditing differences between the current branch and main, surfacing secrets, misconfigurations, and potential injections before merging.

Core Features & Use Cases

Diff-based security review: scans git changes for sensitive patterns (api keys, tokens, passwords) and common vulnerabilities.
Comprehensive checks: highlights injection risks, secret leakage, and insecure configurations across changed files.
Use Case: during a pull request, automatically review diffs to prevent leaking secrets or introducing vulnerabilities.

Quick Start

Run the security review on the current branch against main and report any secrets, vulnerabilities, or injections.

Frequently Asked Questions about security

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

FAQPage Schema

How do I scan git diffs for security vulnerabilities before merging?▼

Scanning git diffs for security vulnerabilities involves reviewing branch changes against main to detect secrets, injections, and insecure configurations in changed files. This process surfaces sensitive patterns like api keys and tokens before merging.

Can I detect leaked secrets and credentials in a pull request code review?▼

Detecting leaked secrets and credentials in a pull request code review requires auditing the git diff between the current branch and main. This highlights sensitive patterns such as passwords and tokens to prevent secret leakage during pre-merge checks.

What is diff-based risk assessment for identifying injection risks?▼

Diff-based risk assessment for identifying injection risks is a security review mechanism that scans git changes for common attack vectors. It evaluates changed files to surface potential injections and insecure configurations before code integration.

Does this security review work without external dependencies or components?▼

This security review operates without external dependencies or components. It independently scans the git diff between your current branch and main to produce a structured assessment of secrets and vulnerabilities.

When should I use a git diff security review instead of a full codebase audit?▼

Use a git diff security review instead of a full codebase audit during pull requests and pre-merge checks. It specifically targets changed files to rapidly surface injection risks and secret leakage without scanning the entire repository.