Menu
Write a commit message and create a git commit. Use when the user wants to commit changes, asks for a commit message, or says "commit this" or "make a commit".
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when the user wants to name or rename something — a product, feature, brand, project, command, or company — or asks to "brainstorm names", "find a better name", "naming ideas", or invokes /brainstorming-names.
Use when a task has a large solution space and a measurable quality signal and the goal is to generate many candidates and select the best — naming/branding, UX/UI variants, marketing copy, code optimization, prompt tuning. Triggers: "brainstorm and pick the best", "explore and exploit", "simulated annealing", "tournament of options", "generate N options and rank them", iterate-until-score loops, or /explore-exploit.
Use when the user asks to rate, score, judge, critique with a number, or "how good is" an artifact — a live website/UI, a markdown draft (blog post, README, plan, docs), or code/a diff — or invokes /score, or sets up an iterate-until-score-N feedback loop (e.g. with /goal "repeat until 9/10").
Start work on a Linear issue end-to-end — create a worktree, fetch issue context from Linear, implement the fix, then commit, push, and open a draft PR. Use when the user says "start issue", "work on STU-1234", "create a worktree and fix <Linear link>", "start a worktree for this ticket", or gives a Linear URL/issue id and wants the whole branch→PR flow.
Use when the user wants to undo, absorb, collapse, or reverse a git worktree — "undo worktree", "absorb worktree", "move worktree branch back to main repo", "remove worktree and checkout in main", "get rid of this worktree", or finish work in a ~/worktrees.nosync worktree and continue it in the main studio checkout.
This skill should be used when the user asks to "clean up my Mac", "free disk space", "my disk is full", "what's taking up space", "reclaim storage", "offload files", or wants to dedupe/archive backups and media to remote storage. Provides a scan → categorize → offload/clean → reclaim workflow with tested scripts and macOS-specific gotchas.
| name | commit |
| description | Write a commit message and create a git commit. Use when the user wants to commit changes, asks for a commit message, or says "commit this" or "make a commit". |
| user-invocable | true |
You are helping the user create a git commit with a well-crafted commit message.
Run these commands in parallel:
git status - See staged and unstaged filesgit diff --cached - See staged changesgit diff - See unstaged changesgit log --oneline -10 - See recent commit message styleAnalyze the changes:
Draft a commit message following these principles:
type: brief description or just brief descriptionStage any relevant unstaged files if needed (ask user first if unclear)
Create the commit:
git commit -m "$(cat <<'EOF'
Your commit message here.
Additional details if needed.
EOF
)"
CRITICAL: Run git status after committing to verify success
Co-Authored-By: in the commit message--amend unless explicitly requestedfeat: add dark mode toggle to settings
fix: prevent crash when API returns null user
refactor: extract validation logic into separate module
docs: update API authentication examples
test: add coverage for edge cases in parser
Match the repository's commit style by examining git log. Common patterns:
type(scope): descriptionAdapt to what you observe in the recent history.