gh-plan-review
Review GitHub Plan
Use this skill when the user wants a deep review of an implementation plan before coding or before broadening an in-flight issue, PR, or branch. This skill is report-only: inspect, challenge, and summarize, but do not edit code, GitHub issues, TODO files, or branch state. Do not commit, amend, push, rebase, or hand off to mutation skills without a separate user request.
Boundary Rules
- Use
gh-issue-kickoffwhen the user wants to start from an issue and produce the first execution-ready plan. - Use this skill when the user wants to review, challenge, pressure-test, or refine an existing implementation plan, test strategy, or branch approach.
- Do not widen this skill into execution, issue cleanup, or git mutation work. If the user switches to implementation, hand off to the appropriate execution skill.
- Do not invoke
gh-commit,gh-pr-create,gh-pr-rebase, orgh-pr-review-commentsfrom this skill unless the user makes a separate follow-up request for mutation work.
Core Workflow
- Identify the authoritative plan source:
- GitHub issue: fetch with
gh issue view {<number> | <url>} --json assignees,author,body,comments,labels,milestone,number,projectItems,state,title,updatedAt,url - GitHub PR: fetch with
gh pr view {<number> | <url>} --json baseRefName,body,files,headRefName,number,state,title,url - Active branch only: inspect
git branch --show-current,git status --short, the current diff, and any local plan or design docs
- GitHub issue: fetch with
- Inspect the relevant local codebase, architecture, tests, and diff before judging the plan.
- Ground the review in evidence. The authoritative GitHub state, current repo shape, and actual branch diff win over pasted summaries or stale notes.
More from beeman/skills
gh-pr-review-comments
Address GitHub pull request review comments on an existing feature branch. Use when Codex needs to fetch live PR review comments with gh, classify each comment as actionable, optional, or rejectable, apply only accepted fixes on the same branch, run a self-review pass for contradictions introduced by those fixes, and then either create a new commit or follow an explicitly approved history-rewrite path before pushing, resolving threads, and re-requesting review.
8feature-structure
Use when reorganizing code around feature boundaries, splitting monolithic screen components or state hooks, deciding whether logic belongs in data-access, feature, ui, or child features, or moving orchestration out of prop-heavy UI files.
8gh-pr-create
Create a GitHub pull request from local repo changes. Use when Codex must get feature-branch setup and local commit packaging from `gh-commit`, get approval before pushing, show the exact PR title and body that will be sent, handle single-commit and multi-commit branch flows explicitly, and open or update the PR with gh.
7gh-issue-kickoff
Kick off work on a GitHub issue with gh. Use when Codex needs to start from the authoritative issue state and local codebase, fix only material issue gaps, and produce the first execution-ready implementation plan. For a deeper critique or tradeoff review of an existing plan, use `gh-plan-review`.
5gh-pr-rebase
Rebase an existing GitHub PR branch onto the repository default branch. Use when Codex needs to fetch the latest default-branch history, keep the local default branch current when that is safe, rebase the current feature branch, resolve straightforward conflicts carefully, ask the user to decide ambiguous conflicts, and update the remote PR branch with `git push --force-with-lease` after any required approval.
5gh-commit
Prepare a local Git commit from repo changes. Use when Codex needs to get onto the correct feature branch if needed, inspect `git status --short`, the current diff, and branch history, run the smallest relevant verification, add any required changeset, and package the tracked work into either a new commit or an explicitly approved amend flow before any push or PR step.
4