commit-work

Create Conventional Commits with patch-based staging and pre-commit checks.

9|2|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/stephanj/claude-code-collections --skill commit-work-stephanj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-work
Source: https://github.com/stephanj/claude-code-collections/tree/main/skills/commit-work
Command: npx skills add https://github.com/stephanj/claude-code-collections --skill commit-work-stephanj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of messy, monolithic, or poorly documented git commits that make code reviews difficult and project history hard to navigate.

Core Features & Use Cases

  • Granular Staging: Uses patch staging to isolate specific changes within files, ensuring each commit contains only one logical unit of work.
  • Conventional Commits Enforcement: Automatically guides the creation of standardized commit messages that follow the type(scope): summary format.
  • Safety Guardrails: Performs pre-commit checks to prevent the inclusion of secrets, debug logs, or unrelated formatting changes.

Quick Start

Ask the assistant to commit your current work and follow the interactive prompts to stage and describe your changes.

Frequently Asked Questions about commit-work

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

FAQPage Schema
How do I create conventional commits with logical scoping for code review?

Conventional commits require isolating logical changes through patch-based staging and generating standardized type(scope): summary messages. This skill enforces granular scoping and structured messaging to prepare production-ready commits for code review readiness.

What is the best way to split monolithic git changes into granular commits?

Splitting monolithic git changes requires patch-based staging to isolate specific file modifications into logical units. This skill automates granular staging verification, ensuring each commit tracks only related changes without mixing unrelated formatting or debug logs.

Can I automatically prevent secrets and debug logs from being included in my git commits?

Preventing secrets and debug logs in git commits requires automated pre-commit safety guardrails that verify staged content. This skill performs checks to block secrets, debug logs, and unrelated formatting changes before generating the final commit message.

Does this conventional commits workflow require any external dependencies or git plugins?

This conventional commits workflow requires no external dependencies or git plugins to function. The skill operates independently to enforce patch-based staging and generate compliant commit messages without integrating additional version control extensions.

How do I stage specific parts of a file for a logical git commit?

Staging specific file parts for logical git commits requires patch-based staging to isolate individual changes within files. This skill automates verification of staged content, ensuring only the intended logical unit of work is included before generating the commit message.