commit

Create Git commits with emoji, type, and scope following team conventions.

7|1|Updated Mar 2, 2022
One-click install
npx skills add https://github.com/Purushot14/user-agent-parser --skill commit-purushot14
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Purushot14/user-agent-parser/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/Purushot14/user-agent-parser --skill commit-purushot14

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates and enforces well-formatted Git commits that clearly communicate intent, improving history readability and team alignment.

Core Features & Use Cases

  • Emoji, type, and scope: Enforces a structured commit message format with standardized signals.
  • Mandatory review workflow: Guides users through a review step to auto-fix issues before commit.
  • Audit-friendly history: Produces consistent commits that streamline code review and project tracing.

Quick Start

Run /review to auto-fix issues, then run /commit to generate a standardized commit message.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate conventional commits with emoji, type, and scope?

You can automate conventional commits by running a guided workflow that reviews context, groups changes, stages them, and generates a message with standardized emoji, type, and scope. This enforces team conventions and improves history readability.

What is the best way to enforce a review-driven git workflow before committing?

To enforce a review-driven git workflow, run a mandatory review step to auto-fix issues before staging. This process guides changes from review through staging to a finalized commit to ensure code quality and alignment.

How do I group and stage code changes for a structured git commit?

Group and stage code changes by following a multi-step process that gathers context, groups related modifications, and stages them before creating the commit. This targets feature work, bug fixes, and maintenance effectively.

Does this conventional commit workflow support feature branches and bug fixes?

Yes, this conventional commit workflow supports feature work, bug fixes, and maintenance. It provides deterministic guidance and guardrails to ensure changes are properly reviewed, staged, and committed across various development tasks.

Why use a multi-step process for creating git commit messages?

Use a multi-step process for git commit messages to ensure deterministic guidance and guardrails. This enforces a structured format with emoji, type, and scope, producing audit-friendly history that streamlines code review and project tracing.

Can I auto-fix code review issues before staging a git commit?

Yes, you can auto-fix code review issues before staging by running a dedicated review step. This action resolves problems prior to grouping and staging changes for the finalized conventional commit.