pr
The pr command automates pull request creation by verifying local review and security checks have passed, confirming CI workflows succeeded, then using GitHub CLI to create a PR from the current branch to a target branch (defaulting to main) with conventional commit titles and project templates. Use this when ready to submit code changes for team review after completing local validation steps.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/alirezarezvani/claude-skills/HEAD/.claude/commands/git/pr.md -o ~/.claude/commands/pr.mdpr.md
## Variables
TARGET_BRANCH: $1 (defaults to `main`)
SOURCE_BRANCH: current branch (`git branch --show-current`)
## Workflow
1. Ensure `/review` and `/security-scan` have passed locally.
2. Confirm `ci-quality-gate` workflow succeeded for `SOURCE_BRANCH`.
3. Create the PR using GitHub CLI:
```bash
gh pr create \
--base "$TARGET_BRANCH" \
--head "$SOURCE_BRANCH" \
--title "<Conventional PR title>" \
--body-file .github/pull_request_template.md
```
If no template exists, provide a summary referencing Context, Testing, and Security results.
4. Add labels (`gh pr edit --add-label "status: in-review"`).
5. Share the PR link with reviewers and ensure at least one human approval is obtained.Deep-dive feature repair — systematically fix an entire feature/module. Usage: /focused-fix <feature-path>
Clean up merged branches locally and on remote, keeping only main, dev, and gh-pages.
Stage working tree changes and create a Conventional Commit (no push).
Stage, commit, and push the current branch following git governance rules.
Run the full 8-phase plugin audit pipeline on a skill directory.
Run the local review gate before pushing.
Run the security scan gate before pushing.
Scan and optimize docs for SEO — meta tags, readability, keywords, broken links, sitemap.