Skip to content

feiskyer/codex-settings / skills/github-review-pr

github-review-pr

Verified

Review a GitHub pull request by number or URL for evidence-backed defects. Not for reviewing local uncommitted changes.

FileKindSize
SKILL.mdskill md4.9 KB
agents/openai.yamlconfig287 B
references/gh-commands.mdmarkdown3.0 KB
references/publishing.mdmarkdown2.9 KB
references/review-criteria.mdmarkdown3.8 KB
references/subagent-prompts.mdmarkdown7.3 KB

references/gh-commands.md

View on GitHub
# Read-only gh Command Reference

Read only when a command is needed. These examples use PR 78; substitute the actual repository, number, and captured SHAs. Publication is covered separately in [publishing.md](publishing.md).

## Read-only

```sh
# List open PRs
gh pr list

# View PR description and metadata
gh pr view 78

# View PR code changes
gh pr diff 78

# Size probe
gh pr view 78 --json changedFiles,additions,deletions

# File manifest for very large PRs, plus one file's patch on demand.
# GitHub omits `patch` for very large files and lists at most 3000 files.
gh api repos/OWNER/REPO/pulls/78/files --paginate --jq '.[] | {filename, additions, deletions}'
gh api repos/OWNER/REPO/pulls/78/files --paginate --jq '.[] | select(.filename == "PATH") | .patch'

# Get repo owner/name
gh repo view --json nameWithOwner --jq '.nameWithOwner'

# Get PR head and base commit SHAs (full 40-char). Reviewers read project
# guidance at the base SHA so the PR cannot rewrite the rules it is judged by.
gh api repos/OWNER/REPO/pulls/78 --jq '.head.sha'
gh api repos/OWNER/REPO/pulls/78 --jq '.base.sha'

# Read an AGENTS.md file at the base SHA (agent #1 reads each guidance file this way)
gh api "repos/OWNER/REPO/contents/AGENTS.md?ref=BASE_SHA" --jq '.content' | base64 -d

# Read any file at the captured head SHA
gh api "repos/OWNER/REPO/contents/PATH?ref=HEAD_SHA" --jq '.content' | base64 -d

# Guidance files this PR modifies (report as a note, not a finding)
gh pr diff 78 --name-only | rg '(CLAUDE|AGENTS)\.md$'

# Your login (only when checking your prior review)
gh api user --jq '.login'

# Existing top-level comments, review bodies, and inline discussion
gh pr view 78 --json comments,reviews
gh api repos/OWNER/REPO/pulls/78/comments --paginate \
  --jq '.[] | {path, line, body, author: .user.login, assoc: .author_association}'

# Latest commit time (for repeat-review checks)
gh pr view 78 --json commits --jq '.commits[-1].committedDate'

# PRs that previously touched a file (agent #4).
# Note: walks the default branch only; does not follow renames. Exclude the current PR number.
gh api "repos/OWNER/REPO/commits?path=path/to/file&per_page=10" --jq '.[].sha' | head -5 \
  | xargs -I{} gh api repos/OWNER/REPO/commits/{}/pulls --jq '.[].number' | sort -un

# Feedback left on a past PR. Keep every comment regardless of author — other
# reviewers, bots, and the author's own replies are all useful context — but carry
# author and author_association through so weight can be judged downstream.
gh api repos/OWNER/REPO/pulls/72/comments --paginate \
  --jq '.[] | {path, line, body, author: .user.login, assoc: .author_association}'   # inline review comments
gh api repos/OWNER/REPO/issues/72/comments --paginate \
  --jq '.[] | {body, author: .user.login, assoc: .author_association}'               # top-level comments
```

`gh pr diff` follows the live PR. Re-check the head before finalizing findings; if it moved, refresh and revalidate affected findings or explicitly report the captured snapshot and the gap. Missing/truncated patches are not evidence that a file is safe.
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: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated 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: 322kUpdated 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: 322kUpdated Claude CodeCodexVerifiedInstall