git-workflow

Validate Git commits for secrets and enforce safe push rules.

8|Updated Nov 4, 2025
One-click install
npx skills add https://github.com/ilude/claude-code-config --skill git-workflow-ilude
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/ilude/claude-code-config/tree/main/skills/git-workflow
Command: npx skills add https://github.com/ilude/claude-code-config --skill git-workflow-ilude

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes Git operations, ensuring secure, well-structured, and human-like commits while preventing common mistakes like pushing secrets or using AI attribution. It automates the tedious parts of Git hygiene, allowing you to focus on coding.

Core Features & Use Cases

  • Automated Security Scan: Scans for secrets (API keys, tokens, passwords) before every commit, blocking pushes if found (with a git-crypt exception), safeguarding your repository.
  • Structured Commit Messages: Enforces conventional commit types (feat, fix, docs, etc.) and a human-like, attribution-free format using HEREDOC, improving commit history readability.
  • Safe Push Behavior: Prevents accidental pushes by requiring an explicit "push" keyword, and prohibits force pushes to main/master, protecting your codebase.
  • Use Case: You've made changes across several files. Ask the AI to "commit my changes with a fix type and a message about fixing the login bug." The AI will scan for secrets, group changes, format the commit message correctly, and commit locally, then wait for an explicit "push" command, ensuring a clean and secure commit history.

Quick Start

Commit all current changes with a 'feat' type and the message "Implement user profile editing." Then, push the changes to the remote repository.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I prevent secrets from being accidentally committed to Git?

This Skill automatically scans for secrets like API keys, tokens, and passwords before every commit, blocking pushes if sensitive data is detected. It safeguards your repository by catching leaks before they reach remote branches.

What's the best way to enforce conventional commit formatting in Git?

Conventional commits standardize your message format using commit types (feat, fix, docs) and human-readable descriptions via HEREDOC syntax. This Skill enforces the format automatically, improving commit history readability and maintainability.

How can I prevent accidental force pushes to main or master?

This Skill blocks force pushes to protected branches like main and master, and requires an explicit 'push' keyword before any push operation. It protects your codebase from destructive overwrites and unintended history rewrites.

Can I automate Git workflow validation across local and remote repositories?

Yes, this Skill enforces safe Git workflows by validating commits, scanning for secrets, and preventing unsafe operations across both local and remote repositories. It applies atomic-commit requirements and safeguards for all destructive commands.

Why should commits be validated before pushing changes?

Pre-push validation catches security issues, formatting violations, and unintended changes early, preventing bad commits from reaching the remote repository. It ensures clean, secure, and auditable commit history before code is shared.