commit

Format git commits using the project's phase-task convention.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/cooper538/eshop-demo --skill commit-cooper538
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/cooper538/eshop-demo/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/cooper538/eshop-demo --skill commit-cooper538

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill formats git commits following the project's phase-task convention and guides the user through staging and messaging.

Core Features & Use Cases

  • Interactive commit mode with phase/task detection from branch names or recent commits.
  • Meta commits support using the [00-00] prefix for infrastructure changes.
  • Enforce a structured commit template and provide guidance to generate meaningful messages.

Quick Start

Run /commit in interactive mode, or use /commit feat add user authentication to create a properly formatted commit.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate structured git commits with a phase-task convention?

You can automate structured git commits by running an interactive command that enforces a phase-task template. The system detects phase and task details from branch names or recent commits, analyzes diffs to suggest messages, and requires user confirmation before execution.

What is a meta commit in git and when should I use the [00-00] prefix?

A meta commit is an infrastructure change formatted with a [00-00] prefix. You use this structured prefix when making foundational updates that do not fit standard phase-task feature categories but still require tracking within the project's commit convention.

How do I generate a properly formatted git commit message from staged changes?

To generate a properly formatted git commit message, the system analyzes your staged diffs and applies a structured template. It guides you through staging and messaging by suggesting phase-task compliant text based on the detected code changes.

Can I manually specify phase and task details instead of relying on automatic branch detection?

Yes, you can manually specify phase and task details instead of relying on automatic branch detection. By passing arguments directly in the command line, you bypass the interactive detection from recent commits and explicitly define the structured commit context.

What is the best way to enforce a consistent commit template across a development team?

The best way to enforce a consistent commit template is to use an automated formatting tool that applies a strict phase-task convention. This ensures every commit follows the structured format by analyzing diffs and standardizing the output before execution.