push-pr
Push branch and create GitHub PR
Files1
View on GitHubSKILL.md.claude/skills/push-pr/SKILL.md
GitHubPush Branch and Create Pull Request
Steps
Get current feature from branch:
BRANCH=$(git rev-parse --abbrev-ref HEAD) NUM=$(echo "$BRANCH" | grep -oE 'alg-([0-9]+)' | grep -oE '[0-9]+')Run verification:
npm run type-check --workspaces --if-present npm test --workspaces --if-presentIf verification fails, stop and report errors. Do NOT proceed to create a PR with failing checks.
Push branch to remote:
git push -u origin $BRANCHGenerate PR title using Conventional Commits:
- Read
specs/alg-${NUM}-*/spec.mdto understand the feature - Generate a title like:
feat(scope): short description - Types:
feat(new feature),fix(bug fix),refactor,perf,docs,chore - Scope: optional component name, e.g.
feat(search):,fix(auth):
- Read
Create PR with gh CLI (following
.github/PULL_REQUEST_TEMPLATE.md):gh pr create \ --title "${TITLE}" \ --body "## Summary Resolves [ALG-${NUM}](https://linear.app/algojuke/issue/ALG-${NUM}) See [spec.md](specs/alg-${NUM}-*/spec.md) for full specification. ## Changes $(git log main..HEAD --oneline) ## Verification - [x] Type check passes - [x] Tests pass "Output the PR URL for the user.
Notes
- The PR body uses "Resolves ALG-XX" to link the Linear issue
- Linear automation will automatically update the issue status to "In Review" when the PR is created
- If the branch already has a PR,
gh pr createwill fail - usegh pr viewinstead - Always run verification before pushing to catch issues early