no-sensitive-commits

Detect and prevent sensitive personal information in git commit messages.

Updated May 22, 2025
One-click install
npx skills add https://github.com/curtjen/.gir --skill no-sensitive-commits
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: no-sensitive-commits
Source: https://github.com/curtjen/.gir/tree/main/skills/no-sensitive-commits
Command: npx skills add https://github.com/curtjen/.gir --skill no-sensitive-commits

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This policy helps prevent sensitive personal information from leaking into git commit messages by providing clear guidelines for privacy-conscious communication.

Core Features & Use Cases

  • Enforces privacy-aware commit messaging practices for teams.
  • Provides examples of safe wording and templates to replace PII.
  • Useful during code reviews and Claude-assisted workflows to maintain data privacy.

Quick Start

Ask Claude to review your commit message and remove any personal data before you push.

Frequently Asked Questions about no-sensitive-commits

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

FAQPage Schema
How do I prevent sensitive data from leaking into git commit messages?

To prevent sensitive data in git commit messages, you can use guardrails that detect PII patterns and suggest safer wording before data enters version history. This enforces privacy-aware messaging during drafting.

What is the best way to scan commit messages for PII before pushing?

Scanning commit messages for PII is best handled by applying detection guardrails during the commit drafting phase. This process identifies sensitive personal information patterns and provides safe wording templates to replace them.

Can I use Claude to review commit messages for privacy compliance?

Yes, you can use Claude-assisted workflows to review commit messages for privacy compliance. The review process checks for sensitive personal information and suggests safer wording to maintain data privacy before pushing.

Does this approach work with existing development workflows and code reviews?

Yes, this approach integrates with existing development workflows and code reviews by applying privacy-aware commit messaging practices. It provides guidelines and examples useful during Claude-assisted reviews to maintain data privacy.

How do I automatically redact personal information in git commit guidelines?

To automatically redact personal information in git commit guidelines, you apply guardrails that detect PII patterns during message drafting. The system suggests safer wording templates to replace sensitive data before it is stored in version history.