Git Security

Validate Git repositories for sensitive files before pushing.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/Takashi-Matsumura/lion-frame --skill git-security
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Git Security
Source: https://github.com/Takashi-Matsumura/lion-frame/tree/main/.claude/skills/git-security
Command: npx skills add https://github.com/Takashi-Matsumura/lion-frame --skill git-security

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents accidental commits of sensitive information like personal data, API keys, and database files to your Git repository, safeguarding against data breaches and compliance violations.

Core Features & Use Cases

  • Pre-push Validation: Automatically checks for common sensitive file types before you push your code.
  • Sensitive File Identification: Lists files that should not be tracked by Git (e.g., .env, .db, employee images).
  • Correction Guidance: Provides clear steps to remove files from Git history and add them to .gitignore.
  • Deployment Notes: Highlights files that require manual, secure transfer to production environments.
  • Use Case: Before pushing a new feature, you can run this Skill to ensure no accidentally committed database backups or API keys are exposed to the public repository.

Quick Start

Run the git security skill to check for sensitive files before your next git push.

Frequently Asked Questions about Git Security

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

FAQPage Schema
How do I check for sensitive files before a git push?

Pre-push validation automatically checks for common sensitive file types before a git push to prevent accidental commits. It scans environment variables, database files, and personal data like employee images to safeguard against data breaches.

How do I remove tracked sensitive files from my git history?

To remove tracked sensitive files from git history, you can follow the correction guidance provided by the validation check. It provides clear steps to remove files from git history and add them to .gitignore, ensuring secure code deployment.

What types of sensitive files should not be tracked in a git repository?

Sensitive files that should not be tracked in a git repository include environment variable files, database files, and personal data like employee images. Identifying these prevents accidental commits of API keys and protects sensitive information.

What is the best way to prevent committing environment variables and database files to git?

The best way to prevent committing environment variables and database files is to run a validation check before pushing code. This process lists files that should not be tracked and provides steps to update .gitignore for data protection.

How do I securely handle files that require manual transfer to production environments?

Securely handle files requiring manual transfer by reviewing deployment notes generated after validation. These notes highlight sensitive files excluded from git that require manual, secure transfer to production environments to maintain compliance.