git-commit

Format git commit messages, stage atomic changes, and generate CalVer tags.

11|4|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/zrong/skills --skill git-commit-zrong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/zrong/skills/tree/main/git-commit
Command: npx skills add https://github.com/zrong/skills --skill git-commit-zrong

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the inconsistency and manual overhead associated with versioning and documenting git commits, ensuring that every change is traceable, atomic, and compliant with CalVer standards.

Core Features & Use Cases

  • CalVer Versioning: Automatically calculates and applies YY.WW.MICRO version tags based on repository history.
  • Atomic Commit Workflow: Enforces logical separation of changes to ensure the repository remains in a buildable state.
  • History Cleanup: Provides a structured, interactive process to squash and rebase commits before merging or opening pull requests.
  • Use Case: When finishing a complex feature, use this skill to split your work into clean, logical commits, generate a new CalVer tag, and format your commit messages with required metadata.

Quick Start

Use the git-commit skill to perform an atomic commit of the current changes and apply the next CalVer tag.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I automate git commit message formatting and CalVer tag generation?

Automating git commit message formatting and CalVer tag generation requires a script that calculates YY.WW.MICRO versions from repository history and enforces atomic change staging. This skill uses python3 to execute version calculation scripts and manage repository state.

What is the best way to enforce atomic commits and clean git history before a pull request?

Enforcing atomic commits and cleaning git history involves a structured, interactive process to squash and rebase commits before merging. This skill separates logical changes to ensure the repository remains buildable and applies standardized metadata tracking.

Do I need python3 and git to calculate and apply CalVer version tags?

Yes, you need python3 and git to calculate and apply CalVer version tags. These dependencies are required to execute the version calculation scripts that generate YY.WW.MICRO tags based on repository history and manage the repository state.

How does automated CalVer versioning calculate the next tag from repository history?

Automated CalVer versioning calculates the next tag by analyzing repository history to generate a YY.WW.MICRO version string. This ensures every change is traceable, atomic, and compliant with strict CalVer standards without manual overhead.

Can I split complex feature changes into logical commits while generating a new CalVer tag?

Yes, you can split complex feature changes into logical commits while generating a new CalVer tag. The skill enforces atomic change staging to separate changes logically, format commit messages with metadata, and apply the next calculated version tag.

Why does my git workflow require strict versioning and standardized metadata tracking?

Your git workflow requires strict versioning and standardized metadata tracking to solve the inconsistency and manual overhead associated with documenting commits. This ensures every change remains traceable, atomic, and compliant with CalVer standards.