commit

Enforce one-issue-per-commit with conventional commit formats and passing tests.

16|2|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/hojinzs/github-symphony --skill commit-hojinzs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/hojinzs/github-symphony/tree/main/.codex/skills/commit
Command: npx skills add https://github.com/hojinzs/github-symphony --skill commit-hojinzs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit discipline is critical to maintain a readable, navigable project history; this skill ensures every commit is purposeful, small, and verifiable.

Core Features & Use Cases

  • Enforces one-issue-per-commit to keep changes isolated
  • Promotes conventional commit formats for clear tokens like feat, fix, docs
  • Validates that tests pass before committing to prevent broken states

Quick Start

Start by composing a small, focused commit that adds a single logical change and passes all tests.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I enforce conventional commit formats in my git workflow?

Enforce conventional commit formats by applying a commit discipline skill that validates messages for clear tokens like feat, fix, and docs before allowing a commit. This ensures consistent messaging and a readable, navigable project history.

What is the best way to keep git commits clean and focused on a single issue?

Keeping git commits clean and focused requires enforcing a one-issue-per-commit rule. This isolates logical changes, ensuring each commit represents a single purposeful update such as a feature, bug fix, or refactor.

Can I prevent broken intermediate states when committing code changes?

Yes, you can prevent broken intermediate states by requiring tests to pass before committing. This validates a verifiable, ship-ready state across your feature work, bug fixes, and refactors, forbidding broken code from entering repository history.

How do I write a conventional commit message for a bug fix or feature?

Writing a conventional commit message involves using specific tokens like fix for bug fixes or feat for new features, followed by a concise description. This enforces clear messaging and improves code quality by categorizing commit intent.

Does enforcing one-issue-per-commit work for refactoring and feature work?

Enforcing one-issue-per-commit works across feature work, bug fixes, and refactors by ensuring every commit is small and logically scoped. It maintains repository history quality by keeping changes isolated and purposeful.