smart-git-commit

Enforce an 11-phase git commit workflow with secret scanning and test gating.

7|Updated May 25, 2026
One-click install
npx skills add https://github.com/Zarl-prog/Smart-git-commit --skill smart-git-commit-zarl-prog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smart-git-commit
Source: https://github.com/Zarl-prog/Smart-git-commit/tree/main/skills/smart-git-commit
Command: npx skills add https://github.com/Zarl-prog/Smart-git-commit --skill smart-git-commit-zarl-prog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Most AI agents produce vague, unhelpful commit messages that make project history impossible to navigate. This Skill enforces a rigorous 11-phase workflow that ensures every commit is atomic, tested, secure, and documented with a clear business rationale.

Core Features & Use Cases

  • 5-Part Commit Format: Enforces a structured CONTEXT/CHANGE/WHY/IMPACT format for every commit, making git history readable and traceable.
  • Security & Quality Gates: Automatically runs secret scanning to prevent credential leaks and executes project-specific test suites before allowing any commit.
  • Atomic Splitting: Analyzes complex diffs and guides the user to split mixed changes into focused, atomic commits.
  • Use Case: Use this whenever you need to save work, push a feature, or create a PR to ensure your contributions meet professional open-source standards.

Quick Start

Trigger the smart git commit skill by asking your agent to commit your current changes to the repository.

Frequently Asked Questions about smart-git-commit

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

FAQPage Schema
How do I automate secure git commits with secret scanning and testing?

Automate secure git commits by triggering an 11-phase workflow that executes secret scanning and project-specific test gating before finalizing any changes. This prevents credential leaks and ensures code quality across all commits, pushes, and pull requests.

What is the best way to format git commit messages for project traceability?

The best way to format git commit messages is using a standardized 5-part CONTEXT/CHANGE/WHY/IMPACT format. This structured approach ensures every commit is human-readable, atomic, and clearly documents the business rationale behind the change.

How do I split complex mixed git diffs into focused atomic commits?

Split complex mixed git diffs into atomic commits by running an automated diff analysis phase. This process evaluates your staged changes and guides you to separate mixed modifications into focused, individual commits that meet professional open-source standards.

Do I need the gh CLI to enforce an automated git commit workflow?

Yes, you need the gh CLI installed as a dependency to enforce this automated git commit workflow. The tool relies on this environment prerequisite to execute secure, traceable version control operations across diverse development environments.

Can I use this structured git commit process for version tagging and pull requests?

Yes, you can use this structured git commit process for version tagging, pushes, and pull requests. The 11-phase workflow applies comprehensively across all git operations to maintain a secure and traceable project history.