Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
npx claudepluginhub killerapp/mem8-plugin --plugin mem8How this command is triggered — by the user, by Claude, or both
Slash command
/mem8:commitThis command is limited to the following tools:
The 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 with git status/diff, plans atomic commits with descriptive messages, seeks user confirmation, then stages files and commits.
/commitStages and commits changes with user-approved messages, grouping related files into logical atomic commits without Claude attribution.
/commitReviews session changes via git status/diff, proposes atomic commits with messages, creates them upon user approval without Claude attribution.
/commitStages and commits changes from the current session with a conventional commit message and co-author attribution.
/commitStages relevant git changes and creates logical commits with conventional format (type(scope): subject). Supports --push, --all, and scope filter.
/commitStages unstaged changes based on git status and diff analysis, then creates a commit with a generated message. Uses current branch and recent commit history for context.
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]