- Rename marketplace to lm-claude-plugins - Move MCP servers to root with symlinks - Add 6 PR tools to Gitea MCP (list_pull_requests, get_pull_request, get_pr_diff, get_pr_comments, create_pr_review, add_pr_comment) - Add clarity-assist plugin (prompt optimization with ND accommodations) - Add git-flow plugin (workflow automation) - Add pr-review plugin (multi-agent review with confidence scoring) - Centralize configuration docs - Update all documentation for v3.0.0 BREAKING CHANGE: MCP server paths changed, marketplace renamed Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
/commit-push - Commit and Push
Purpose
Create a commit and push to the remote repository in one operation.
Behavior
Step 1: Run /commit
Execute the standard commit workflow (see commit.md).
Step 2: Push to Remote
After successful commit:
- Check if branch has upstream tracking
- If no upstream, set it:
git push -u origin <branch> - If upstream exists:
git push
Step 3: Handle Conflicts
If push fails due to diverged history:
Remote has changes not in your local branch.
Options:
1. Pull and rebase, then push (Recommended)
2. Pull and merge, then push
3. Force push (⚠️ destructive)
4. Cancel and review manually
Environment Variables
| Variable | Default | Description |
|---|---|---|
GIT_AUTO_PUSH |
true |
Auto-push after commit |
GIT_PUSH_STRATEGY |
rebase |
How to handle diverged branches |
Safety Checks
- Protected branches: Warn before pushing to main/master/production
- Force push: Require explicit confirmation
- No tracking: Ask before creating new remote branch
Output
On success:
Committed: abc1234
feat(auth): add password reset functionality
Pushed to: origin/feat/password-reset
Remote URL: https://github.com/user/repo