From majestic-engineer
Stages unstaged changes if needed and creates a git commit with conventional commit format (feat, fix, docs, etc.). Uses arguments as optional message hint.
npx claudepluginhub majesticlabs-dev/majestic-marketplace --plugin majestic-engineersonnetgit/## Context - Current git status: !`git status` - Staged changes: !`git diff --cached` - Unstaged changes: !`git diff` - Current branch: !`git branch --show-current` - Recent commits: !`git log --oneline -5 2>/dev/null || echo "(no commits yet)"` ## Workflow Create a git commit using conventional commit format: **Types:** `feat`, `fix`, `docs`, `style`, `refactor`, `test`, `chore` Stage changes if needed, then commit. Use HEREDOC for multi-line messages: If `$ARGUMENTS` is provided, use it as hint for the commit message.
/commitCreates a conventional git commit with auto-generated message from staged changes. Supports types like feat, fix; accepts optional scope or message hint.
/commitReviews repo changes via git status and diff, prepares logical conventional commits, stages files, and executes git commits.
/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.
/commitCommits git changes with auto-generated Conventional Commits semantic message. Analyzes diffs, optionally stages unstaged files, confirms message, executes commit, and offers to push. Accepts optional custom message.
/commitCommits staged changes with descriptive messages in conventional commit format using emoji prefixes (e.g., ✨ feat:, 🐛 fix:, ♻️ refactor:). Runs git status and git commit -m.
/commitAnalyzes staged git changes, generates a conventional commit message, seeks user approval, and executes the commit without trailers.
Share bugs, ideas, or general feedback.
git statusgit diff --cachedgit diffgit branch --show-currentgit log --oneline -5 2>/dev/null || echo "(no commits yet)"Create a git commit using conventional commit format:
<type>(<scope>): <description>
Types: feat, fix, docs, style, refactor, test, chore
Stage changes if needed, then commit. Use HEREDOC for multi-line messages:
git commit -m "$(cat <<'EOF'
type(scope): description
optional body
EOF
)"
If $ARGUMENTS is provided, use it as hint for the commit message.