Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From claude-scholar
Stages 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.
npx claudepluginhub galaxy-dawn/claude-scholar --plugin claude-scholarHow this command is triggered — by the user, by Claude, or both
Slash command
/claude-scholar:commitThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Commit Stage and commit changes using Conventional Commits format. ## Instructions 1. **Check Git Status** - Run `git status` to review all changes - Run `git diff` to inspect modifications 2. **Analyze Changes** - Review changed files and their content - Determine commit type and scope - Draft a concise commit message 3. **Commit Type Reference** 4. **Commit Message Format** - Subject: imperative mood, no period, max 72 chars - Body: explain what and why (optional for small changes) - Scope: affected module (data, model, config, trainer, utils, workf...
/commitStages and commits changes from the current session with a conventional commit message and co-author attribution.
/commitAnalyzes staged git changes, generates a conventional commit message, seeks user approval, and executes the commit without trailers.
/commitCommits git changes following best practices for staging, conventional messages, and hooks using the git:commit skill.
/commit-generatorGenerates a conventional commit message for staged changes, shows it for approval, commits, and optionally pushes to remote.
/commitAnalyzes git changes to generate conventional commit messages, stages files appropriately, runs pre-commit checks like linting and tests, and creates atomic commits.
/git-commitCreates conventional git commits with emojis, auto-stages unstaged files if needed, analyzes diffs, detects multiple logical changes, and suggests splitting into atomic commits.
Share bugs, ideas, or general feedback.
Stage and commit changes using Conventional Commits format.
Check Git Status
git status to review all changesgit diff to inspect modificationsAnalyze Changes
Commit Type Reference
feat - New feature
fix - Bug fix
docs - Documentation only
style - Code style (formatting, semicolons, etc.)
refactor - Code refactoring (no feature/fix)
perf - Performance improvement
test - Adding or updating tests
chore - Build, CI, tooling, dependencies
Commit Message Format
<type>(<scope>): <subject>
<body>
Stage and Commit
git addCo-Authored-By footers unless the user explicitly asks for themgit log --oneline -1/update-github to also push.