git-privacy

Block AI attribution lines from git commits and pull requests.

35|3|Updated Jun 24, 2025

Search Tags:#git #compliance #attribution #privacy #co-authored-by #generated-with

Ready to run

npx skills add https://github.com/intelligentcode-ai/intelligent-claude-code --skill git-privacy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-privacy
Source: https://github.com/intelligentcode-ai/intelligent-claude-code/tree/main/src/skills/git-privacy
Command: npx skills add https://github.com/intelligentcode-ai/intelligent-claude-code --skill git-privacy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents AI attribution in git operations by blocking Co-Authored-By lines and generated-footers from commits, PRs, and related metadata.

Core Features & Use Cases

Enforces attribution privacy: blocks AI-authorship indicators in commit messages, PR titles, and bodies.
Supports standard workflows: applies during commits, PR creation, and branch naming to prevent leakage of model info.
Use Case: when collaborating on sensitive code, ensure that no attribution lines or "Generated with" footers appear in history or PR discussions.

Quick Start

Default behavior enforces attribution privacy across Git operations. If you need to disable, edit icc.config.json and set: { "git": { "privacy": false } }

Frequently Asked Questions about git-privacy

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

FAQPage Schema

How do I remove Co-Authored-By lines from git commits?▼

To remove Co-Authored-By lines from git commits, you need a privacy enforcement mechanism that blocks AI attribution indicators across standard commit workflows. This prevents AI authorship metadata from appearing in your commit history and pull requests.

Can I block "Generated with" footers in pull requests automatically?▼

Yes, you can block "Generated with" footers in pull requests automatically by applying an attribution privacy rule. This enforces default privacy across PR titles and bodies while still allowing legitimate AI feature descriptions in the text.

Does git-privacy affect branch naming or only commit messages?▼

Git-privacy affects both commit messages and branch naming to prevent leakage of model info. It applies across standard git workflows including commits, PR creation, and branch generation to comprehensively enforce attribution privacy.

How do I disable attribution blocking if I need to show AI authorship?▼

To disable attribution blocking and show AI authorship, edit the icc.config.json file and set the git privacy option to false. This provides an easy opt-out mechanism when you need to display AI attribution in your git history.

What is the best way to prevent AI model info leakage in sensitive code?▼

The best way to prevent AI model info leakage in sensitive code is to enforce attribution privacy that blocks Co-Authored-By lines and generated footers. This ensures no attribution lines appear in history or PR discussions during collaboration.