Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From rpi
Stages and commits changes with user-approved messages, grouping related files into logical atomic commits without Claude attribution.
npx claudepluginhub hoblin/claude-ruby-marketplace --plugin rpiHow this command is triggered — by the user, by Claude, or both
Slash command
/rpi:commitThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Commit Changes You are tasked with creating git commits for the changes made during this session. ## Process: 1. **Think about what changed:** - Review the conversation history and understand what was accomplished - Run `git status` to see current changes - Run `git diff` to understand the modifications - Consider whether changes should be one commit or multiple logical commits 2. **Plan your commit(s):** - Identify which files belong together - Draft clear, descriptive commit messages - Use imperative mood in commit messages - Focus on why the changes were mad...
/commitReviews session changes via git status/diff, proposes atomic commits with messages, creates them upon user approval without Claude attribution.
/commitReviews session changes with git status/diff, plans atomic commits with descriptive messages, seeks user confirmation, then stages files and commits.
/commitStages and commits changes from the current session with a conventional commit message and co-author attribution.
/commit-generatorGenerates a conventional commit message for staged changes, shows it for approval, commits, and optionally pushes to remote.
/commitStages changes and commits locally using Conventional Commits format. Analyzes git status/diffs, drafts typed message with scope, confirms with user before git add and commit.
/SKILLCreates a conventional git commit using git-agent with intent from conversation, optionally co-authored by Claude model from argument.
Share bugs, ideas, or general feedback.
You are tasked with creating git commits for the changes made during this session.
Think about what changed:
git status to see current changesgit diff to understand the modificationsPlan your commit(s):
Present your plan to the user:
Execute upon confirmation:
git add with specific files (never use -A or .)git log --oneline -n [number]