Git Operations
Default (No Arguments)
If invoked without arguments, use AskUserQuestion to present available git operations:
| Operation |
Description |
cm |
Stage files & create commits |
cp |
Stage files, create commits and push |
pr |
Create Pull Request |
merge |
Merge branches |
merge-pr |
Review, label, merge PRs, then watch/fix CI |
Present as options via AskUserQuestion with header "Git Operation", question "What would you like to do?".
Execute git workflows via git-manager subagent to isolate verbose output.
Activate mk-context-engineering skill.
IMPORTANT:
- Sacrifice grammar for the sake of concision.
- Ensure token efficiency while maintaining high quality.
- Pass these rules to subagents.
Arguments
cm: Stage files & create commits
cp: Stage files, create commits and push
pr: Create Pull Request [to-branch] [from-branch]
to-branch: Target branch (default: main)
from-branch: Source branch (default: current branch)
merge: Merge [to-branch] [from-branch]
to-branch: Target branch (default: main)
from-branch: Source branch (default: current branch)
merge-pr: Review, label, merge, and post-merge verify PRs
- Usage:
/mk-git merge-pr <PR numbers or URLs>
- Accepts one or more PR numbers or GitHub PR URLs
- Runs
/mk-review-pr <PR> --fix --reply before any label or merge
- Adds label
ready to ship only after review/fix/reply reports the PR is merge-ready
- Merges only reviewed-and-ready PRs, then watches target-branch CI to success
Quick Reference
| Task |
Reference |
| Commit |
references/workflow-commit.md |
| Push |
references/workflow-push.md |
| Pull Request |
references/workflow-pr.md |
| Merge |
references/workflow-merge.md |
| Merge PRs |
references/workflow-merge-pr.md |
| Standards |
references/commit-standards.md |
| Safety |
references/safety-protocols.md |
| Branches |
references/branch-management.md |
| GitHub CLI |
references/gh-cli-guide.md |
Core Workflow
Step 1: Stage + Analyze
git add -A && git diff --cached --stat && git diff --cached --name-only
Step 2: Security Check
Scan for secrets before commit:
git diff --cached | grep -iE "(api[_-]?key|token|password|secret|credential)"
If secrets found: STOP, warn user, suggest .gitignore.
Step 3: Split Decision
NOTE:
- Search for related issues on GitHub and add to body.
- Only use
feat, fix, or perf prefixes for files in .claude directory (do not use docs).
Split commits if:
- Different types mixed (feat + fix, code + docs)
- Multiple scopes (auth + payments)
- Config/deps + code mixed
- FILES > 10 unrelated
Single commit if:
- Same type/scope, FILES ≤ 3, LINES ≤ 50
Step 4: Commit
git commit -m "type(scope): description"
Output Format
✓ staged: N files (+X/-Y lines)
✓ security: passed
✓ commit: HASH type(scope): description
✓ pushed: yes/no
Error Handling
| Error |
Action |
| Secrets detected |
Block commit, show files |
| No changes |
Exit cleanly |
| Push rejected |
Suggest git pull --rebase |
| Merge conflicts |
Suggest manual resolution |
References
references/workflow-commit.md - Commit workflow with split logic
references/workflow-push.md - Push workflow with error handling
references/workflow-pr.md - PR creation with remote diff analysis
references/workflow-merge.md - Branch merge workflow
references/workflow-merge-pr.md - PR review, ready label, merge, and CI convergence workflow
references/commit-standards.md - Conventional commit format rules
references/safety-protocols.md - Secret detection, branch protection
references/branch-management.md - Naming, lifecycle, strategies
references/gh-cli-guide.md - GitHub CLI commands reference
1---2name: mk-git3description: Manage git commits, pushes, PRs, branch merges, and PR review-and-merge automation. Use for commit, push, PR creation, PR merge, CI follow-up, and secret scanning.4---56# Git Operations78## Default (No Arguments)910If invoked without arguments, use `AskUserQuestion` to present available git operations:1112| Operation | Description |13|-----------|-------------|14| `cm` | Stage files & create commits |15| `cp` | Stage files, create commits and push |16| `pr` | Create Pull Request |17| `merge` | Merge branches |18| `merge-pr` | Review, label, merge PRs, then watch/fix CI |1920Present as options via `AskUserQuestion` with header "Git Operation", question "What would you like to do?".2122Execute git workflows via `git-manager` subagent to isolate verbose output.23Activate `mk-context-engineering` skill.2425**IMPORTANT:**26- Sacrifice grammar for the sake of concision.27- Ensure token efficiency while maintaining high quality.28- Pass these rules to subagents.2930## Arguments31- `cm`: Stage files & create commits32- `cp`: Stage files, create commits and push33- `pr`: Create Pull Request [to-branch] [from-branch]34 - `to-branch`: Target branch (default: main)35 - `from-branch`: Source branch (default: current branch)36- `merge`: Merge [to-branch] [from-branch]37 - `to-branch`: Target branch (default: main)38 - `from-branch`: Source branch (default: current branch)39- `merge-pr`: Review, label, merge, and post-merge verify PRs40 - Usage: `/mk-git merge-pr <PR numbers or URLs>`41 - Accepts one or more PR numbers or GitHub PR URLs42 - Runs `/mk-review-pr <PR> --fix --reply` before any label or merge43 - Adds label `ready to ship` only after review/fix/reply reports the PR is merge-ready44 - Merges only reviewed-and-ready PRs, then watches target-branch CI to success4546## Quick Reference4748| Task | Reference |49|------|-----------|50| Commit | `references/workflow-commit.md` |51| Push | `references/workflow-push.md` |52| Pull Request | `references/workflow-pr.md` |53| Merge | `references/workflow-merge.md` |54| Merge PRs | `references/workflow-merge-pr.md` |55| Standards | `references/commit-standards.md` |56| Safety | `references/safety-protocols.md` |57| Branches | `references/branch-management.md` |58| GitHub CLI | `references/gh-cli-guide.md` |5960## Core Workflow6162### Step 1: Stage + Analyze63```bash64git add -A && git diff --cached --stat && git diff --cached --name-only65```6667### Step 2: Security Check68Scan for secrets before commit:69```bash70git diff --cached | grep -iE "(api[_-]?key|token|password|secret|credential)"71```72**If secrets found:** STOP, warn user, suggest `.gitignore`.7374### Step 3: Split Decision7576**NOTE:**77- Search for related issues on GitHub and add to body.78- Only use `feat`, `fix`, or `perf` prefixes for files in `.claude` directory (do not use `docs`).7980**Split commits if:**81- Different types mixed (feat + fix, code + docs)82- Multiple scopes (auth + payments)83- Config/deps + code mixed84- FILES > 10 unrelated8586**Single commit if:**87- Same type/scope, FILES ≤ 3, LINES ≤ 508889### Step 4: Commit90```bash91git commit -m "type(scope): description"92```9394## Output Format95```96✓ staged: N files (+X/-Y lines)97✓ security: passed98✓ commit: HASH type(scope): description99✓ pushed: yes/no100```101102## Error Handling103104| Error | Action |105|-------|--------|106| Secrets detected | Block commit, show files |107| No changes | Exit cleanly |108| Push rejected | Suggest `git pull --rebase` |109| Merge conflicts | Suggest manual resolution |110111## References112113- `references/workflow-commit.md` - Commit workflow with split logic114- `references/workflow-push.md` - Push workflow with error handling115- `references/workflow-pr.md` - PR creation with remote diff analysis116- `references/workflow-merge.md` - Branch merge workflow117- `references/workflow-merge-pr.md` - PR review, ready label, merge, and CI convergence workflow118- `references/commit-standards.md` - Conventional commit format rules119- `references/safety-protocols.md` - Secret detection, branch protection120- `references/branch-management.md` - Naming, lifecycle, strategies121- `references/gh-cli-guide.md` - GitHub CLI commands reference