git-security

Name: git-security
Availability: InStock
Author: winsorllc

Scan Git repositories for hardcoded secrets using predefined regular expressions.

1|Updated Feb 25, 2026

Search Tags:#git #code review #security #secrets #pre-commit #scanning

Ready to run

npx skills add https://github.com/winsorllc/upgraded-carnival --skill git-security-winsorllc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-security
Source: https://github.com/winsorllc/upgraded-carnival/tree/main/.pi/skills/git-security
Command: npx skills add https://github.com/winsorllc/upgraded-carnival --skill git-security-winsorllc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps prevent sensitive information like API keys and passwords from being accidentally committed to your Git repository, safeguarding your project's security.

Core Features & Use Cases

Secret Detection: Scans files for common patterns of secrets (API keys, passwords, tokens).
Commit Validation: Can be integrated as a pre-commit hook to block commits containing secrets.
Use Case: Before pushing your code, run this scanner to ensure no accidental exposure of your AWS credentials or database passwords.

Quick Start

Run the git-security scanner on your repository to check for secrets.

Frequently Asked Questions about git-security

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

FAQPage Schema

How do I scan a Git repository for hardcoded secrets and API keys?▼

You can scan a Git repository for hardcoded secrets by running the scanner on your project directory to detect API keys, passwords, and tokens using predefined regular expressions. It supports scanning staged files and entire directories to prevent accidental commits of sensitive data.

How do I prevent passwords or tokens from being committed to Git?▼

To prevent passwords or tokens from being committed, integrate this scanner as a pre-commit hook to automatically block commits containing detected secrets. This safeguards your project's security by validating code before it gets pushed to the remote repository.

What is the best way to check staged files for sensitive data before a commit?▼

The best way to check staged files for sensitive data is using a pre-commit hook that validates staged changes. The scanner supports scanning staged files to prevent accidental exposure of AWS credentials or database passwords during your commit process.

Does pre-commit scanning work with existing Git repositories and directories?▼

Yes, pre-commit scanning works with existing Git repositories and directories. The scanner supports scanning entire directories as well as staged files, allowing you to validate both your current codebase and new changes before committing.

Can I use this secret scanning tool to detect AWS credentials in my code?▼

Yes, you can use this secret scanning tool to detect AWS credentials in your code. It scans files for common patterns of secrets including API keys, passwords, and tokens using predefined regular expressions to ensure no accidental exposure occurs.

What types of secrets can regular expression scanning find in my codebase?▼

Regular expression scanning can find common patterns of hardcoded secrets in your codebase, including API keys, passwords, and tokens. It uses predefined regular expressions to identify sensitive data across staged files and entire project directories.

dotnet

209

secret-handling

Block unsafe .env reads and scan staged git changes for secrets.

Official

Advanced

eysenfalk

git-workflow

Enforce Git branch naming, commit message formats, and merge policies.

Community

Advanced

JFrangel

security-guard

Detects and remediates security vulnerabilities in code, infrastructure, and architecture using OWASP and DevSecOps standards for pre-production environments.

Community

Advanced