security

Detect leaked credentials in code before Git commits.

41|7|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/DGouron/review-flow --skill security-dgouron
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security
Source: https://github.com/DGouron/review-flow/tree/main/.claude/skills/security
Command: npx skills add https://github.com/DGouron/review-flow --skill security-dgouron

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code scan to detect secrets before commit. Use before git add/commit/push or on demand. Checks for tokens, API keys, credentials, and other sensitive data.

Core Features & Use Cases

  • Pre-commit secret detection to prevent credentials leaking into version control.
  • Activation before git commit, git push, or on explicit request; CLI support via flux security-scan.
  • Detects patterns for tokens, API keys, credentials, and other sensitive data with actionable guidance.

Quick Start

Run a pre-commit secret scan before committing by using the CLI or on-demand trigger.

Frequently Asked Questions about security

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

FAQPage Schema
How do I detect API keys and secrets before a git commit?

Pre-commit secret detection scans staged code to find and block leaked credentials before they enter version control. It checks for tokens, API keys, and sensitive data patterns by running before git add or commit operations.

Can I scan for credentials in GitHub and GitLab repositories on demand?

Yes, you can run on-demand credential scans across GitHub and GitLab repositories. The tool integrates with Git workflows covering pushes and pull/merge requests, and supports CLI execution via the security-scan command.

What types of tokens and credentials does pattern-based secret detection find?

Pattern-based secret detection identifies common credentials including API keys, access tokens, and other sensitive data patterns. It reports findings with actionable guidance to help remediate detected credential leaks before committing code.

Does this pre-commit hook work with existing CLI workflows?

Yes, the pre-commit hook integrates with existing CLI workflows through the flux security-scan command. You can trigger secret detection before git commit, git push, or run it on explicit request without disrupting your development pipeline.

Why run secret detection before a git push instead of after?

Running secret detection before a git push prevents credentials from leaking into remote version control. Scanning code pre-commit blocks sensitive data locally, avoiding the need to purge leaked tokens from GitHub or GitLab history after exposure.

What is the best way to block leaked tokens in pull and merge requests?

The best way to block leaked tokens is applying pre-commit secret detection across Git workflows. It intercepts commits, pushes, and pull/merge requests on GitHub and GitLab, using pattern matching to find credentials before integration.