crysk-pr

When to Use

Load this skill whenever the user asks to open, create, submit, or update a pull request (or push a branch and open a PR).

Step 1: Branch, Pre-Push Checks & Repo Conventions

1. Protect integration branches: Never commit or push directly to the default branch, or to the integration branch the repository declares (for example dev in a repo whose rules say so). If currently on one, create a focused branch first (feat/<slug>, fix/<slug>, chore/<slug>, refactor/<slug>).
2. Resolve target base branch:
   • Check AGENTS.md, CLAUDE.md, CONTRIBUTING.md, or an active project PR skill (such as branch-pr or gh-stack) for the required target branch (e.g. dev vs main).
   • If the repo defines no rule, inspect whether an active dev integration branch exists or fall back to gh repo view --json defaultBranchRef --jq .defaultBranchRef.name.
3. Run local gates before pushing: Run the project's fast verification commands (tests, typecheck, linter) before pushing the branch (git push -u origin HEAD).

Step 2: PR Title & Description (Repo Template or Built-in Fallback)