commit-branch

Stages and commits working tree changes with a Conventional Commits message derived from the actual diff.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/muselesscreator/ui-skills --skill commit-branch-muselesscreator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-branch
Source: https://github.com/muselesscreator/ui-skills/tree/main/commit-branch
Command: npx skills add https://github.com/muselesscreator/ui-skills --skill commit-branch-muselesscreator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing honest, well-structured git commit messages is tedious, and vague messages erode repository history quality. This Skill inspects the real diff, composes a Conventional Commits message, stages only intentional source changes, and records a commit report — without pushing or opening a PR. ## Core Features & Use Cases - Diff-Derived Commit Messages: Reads git diff and git diff --cached to write an accurate Conventional Commits subject (feat, fix, refactor, etc.) and optional body bullets. - Noise Exclusion: Stages source changes while leaving .cursor/ and .claude/ tooling files unstaged, and refuses to create empty commits on a clean tree. - Commit Reporting: Writes a timestamped report with the commit hash, subject, committed files, and anything intentionally left unstaged, plus a runlog entry for cycle tracking. - Use Case: As the commit step of an automated workflow cycle, invoke it after making code changes to produce a clean, well-described commit and an auditable report — then let a separate step handle push and PR creation. ## Quick Start Commit my current branch's changes with a Conventional Commits message based on the actual diff, without pushing.

Frequently Asked Questions about commit-branch

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

FAQPage Schema
How do I generate a Conventional Commits message from my git diff?

Read the actual changes with git diff and git diff --cached, then write a subject in the form type(scope): summary under 72 characters using types like feat, fix, refactor, test, chore, docs, style, or perf. Add body bullets only when they explain what changed and why.

How to commit changes without pushing or opening a pull request?

Stage the intended files with git add and run git commit with the message, then stop. This Skill is explicitly commit-only: it never runs git push and never creates a PR, leaving those steps to a separate workflow stage.

Can I provide my own commit message instead of a generated one?

Yes. Pass an optional argument with your desired subject, and it will be used verbatim or as a strong hint instead of generating one from the diff. The staging, reporting, and no-push behavior remain unchanged.

What happens if there is nothing to commit in the working tree?

When git status shows a clean tree, the Skill writes a report noting there is nothing to commit and stops. It never creates an empty commit, keeping the repository history free of noise.

Why are .cursor and .claude files excluded from the commit?

Local tooling and permission files are non-code noise that should not enter source history. The staging step uses git pathspec exclusions for .cursor and .claude, though this can be adjusted if a repository legitimately tracks those directories.