Menu
Use when working on GitHub pull requests that need PR-ready validation, review-thread replies, reviewer mentions, linked external references, or merge readiness checks.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when changing what a running devloop harness serves — pointing it at a different directory or worktree, or making the live harness serve newer or different code (a newer commit, another branch, or in-progress edits) without a wasteful restart.
Use when verifying that a UI change works end to end by driving the running app in a real browser — confirming a fix, reproducing a reported UI symptom, or proving a wizard/form/flow behaves — with Playwright against the exact code under review.
Enforce a Roborev plus Kata development workflow for code changes. Use when Codex is asked to implement, fix, refactor, or review work tracked by Kata and Roborev, especially when branch discipline, non-blocking review jobs, validation gates, SemVer, changelog checks, and final delivery reporting matter.
Create or review a standalone repository that publishes a set of Codex or Claude skills with shared validation, linking, eval, and agent metadata conventions.
Prepare small, reviewable local commits with explicit rationale, SemVer impact, task hygiene, branch cleanup expectations, and clear commit commentary. Use when asked to commit work, prepare a PR-ready change, decide version impact, write commit messages, or clean up merged feature branches.
Use when classifying the priority of a Jira issue or creating a Jira issue with the correct priority assigned.
| name | pull-request |
| description | Use when working on GitHub pull requests that need PR-ready validation, review-thread replies, reviewer mentions, linked external references, or merge readiness checks. |
Use this skill for GitHub pull request work that is not specifically a release.
Use $release for release PRs and $repo-policy for repository protection settings.
$testing before claiming a PR is ready.When addressing GitHub PR review comments:
@octocat, in the thread reply.gh to reply to a review thread, use gh api graphql with the review thread or review comment node ID. State explicitly that this is an in-thread reply, not a top-level PR comment.gh pr comment, gh pr review --comment, or REST endpoints for an in-thread review reply.gh thread-reply command, include the explicit warning that gh pr comment creates a top-level PR comment and must not be used for the thread reply.Before reporting PR work complete, state: