Menu
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
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.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/mhenke/claude-code-unplugged --skill commit-commandsThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for coding assistant plugins.
Automated PR and code reviewer guidelines
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for coding assistant.
Based on SOC occupation classification
Showing SKILL.md
| name | commit-commands |
| description | Git commit and repository workflows |
Streamline your git workflow with simple commands for committing, pushing, and creating pull requests.
The Commit Commands Plugin automates common git operations, reducing context switching and manual command execution. Instead of running multiple git commands, use a single slash command to handle your entire workflow.
commitCreates a git commit with an automatically generated commit message based on staged and unstaged changes.
What it does:
Usage:
/commit
Example workflow:
# Make some changes to your code
# Then simply run:
/commit
# Claude will:
# - Review your changes
# - Stage the files
# - Create a commit with an appropriate message
# - Show you the commit status
Features:
commit-push-prComplete workflow command that commits, pushes, and creates a pull request in one step.
What it does:
gh pr createUsage:
/commit-push-pr
Example workflow:
# Make your changes
# Then run:
/commit-push-pr
# Claude will:
# - Create a feature branch (if needed)
# - Commit your changes
# - Push to remote
# - Open a PR with summary and test plan
# - Give you the PR URL to review
Features:
gh) for PR creationRequirements:
gh) must be installed and authenticatedoriginclean_goneCleans up local branches that have been deleted from the remote repository.
What it does:
Usage:
/clean_gone
Example workflow:
# After PRs are merged and remote branches are deleted
/clean_gone
# Claude will:
# - Find all branches marked as [gone]
# - Remove any associated worktrees
# - Delete the stale local branches
# - Report what was cleaned up
Features:
When to use:
This plugin is included in the coding assistant repository. The commands are automatically available when using coding assistant.
commitcommit-push-prclean_gone# Write code
/commit
# Continue development
# Develop feature across multiple commits
/commit # First commit
# More changes
/commit # Second commit
# Ready to create PR
/commit-push-pr
# After several PRs are merged
/clean_gone
# Clean workspace ready for next feature
commit-push-pr: GitHub CLI (gh) must be installed and authenticatedcommit creates empty commitIssue: No changes to commit
Solution:
git status to verify changes existcommit-push-pr fails to create PRIssue: gh pr create command fails
Solution:
brew install gh (macOS) or see GitHub CLI installationgh auth loginclean_gone doesn't find branchesIssue: No branches marked as [gone]
Solution:
git fetch --prune to update remote trackingcommit during development, then commit-push-pr when readyclean_gone weekly to maintain a clean branch listAnthropic (support@anthropic.com)
1.0.0
clean_goneDescription: Cleans up all git branches marked as [gone] (branches that have been deleted on the remote but still exist locally), including removing associated worktrees.
You need to execute the following bash commands to clean up stale local branches that have been deleted from the remote repository.
First, list branches to identify any with [gone] status Execute this command:
git branch -v
Note: Branches with a '+' prefix have associated worktrees and must have their worktrees removed before deletion.
Next, identify worktrees that need to be removed for [gone] branches Execute this command:
git worktree list
Finally, remove worktrees and delete [gone] branches (handles both regular and worktree branches) Execute this command:
# Process all [gone] branches, removing '+' prefix if present
git branch -v | grep '\[gone\]' | sed 's/^[+* ]//' | awk '{print $1}' | while read branch; do
echo "Processing branch: $branch"
# Find and remove worktree if it exists
worktree=$(git worktree list | grep "\\[$branch\\]" | awk '{print $1}')
if [ ! -z "$worktree" ] && [ "$worktree" != "$(git rev-parse --show-toplevel)" ]; then
echo " Removing worktree: $worktree"
git worktree remove --force "$worktree"
fi
# Delete the branch
echo " Deleting branch: $branch"
git branch -D "$branch"
done
After executing these commands, you will:
If no branches are marked as [gone], report that no cleanup was needed.
commit-push-prDescription: Commit, push, and open a PR
git status with your bash tool)git diff HEAD with your bash tool)git branch --show-current with your bash tool)Based on the above changes:
gh pr createcommitDescription: Create a git commit
git status with your bash tool)git diff HEAD with your bash tool)git branch --show-current with your bash tool)git log --oneline -10 with your bash tool)Based on the above changes, create a single git commit.
You have the capability to call multiple tools in a single response. Stage and create the commit using a single message. Do not use any other tools or do anything else. Do not send any other text or messages besides these tool calls.
Before executing commands or submitting reviews, you MUST output a structured XML <verification_gate> block evaluating the following checks:
conventions: All changes align with target guidelines. (PASS/FAIL)correctness: Verify code correctness and lack of logical bugs. (PASS/FAIL)Example output format:
<verification_gate>
<conventions>PASS</conventions>
<correctness>PASS</correctness>
</verification_gate>
Do not proceed until you have output this verification gate.