check-security

Review git diffs for security issues and generate structured reports.

36|12|Updated Nov 7, 2018
One-click install
npx skills add https://github.com/covoiturage-gouv-fr/mono --skill check-security-covoiturage-gouv-fr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-security
Source: https://github.com/covoiturage-gouv-fr/mono/tree/main/.claude/skills/check-security
Command: npx skills add https://github.com/covoiturage-gouv-fr/mono --skill check-security-covoiturage-gouv-fr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables fast and thorough security code reviews of pending changes or specific files to catch vulnerabilities early.

Core Features & Use Cases

  • Reviews diffs from git diff, git show, or git log to surface potential security issues
  • Provides a structured security checklist covering injection, authentication, data exposure, input validation, dependencies, secrets, and deno-specific considerations
  • Generates a formal report suitable for pull requests and security audits

Quick Start

Run the security scan on your current changes with /check-security.

Frequently Asked Questions about check-security

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

FAQPage Schema
How do I run a security code review on my git diff?

You can review pending changes by applying a comprehensive security checklist to diffs gathered from git diff, git show, or git log, which outputs a structured report for pull requests.

What specific vulnerabilities does a security audit of pending code changes cover?

A security audit of pending code changes covers injection, authentication, data exposure, input validation, dependencies, secrets, and deno-specific considerations to surface potential security issues.

Can I review arbitrary file sets across repositories for security compliance?

Yes, you can review arbitrary file sets across repositories for security compliance, as the security check supports scanning specified files and not just limited git diffs.

Does the security check generate a formal report suitable for PR reviews?

Yes, the security check generates a formal structured report suitable for PR reviews and security audits, directly mapping discovered vulnerabilities from the code diff to actionable items.

What is the best way to catch security vulnerabilities early before merging code?

The best way to catch security vulnerabilities early is performing fast and thorough security code reviews on pending changes, scanning git diffs against a comprehensive security checklist before merge.

When do I need to run a security scan on specified files instead of just git diff?

You need to run a security scan on specified files instead of git diff when auditing existing codebases, reviewing arbitrary file sets across repositories, or targeting specific high-risk modules outside current pending changes.