commit

Review git diffs and create Conventional Commits from staged changes.

4|Updated Feb 9, 2021
One-click install
npx skills add https://github.com/breengles/poor-man-OS-setup --skill commit-breengles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/breengles/poor-man-OS-setup/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/breengles/poor-man-OS-setup --skill commit-breengles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you create well-formatted git commits that follow Conventional Commits, reducing ambiguity and improving changelog quality during development.

Core Features & Use Cases

  • Staged/unstaged change review: Inspects both what’s staged and what isn’t using git diff and git diff --cached to ensure commits reflect the right scope.
  • Semantic commit composition: Splits work into logical, separable commits (e.g., feature vs. fix) when changes can be cleanly separated without producing broken intermediate states.
  • Safety guardrails: Avoids committing secrets and focuses strictly on changes made during the current session rather than pre-existing uncommitted work.

Quick Start

Review the diffs for the current session and create appropriately scoped Conventional Commits by following the commit instructions in this skill.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commits from staged and unstaged git changes?

The Skill inspects staged and unstaged git diffs to selectively stage changes into logical semantic commits. This process ensures your git history follows conventional commit conventions reliably without mixing unrelated modifications.

What is the best way to split mixed git changes into semantic commits?

The best way to split mixed changes is by reviewing git diff and git diff --cached to group modifications logically. The Skill separates work into feature or fix commits only when changes can be split without producing broken intermediate code states.

Does this skill commit pre-existing uncommitted work in my repository?

No, it strictly limits commits to changes made during the current development session. It applies safety guardrails to prevent committing pre-existing uncommitted work, ensuring only relevant session modifications are included in the semantic commits.

Can I use this to prevent secrets from being included in git commit history?

Yes, the Skill includes safety guardrails designed to prevent secrets from being committed. When inspecting git diffs and selectively staging changes, it actively avoids including sensitive data in your semantic conventional commits.

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

Conventional commits reduce ambiguity and improve changelog quality during development. By applying semantic commit composition, the Skill formats your git history logically, making version control changes easier to track, review, and automate.

When should I not use semantic commit composition for my code review?

Avoid semantic commit composition when changes cannot be cleanly separated without producing broken intermediate states. If splitting modifications results in unstable or non-functioning code, the Skill will not force a logical separation into feature or fix commits.