commit-code

Splits working tree changes into themed git commits with conventional commit messages.

1|Updated Sep 13, 2026
One-click install
npx skills add https://github.com/silentFellow/public-dotfiles --skill commit-code-silentfellow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-code
Source: https://github.com/silentFellow/public-dotfiles/tree/main/agents/skills/commit-code
Command: npx skills add https://github.com/silentFellow/public-dotfiles --skill commit-code-silentfellow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a messy working tree full of mixed changes into clean, meaningful git commits is tedious and error-prone. This Skill clusters diffs by theme, stages hunks precisely, and writes commit messages that match the repository's existing conventions. ## Core Features & Use Cases - Theme-Based Clustering: Groups changed hunks by purpose rather than by file, operation type, or directory, producing a commit graph of working states. - Hunk-Level Staging: Uses git add -p and hand-edited patches to split files or even single hunks that mix unrelated themes. - Convention-Aware Messages: Reads git log and branch names to match existing styles, layering ticket prefixes with conventional commit types and structured nested-bullet bodies. - Use Case: You modified install scripts, configs, and env files for two different tools in one session. The Skill proposes two themed commits, stages the right hunks for each, and asks how to handle leftover untracked files instead of deciding silently. ## Quick Start Ask the assistant to turn the current working tree changes into well-organized git commits split by theme.

Frequently Asked Questions about commit-code

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

FAQPage Schema
How do I split a large git diff into multiple commits?▼

Group changed hunks by theme or purpose rather than by file. Use git add -p to stage only the hunks belonging to each theme, then commit each cluster separately with its own message.

How to stage only part of a file in git?▼

Use git add -p to interactively select individual hunks from a file. If a single hunk mixes two themes and cannot be split with s, use the manual hunk-edit option e or git apply --cached with a hand-edited patch.

Should I write conventional commit messages for every repo?▼

Check the repository's existing conventions first with git log and the branch name. If prior commits use a ticket prefix or different style, match that pattern and layer conventional commit types on top only when appropriate.

When should a commit message include a body?▼

Include a body whenever the commit contains more than one specific change worth naming. Use nested bullets with backticked file or feature names, and skip the body only when it would merely repeat the subject.

What should I do with untracked files when committing?▼

Ask whether each untracked file should be staged into a commit, left untracked, or excluded via .gitignore or .git/info/exclude. Only skip asking when the file is clearly build output already covered by an existing ignore pattern.