security

Audits pending code changes for vulnerabilities, secrets, and unsafe patterns.

5|Updated Apr 29, 2026

Search Tags:#owasp #security review #secrets #code audit #git diff #cwe #dependency risk

Ready to run

npx skills add https://github.com/friedbotstudio/baseline --skill security-friedbotstudio

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security
Source: https://github.com/friedbotstudio/baseline/tree/main/.claude/skills/security
Command: npx skills add https://github.com/friedbotstudio/baseline --skill security-friedbotstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill performs an evidence-based security review of pending code changes so teams can spot vulnerabilities, secret leakage, and unsafe design choices before merge.

Core Features & Use Cases

Diff-focused review: Analyzes only the current branch changes and any explicitly named files, keeping the review targeted and efficient.
Risk prioritization: Maps findings to OWASP Top 10 and CWE identifiers, then ranks issues from Critical to Low for clear triage.
Reporting workflow: Produces a structured review report in docs/security/<slug>-<date>.md for auditability and follow-up.
Use case: A developer preparing a release can run this Skill to evaluate auth logic, input handling, dependency additions, and secret exposure without modifying code.

Quick Start

Review the current branch’s changes for security issues and write the findings report to docs/security/<slug>-<date>.md.

Frequently Asked Questions about security

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

FAQPage Schema

How do I review a git diff for security vulnerabilities before merging?▼

To review a git diff for security vulnerabilities, this Skill audits pending branch changes for unsafe patterns, mapping exposure risks to OWASP and CWE identifiers, and generates a written report in docs/security.

What's the best way to check code changes for exposed secrets and dependency risks?▼

Checking code changes for exposed secrets and dependency risks involves analyzing the current branch diff to detect hardcoded credentials and unsafe dependency additions, producing a structured triage report for release readiness.

Does this security review tool analyze the entire codebase or just pending changes?▼

This security review tool analyzes only the current branch diff and explicitly named files, keeping the vulnerability audit targeted and efficient without scanning the entire codebase or modifying code.

How do I map detected code vulnerabilities to CWE and OWASP standards during a code audit?▼

To map detected code vulnerabilities to CWE and OWASP standards during a code audit, this Skill evaluates implementation patterns in the branch diff and categorizes findings from Critical to Low for clear triage.

Can I run an automated code audit for release readiness without altering my source files?▼

You can run an automated code audit for release readiness without altering source files by evaluating auth logic and input handling through diff-based analysis, outputting the findings to a markdown report.

Why do I need a written security report for my branch changes?▼

A written security report for branch changes provides auditability and follow-up tracking by documenting secret exposure, dependency risks, and OWASP mapped vulnerabilities in a standardized docs/security file path.