skills.rest
monamaret
monamaretCOMMUNITY
Explore all skills by this author →
GitHub

commit-work

Create scoped git commits with Conventional Commit messages and validation.

Updated Apr 26, 2026
Search Tags:#git#code review#version control#conventional commits#staging#commit message#branch hygiene
One-click install
npx skills add https://github.com/monamaret/rook-reference --skill commit-work-monamaret
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-work
Source: https://github.com/monamaret/rook-reference/tree/main/.tabnine/agent/skills/commit-work
Command: npx skills add https://github.com/monamaret/rook-reference --skill commit-work-monamaret

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents messy, hard-to-review pull requests by helping you create well-scoped git commits with consistent, Conventional Commit messages.

Core Features & Use Cases

  • Safe commit preparation: inspects the working tree and staged changes to ensure only intended diffs are included.
  • Logical splitting: guides splitting work into multiple commits by feature/refactor boundaries and mixed-file scenarios (including patch staging).
  • Conventional Commit messaging: produces imperative, specific headers with required formatting and optional BREAKING CHANGE footers.
  • Validation before repeat: recommends the smallest relevant check (tests, lint, or build) before proceeding to the next commit.

Quick Start

Use the commit-work skill to generate one or more Conventional Commit messages for the changes you plan to stage, including the commands you should run to review git diff --cached and any quick verification to run before committing.

Frequently Asked Questions about commit-work

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

FAQPage Schema
How do I split mixed or large git changes into multiple safe commits?▼

To split mixed git changes into safe commits, inspect the working tree and stage specific hunks logically by feature or refactor boundaries. This ensures only intended diffs are included, making history clearer and code review faster.

What is the conventional commit format for git commit messages?▼

Conventional commit format requires an imperative type(scope): summary header. This Skill generates these messages for your staged changes, optionally adding BREAKING CHANGE footers to ensure consistent and specific git history.

Can I stage specific file hunks before creating a conventional commit?▼

Yes, you can stage specific file hunks. This Skill inspects the working tree and guides patch staging to ensure only the correct, intended diffs are included before generating a commit message.

What's the best way to verify code before repeating multiple git commits?▼

The best way to verify code before repeating multiple git commits is to run the smallest relevant check, such as tests, lint, or build. This Skill recommends the appropriate validation before proceeding to the next commit.

Why does staging all modified files at once lead to messy pull requests?▼

Staging all modified files at once leads to messy pull requests because unrelated changes are grouped together. This Skill prevents this by guiding logical splitting and patch staging to create well-scoped commits.

Related Skills

Explore More Software Engineering Skills→
thoreinsteinthoreinstein
5

commit

Analyze git diffs to plan atomic commits with grouped files and messages.

Community
Basic
JaimeJunrJaimeJunr
2

ship

Automate commits, branch creation, and pull request generation.

Community
Advanced
tkerseytkersey
66

commit

Create small Git commits with validation signals before finalizing.

Community
Intermediate
chijunzhengchijunzheng

tdd-committer

Verify tests, stage files, and create conventional commits in Git.

Community
Advanced