secrets-check

Scan staged git changes for sensitive patterns like AWS keys and JWTs.

Updated Jul 1, 2026

Search Tags:#git #code review #security scanning #secret detection #commit security

Ready to run

npx skills add https://github.com/NIMBUS-MX/nimbus-skills --skill secrets-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: secrets-check
Source: https://github.com/NIMBUS-MX/nimbus-skills/tree/main/skills/secrets-check
Command: npx skills add https://github.com/NIMBUS-MX/nimbus-skills --skill secrets-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill scans staged changes for known patterns of secrets before committing, preventing accidental exposure of sensitive information.

Core Features & Use Cases

Secret Scan: Identifies patterns for AWS keys, Stripe live keys, JWTs, and more.
Commit Block: Blocks commits containing matched secrets.
User Confirmation: Offers options to unstage files, ignore, or rewrite the commit.

Quick Start

Run 'git commit' or say 'check for secrets' to scan for and block commits with secrets.

Frequently Asked Questions about secrets-check

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

FAQPage Schema

How do I prevent secret exposure in git commits before pushing code?▼

To prevent secret exposure in git commits, you can scan staged changes for sensitive patterns like AWS access keys and JWT tokens before finalizing the commit. This process blocks accidental disclosure of secrets by utilizing regex matching against file contents.

How does regex matching detect sensitive patterns in staged git changes?▼

Regex matching detects sensitive patterns in staged git changes by evaluating file contents against known formats for credentials like Stripe API keys and JWT tokens. When a match is found, the commit is blocked and user prompts are provided to handle false positives.

Can I ignore false positives when scanning staged files for API keys?▼

Yes, you can ignore false positives when scanning staged files for API keys. The scan provides user confirmation options to unstage files, ignore the detected pattern, or rewrite the commit to ensure only actual secrets are blocked.

What types of API keys and tokens are blocked during a pre-commit secret scan?▼

A pre-commit secret scan blocks API keys and tokens such as AWS access keys, Stripe live keys, and JWT tokens. It identifies these specific sensitive patterns within staged git changes to prevent accidental disclosure in code commits.

Does secret detection work automatically when I run a git commit?▼

Yes, secret detection works automatically when you run a git commit or request a check for secrets. The scan evaluates your staged git changes for known secret patterns and blocks the commit if sensitive information is found.