Skip to content

pensarai/apex / .agents/skills/pr

Create, update, format, babysit, resolve conflicts and review findings on, and merge Apex pull requests and PR stacks. Use when the user asks to open or update a PR or merge request, align a stack, get CI green, address review or Bugbot findings, resolve merge conflicts, or merge.

PR

Apex pull-request workflow. Read this file, then read every applicable playbook under .agent-instructions/skills/pr/ before acting. Do not improvise past a playbook.

This is repository-development guidance for coding agents working on Apex. Keep it in the repo's .agents/skills tree only; do not copy or link it into .claude/skills, .skills, skills, ~/.agents/skills, or ~/.pensar/skills, because Apex scans those locations as runtime skills.

Invariants

  • Resolve OWNER/REPO, the target PR's current head/base SHAs, and stack topology from live Git and GitHub state. A body saying "stack" is not proof of dependent branches.
  • Ordinary Apex work branches from and targets canary. Do not target main, retarget a PR, or rewrite stack topology unless the user explicitly asks for that exact change.
  • GitHub reads and writes go through gh api (REST or GraphQL). Do not use gh pr create, gh pr comment, or gh pr merge.
  • Preserve bot-managed body regions (CURSOR_SUMMARY, codesmith:footer) byte-for-byte when editing human-authored sections.
  • Never merge, squash, close, enable auto-merge, or delete a branch unless the user explicitly authorizes that exact action. A request to resolve conflicts and push does not authorize merging.
  • A branch is brought up to date by rebasing onto its base, never by merging the base into it. PR branches keep linear history.
  • A rebase is published with the leased force-push in conflicts-and-merge.md. Rebasing a PR's own branch in a PR flow authorizes that push; do not ask again, and do not merge the base in to avoid it. Every other force-push needs the user's explicit authorization, and canary and main are never force-pushed.
  • Work from a clean, isolated checkout when the user's current checkout has unrelated changes. Never stash, reset, or overwrite user work to make a PR task convenient.
  • Judge CI, reviews, and mergeability on the latest PR head SHA. Pending work or green checks on an older SHA are not done.

Route

IntentPlaybook
Create or update a feature/fix/docs PRcreate-and-update.md
Create, inspect, format, or refresh a PR stackstacks.md
Stay until CI and mergeability settlebabysit.md
Review comments, Cursor Bugbot, or thread resolutioncomments-and-bugbot.md
Resolve conflicts or perform an authorized mergeconflicts-and-merge.md

After creating, updating, refreshing, or fixing a PR, babysit the new SHA. If it belongs to a stack, also apply stacks.md. If review findings exist, apply comments-and-bugbot.md before declaring the PR ready.

Babysit means staying until required checks have conclusions on the latest SHA, mergeability is known, and no unresolved actionable review work remains. Waiting for human approval after every technical gate is green is terminal; pending CI is not.

receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 319kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 319kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 319kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 319kUpdated Claude CodeCodexVerifiedInstall