skills.rest
whinc
whincCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

commit-work

Inspect working tree changes, stage them selectively, and generate Conventional Commits messages.

39|3|Updated Mar 7, 2026
Search Tags:#git#workflow#commit#staging#code-review#version-control#conventional-commits
One-click install
npx skills add https://github.com/whinc/super-skills --skill commit-work-whinc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-work
Source: https://github.com/whinc/super-skills/tree/main/.agents/skills/commit-work
Command: npx skills add https://github.com/whinc/super-skills --skill commit-work-whinc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps developers create well-scoped commits by reviewing changes, dividing them into logical units, and generating clear, conventional messages.

Core Features & Use Cases

  • Inspects working tree and suggests commit boundaries.
  • Stages changes selectively and crafts Conventional Commits messages.
  • Verifies and delivers review-ready commits with minimal risk.

Quick Start

Tell me to commit the current changes with logical boundaries using Conventional Commits.

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 git changes into logical commits using Conventional Commits?▼

To split mixed git changes, this skill inspects the working tree, suggests logical commit boundaries, selectively stages patches, and generates Conventional Commits-compliant messages for safe review.

What is the best way to generate Conventional Commits messages for multiple staged changes?▼

Generating Conventional Commits messages is handled by inspecting staged changes, partitioning them into logical units, and crafting clear messages to ensure review-ready commits with minimal merge risk.

How does patch staging work when separating feature updates from documentation fixes?▼

Patch staging separates feature updates from documentation fixes by inspecting the working tree, selectively staging specific changes, and verifying boundaries before finalizing each logical commit.

When do I need to partition working tree changes before committing?▼

You need to partition working tree changes when mixed updates across features, fixes, and dependencies require careful division into logical commits to enforce Conventional Commits format and ensure safe merges.

Can I use this workflow to verify changes before finalizing git commits?▼

Yes, you can use this workflow to verify changes before finalizing git commits, as it performs end-to-end commit orchestration that reviews staged patches and enforces Conventional Commits formatting for safe delivery.

Does this approach support reviewing code changes across features and dependencies?▼

Yes, this approach supports reviewing code changes across features and dependencies by inspecting mixed updates, dividing them into logical units, and generating clear conventional messages for review-ready commits.

Related Skills

Explore More Software Engineering Skills→
GLaDO8GLaDO8

smartcommit

Generates concise Git commit messages and commits staged or unstaged changes.

Community
Basic
bswrundquistbswrundquist

commit-and-push

Commit staged changes using conventional commits and push them to the remote repository.

Community
Basic
Hey-DigaHey-Diga
16

merge-to-staging

Merge the current feature branch into a fresh staging branch with automated conflict analysis.

Official
Advanced
channingwaltonchanningwalton
3

Commit Helper

Generate conventional commit messages from staged git diffs.

Community
Intermediate