jpmschweitzerandClaude Opus 4.6
7158ae9cf5
Claude-native starter kit that bootstraps multi-agent team infrastructure for any project. Clone once, install as a global skill, run /kit-install in any project directory. Includes: - 3-tier profile system (minimal/standard/full: 3-12 agents) - 16 agent archetype templates with personality spectrum - 18 skill templates using domain-action naming convention - Stakeholder persona panel for workshops and PR reviews - SQLite ticketing DB with CLI tools (config-based DB paths) - Decision tracking, sprint lifecycle, workshop orchestration - Multi-git-host support (GitHub, Gitea, GitLab) - /kit-update skill for syncing with source repo evolution - Naming theme support for agent identity/flavor - Smoke tests for all three profile tiers Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2.8 KiB
name, description, user-invocable, allowed-tools
| name | description | user-invocable | allowed-tools |
|---|---|---|---|
| pr-push | Push commits and create or update a pull request. Use when the user says "push pr", "push and create pr", "update pr", "create a pr", "open a pr", or invokes /pr-push. NOT triggered by plain "push". Pushes the current branch, creates a PR if none exists, or confirms the existing PR was updated. NEVER merges the PR into main. | true | Bash, Read, Grep, Glob, AskUserQuestion |
Push PR Skill
Push commits to remote and create or update a PR. Operates exclusively on the current branch — never touches main.
Safety Rules (NON-NEGOTIABLE)
- NEVER merge a PR into main. No merge commands, no git merge into main.
- NEVER checkout or push to main.
- NEVER force-push unless the user explicitly requests it.
- NEVER use
--no-verifyor skip hooks. - Only push to the current working branch.
Workflow
1. Validate branch
git branch --show-current
If on main, stop: "You're on main. Switch to a working branch first."
2. Check for unpushed commits
git fetch --all
git status
git log --oneline origin/<branch>..<branch>
If no unpushed commits, skip to step 4 (PR check).
3. Check for conflicts with main
git merge-tree --write-tree origin/main HEAD 2>&1
If conflicts reported, merge main into current branch:
git merge origin/main --no-edit
If merge conflicts, stop and report — let the user resolve. If clean, continue.
4. Push
git push origin <branch>
If push fails, stop and report. Never force-push without explicit request.
5. Check for existing PR
Use the git host CLI matching your project's configuration (see CLAUDE.md):
# GitHub:
gh pr list --state open --head <branch>
# Gitea:
tea pr list --login <login> --repo <owner/repo> --state open --output simple
# GitLab:
glab mr list --state opened --source-branch <branch>
Match current branch name in PR list.
- PR exists: Report "Pushed N commits to
<branch>. PR #X updated." Done. - No PR: Continue to step 6.
6. Create a new PR
git log --oneline main..<branch>
git diff --stat main...<branch>
Draft title (<type>(<scope>): <summary>, max 70 chars) and description.
Use the git host CLI matching your project's configuration:
# GitHub:
gh pr create --title "<title>" --body "<description>" --base main --head <branch>
# Gitea:
tea pr create --repo <owner/repo> --login <login> --title "<title>" --description "<description>" --base main --head <branch>
# GitLab:
glab mr create --title "<title>" --description "<description>" --target-branch main --source-branch <branch>
Report PR URL when done.
Arguments
If the user passes arguments (e.g., /pr-push "my title"), use them as the
PR title instead of generating one.