skills.rest
jMerta
jMertaCOMMUNITY
Explore all skills by this author →
GitHub

commit-work

Split code changes into logical Conventional Commits with clear messages.

130|15|Updated Dec 14, 2025
Search Tags:#git#workflow#commit#staging#code-review#Conventional Commits
One-click install
npx skills add https://github.com/jMerta/codex-skills --skill commit-work-jmerta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-work
Source: https://github.com/jMerta/codex-skills/tree/main/commit-work
Command: npx skills add https://github.com/jMerta/codex-skills --skill commit-work-jmerta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers produce well-scoped, review-ready git commits by guiding you to review changes, segment work into logical units, and craft clear commit messages that adhere to Conventional Commits.

Core Features & Use Cases

  • Guided commit boundaries: identify logical groupings of changes across files and stages.
  • Conventional commit messages: enforce type (feat, fix, chore, etc.) and formatting for easier history navigation.
  • Safe, incremental commits: provide strategies for patch staging and incremental commits to minimize risk.

Quick Start

Provide a plan to split current changes into logical commits and generate conventional messages. Example: Split my changes into two commits: one for UI updates, one for bug fixes, with messages following the Conventional Commits format.

Frequently Asked Questions about commit-work

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

FAQPage Schema
How do I split multiple file changes into logical git commits?▼

To split changes into logical git commits, you review file diffs, group related modifications, stage them incrementally, and write distinct conventional commit messages for each scoped unit.

What is the Conventional Commits format for git commit messages?▼

The Conventional Commits format requires a type prefix like feat, fix, or chore, followed by a concise subject line, ensuring structured commit history for easier navigation and automated processing.

How do I write a concise commit message for a complex code review?▼

Writing a concise commit message for code review involves segmenting work into logical boundaries, applying Conventional Commits types, and keeping subject lines short to ensure review-ready submissions.

Does this workflow support patch staging for incremental commits?▼

Patch staging for incremental commits is supported, providing strategies to selectively stage file segments to minimize risk and maintain strict staging discipline.

When should I enforce staging discipline before committing code?▼

You should enforce staging discipline when changes span multiple files or logical boundaries, ensuring each commit remains well-scoped and isolated to reduce risk and simplify history navigation.

Related Skills

Explore More Software Engineering Skills→
bitsocialnetbitsocialnet
1

commit

Generates logical, formatted git commits from analyzed diffs and predefined scopes.

Official
Intermediate
bdsqqqbdsqqq
59

git-ship

Stage modified files, commit with conventional commits, and push to the remote repository.

Community
Intermediate
alinaqialinaqi
705

commit-hygiene

Enforce atomic commits and small pull requests with file and line count thresholds.

Community
Intermediate
DavidROliverBADavidROliverBA
49

commit

Stage and commit vault changes with UK English conventional commit messages.

Community
Intermediate