// Create git commits with optional intelligent grouping, push, and PR creation. Use when committing changes — standard single commit, logically grouped commits, pushing, or creating a PR.
| name | commit |
| description | Create git commits with optional intelligent grouping, push, and PR creation. Use when committing changes — standard single commit, logically grouped commits, pushing, or creating a PR. |
| argument-hint | [group] [pr] [push [branch]] |
| allowed-tools | ["Bash","Read","Grep","Glob","AskUserQuestion"] |
| hooks | {"PreToolUse":[{"matcher":"Bash","hooks":[{"type":"command","command":"[ -f vendor/bin/pint ] && vendor/bin/pint --dirty || true","once":true}]}]} |
Create git commits with optional intelligent grouping of changes.
/mella:commit — Standard commit/mella:commit group — Analyze and group changes into logical commits/mella:commit pr — Commit and use existing PR (or ask to create one)/mella:commit push — Commit and push to current branch/mella:commit push origin/feature-branch — Commit and push to specific branch/mella:commit group pr push — Combine all optionsCheck $ARGUMENTS for flags: group, pr, push. For push, extract the next token as the target branch if present.
Run git status, git diff, and git log -5 --oneline to understand changes and commit style. Draft a conventional commit message, stage relevant files with git add, commit, then verify with git status.
git status + git diff HEAD + Read each changed file.git add <files> → conventional commit message → commit → verify.git log --oneline -n <N> and git status to confirm all changes committed.| Group | Files | Message |
|---|---|---|
| Dependencies | package.json, composer.json | "Update dependencies" |
| Feature | src/Controllers/UserController.php, src/Middleware/AuthMiddleware.php | "Add authentication middleware" |
| Tests | tests/AuthTest.php | "Add authentication tests" |
Run gh pr view --json number,title,url:
gh pr create --fill and display the new PR URL.After all commits are created, push:
push: git push origin HEAD:<branch>git pushIf push fails, explain the error and suggest git push -u origin <branch> for new branches.
--amend, --force, or other destructive operations.Comprehensive code review that runs all installed review skills in parallel and consolidates findings into one actionable report. Use any time a user wants their code, diff, or branch reviewed — triggers on: "check my changes", "look over my diff", "review this before I merge", "anything look off?", "second set of eyes", "review PR #N", or pre-PR sanity checks. Use for code review intent — not for git help, writing PR descriptions, or explaining diffs.
Deep-dive codebase analysis that generates innovative, high-leverage feature ideas and improvements. Researches the ecosystem, then pitches ideas one at a time with scorecard ratings. Accepts an optional count and brief: /pitch [N] [brief]. Use when the user asks "what should I build next?", "pitch me ideas", "what's the smartest thing to add?", "innovate on this codebase", "suggest features", or runs /pitch. Works on any language, framework, or project type.
Deep competitive intelligence for any product. Reads the current project's code and documentation to understand what the product does, then searches the web for competitors and visits each competitor's site live to research pricing, features, copywriting, design, and positioning. Use when the user asks for competitor research, competitive landscape, market analysis, "who are our competitors", or wants to compare their product against alternatives. Produces either a structured Markdown report or an interactive self-contained HTML dashboard. Persists findings to .claude/competitor-data.yaml for use by other skills.
Triage a review bot's comments on a GitHub PR. Re-reviews each comment against the actual code, applies valid fixes, dismisses false positives, and posts a summary comment on the PR. Use when asked to "handle the bot review", "triage bot comments", "check the bot's feedback", or "review the bot review on PR #N".
Generate step-by-step walkthrough guides for testing features or bug fixes. Auto-detects code changes from git diff or PR. Use when the user asks to create testing instructions, QA documentation, or says "write a walkthrough" after implementing a feature.