commit-work

Guide staging and draft Conventional Commits messages for logical Git commits.

121|12|Updated Nov 16, 2022

Search Tags:#git #workflow #commit #code-review #version-control #conventional-commits

Ready to run

npx skills add https://github.com/bartstc/vite-ts-react-template --skill commit-work-bartstc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-work
Source: https://github.com/bartstc/vite-ts-react-template/tree/main/.agents/skills/commit-work
Command: npx skills add https://github.com/bartstc/vite-ts-react-template --skill commit-work-bartstc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Make commits that are easy to review and safe to ship: only intended changes are included, commits are logically scoped, and messages describe what changed and why, using Conventional Commits.

Core Features & Use Cases

Inspects the working tree to identify logical boundaries.
Guides staging to include only the next commit and drafts a standardized message.
Supports multi-commit workflows with a repeatable, auditable process.

Quick Start

Review your changes, stage the relevant hunks, and craft a conventional commit message for the next commit.

Frequently Asked Questions about commit-work

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

FAQPage Schema

How do I write conventional commits for split logical changes?▼

To write conventional commits for split logical changes, inspect the working tree to identify boundaries, stage only the relevant hunks, and draft a structured message. This enforces a stepwise workflow to maintain a clear project history.

What is the best way to stage only intended changes for a git commit?▼

The best way to stage only intended changes for a git commit is to inspect the working tree for logical boundaries and selectively stage specific hunks. This ensures only the next commit is included and changes are safe to ship.

How does a conventional commit workflow handle multi-commit reviews?▼

A conventional commit workflow handles multi-commit reviews by applying a repeatable, auditable process. It guides you through inspecting changes, staging relevant hunks, and validating changes with a checklist before committing each logical unit.

Can I use this commit workflow without installing external dependencies?▼

Yes, you can use this commit workflow without installing external dependencies. It operates independently to guide review, staging, and structured message drafting using Conventional Commits standards.

Why should I use conventional commits instead of plain git commit messages?▼

You should use conventional commits instead of plain git commit messages to make commits easy to review and safe to ship. Structured messages logically scope changes and describe what changed and why, maintaining a clear project history.