git-commit

Analyze staged changes and draft Conventional Commits with safety scans.

16|1|Updated Jan 2, 2026
One-click install
npx skills add https://github.com/bahayonghang/my-ai-cli-toolkit --skill git-commit-bahayonghang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/bahayonghang/my-ai-cli-toolkit/tree/main/skills/git-github-collaboration/git-commit
Command: npx skills add https://github.com/bahayonghang/my-ai-cli-toolkit --skill git-commit-bahayonghang

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill solves the challenge of maintaining a clean, consistent, and audit-ready Git history when working with AI agents, preventing messy commits and ensuring compliance with repository conventions.

Core Features & Use Cases

  • Atomic Commit Orchestration: Automatically plans and executes commits based on staged or working-tree changes, ensuring atomic boundaries.
  • Agent-Aware Metadata: Injects structured trailers like Agent-Task, Agent-Model, and audit-ready provenance markers, while enforcing Why-line requirements for critical changes.
  • Safety & Compliance: Performs pre-commit safety scans for secrets and large files, respects repository-specific commitlint rules, and handles complex scenarios like reformatting hooks or checkpoint-based workflows.

Quick Start

Use the git-commit skill to analyze my staged changes and draft a conventional commit message following the repository's established history.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I automate Conventional Commits for agent-based workflows?

You can automate Conventional Commits by analyzing staged or working-tree changes against repository-specific conventions, enforcing Why-line requirements, and injecting agent-aware metadata like Agent-Task and Agent-Model trailers for audit trails.

What is atomic commit orchestration in version control?

Atomic commit orchestration plans and executes commits based on staged or working-tree changes, ensuring atomic boundaries to maintain a clean, audit-ready Git history when working with AI agents.

How do I prevent AI agents from committing secrets or large binary artifacts?

To prevent committing secrets or large files, pre-commit safety scans are performed automatically to detect and block restricted artifacts before the version control history is updated.

Does the git-commit automation work with custom commitlint rules?

Yes, the automation respects repository-specific commitlint rules and handles complex scenarios such as reformatting hooks or checkpoint-based workflows to ensure compliance with established conventions.

Do I need python3 to orchestrate atomic Conventional Commits?

Yes, python3 is required as a dependency to run the scripts that orchestrate atomic change management and apply structured commit messages with agent-aware provenance markers.

What's the best way to enforce structured commit messages with audit trails?

The best way to enforce structured messages is by orchestrating atomic Conventional Commits that inject structured trailers like Agent-Task and audit-ready provenance markers while satisfying compliance constraints.