commit-work

Create scoped git commits with Conventional Commits and safety checks.

1|Updated Jun 8, 2024
One-click install
npx skills add https://github.com/michaelmechenko/dotfiles --skill commit-work-michaelmechenko
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-work
Source: https://github.com/michaelmechenko/dotfiles/tree/main/opencode/skill/commit-work
Command: npx skills add https://github.com/michaelmechenko/dotfiles --skill commit-work-michaelmechenko

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Git workflows often result in noisy, large commits that are hard to review. This skill ensures changes are scoped, reviewed, and safely shipped.

Core Features & Use Cases

  • Smart Commit Splitting: automatically segments changes into logical commits based on feature/refactor, backend/frontend, formatting vs logic, tests vs production code.
  • Conventional Commits Format: enforces the standard type(scope): short summary with optional BREAKING CHANGE footer.
  • Safety & Quality Checks: scans for secrets, debug logs, and unrelated churn before committing.
  • Patch Staging: supports selective staging (git add -p) for granular control.
  • Review-ready Deliverables: provides final commit messages and a short summary per commit.

Quick Start

Ask to split changes into logical commits and generate conventional commit messages for your current work.

Frequently Asked Questions about commit-work

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

FAQPage Schema
How do I split my working tree changes into logical git commits?

Split your working tree changes into logical git commits by segmenting diffs based on feature, refactor, or test boundaries. This skill automatically groups related changes and generates review-ready conventional commit messages for each segment.

What is the conventional commits format for git commit messages?

The conventional commits format structures git commit messages as type(scope): short summary, with an optional BREAKING CHANGE footer. This skill enforces that standard automatically, drafting compliant messages for your staged changes.

How do I use git add -p for selective patch staging?

Selective patch staging with git add -p lets you interactively choose specific hunks from your working tree to include in a commit. This skill supports granular patch staging to help scope your commits precisely before drafting messages.

How do I scan staged changes for secrets and debug logs before committing?

Scan staged changes for secrets, debug logs, and unrelated formatting churn before committing to ensure code quality. This skill validates your diff and blocks unsafe or noisy changes from entering the final git commit.

Can I generate multiple conventional commit messages for unrelated changes in one working tree?

Generate multiple conventional commit messages for unrelated changes by splitting the working tree into logical commits. This skill segments mixed edits like backend and frontend code, drafting a separate conventional commit message for each scoped change.

Does this git commit workflow require any external dependencies?

This git commit workflow requires no external dependencies, operating entirely within your standard software project environment. It uses native git commands to stage patches, validate changes, and produce review-ready commit messages.