git-commit

Generate conventional git commit messages with automatic file staging and secret detection.

Updated May 7, 2026
One-click install
npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill git-commit-tmalcolm-0607
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/tmalcolm-0607/mad-council-claw/tree/main/.claude/skills/git-commit
Command: npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill git-commit-tmalcolm-0607

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the hassle of manually formatting git commits to match conventional standards, ensuring consistent, readable commit history across your project without needing to memorize commit formatting rules.

Core Features & Use Cases

  • Conventional Commit Formatting: Automatically generates commit messages following the standard type/scope/subject structure (using prefixes like feat, fix, docs, etc.) to maintain consistent project commit history.
  • Built-in Safety Guardrails: Prevents common destructive git mistakes including amending public commits, force pushing, skipping pre-commit hooks, and accidentally committing secrets or sensitive files.
  • Use Case: A developer finishing a bug fix can use this skill to automatically stage relevant changed files, generate a properly formatted commit message with co-author attribution, and create the commit without manual formatting work or risk of including sensitive files.

Quick Start

Invoke the git-commit skill to automatically generate and create a properly formatted conventional commit for all current changes in your repository.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I automatically generate conventional commit messages for my git changes?

You can automatically generate conventional commit messages by invoking the git-commit skill, which analyzes your repository changes and creates a compliant commit using the standard type, scope, and subject structure without manual formatting.

What is the best way to prevent accidentally committing secrets or sensitive files in git?

To prevent committing secrets in git, the git-commit skill includes built-in safety guardrails that automatically detect sensitive files and credentials, blocking them from being staged and committed to your repository.

How do I enforce conventional commit standards across my software development workflow?

You can enforce conventional commit standards by using the git-commit skill to automate change categorization and generate compliant commit messages, ensuring consistent and readable project commit history for your team.

Can I automatically stage relevant changed files and create a git commit in one step?

Yes, you can automatically stage relevant changed files and create a git commit in one step by invoking the git-commit skill, which handles file staging, message generation, and compliant commit creation simultaneously.

Does this git commit tool have safety guardrails against destructive operations like force pushing?

The git commit tool includes safety guardrails against destructive git operations, specifically preventing public commit amendments, force pushes, and skipped pre-commit hooks to protect your repository history.

What are the limitations of automating conventional commit formatting?

While automating conventional commit formatting eliminates inconsistent messages and prevents destructive git operations, it is designed specifically for software engineering workflows enforcing conventional commit standards and does not support non-standard commit formats.