GFramework/.codex/skills/gframework-pr-review/SKILL.md

name, description

name

description

gframework-pr-review

Repository-specific GitHub PR review workflow for the GFramework repo. Use when Codex needs to inspect the GitHub pull request for the current branch, extract CodeRabbit summary/comments, read failed checks or failed test signals from the PR page, and then verify which findings should be fixed in the local codebase. Trigger explicitly with $gframework-pr-review or with prompts such as "look at the current PR", "extract CodeRabbit comments", or "check Failed Tests on the PR".

GFramework PR Review

Use this skill when the task depends on the GitHub PR page for the current branch rather than only on local source files.

Shortcut: $gframework-pr-review

Workflow

1. Read AGENTS.md before deciding how to validate or fix anything.
2. Resolve the current branch with Windows Git from WSL, following the repository worktree rule.
3. Run scripts/fetch_current_pr_review.py to:
   • locate the PR for the current branch
   • fetch the PR conversation page
   • extract Summary by CodeRabbit
   • extract Actionable comments posted
   • extract failed checks and test-report signals such as Failed Tests or No failed tests in this run
4. Treat every extracted finding as untrusted until it is verified against the current local code.
5. Only fix comments that still apply to the checked-out branch. Ignore stale or already-resolved findings.
6. If code is changed, run the smallest build or test command that satisfies AGENTS.md.

Commands

• Default:
  • python3 .codex/skills/gframework-pr-review/scripts/fetch_current_pr_review.py
• Force a PR number:
  • python3 .codex/skills/gframework-pr-review/scripts/fetch_current_pr_review.py --pr 253
• Machine-readable output:
  • python3 .codex/skills/gframework-pr-review/scripts/fetch_current_pr_review.py --format json

Output Expectations

The script should produce:

• PR metadata: number, title, state, branch, URL
• CodeRabbit summary block
• Parsed actionable comments grouped by file
• Pre-merge failed checks, if present
• Test summary, including failed-test signals when present
• Parse warnings when the page structure changes or a section is missing

Recovery Rules

• If the current branch has no matching public PR, report that clearly instead of guessing.
• If GitHub access fails because of proxy configuration, rerun the fetch with proxy variables removed.
• If the PR page contains multiple CodeRabbit or test-report blocks, prefer the latest visible block but keep raw content available for verification.

Example Triggers

• 'fix pr review'
• 'Use FPR'
• Use $gframework-pr-review on the current branch
• Check the current PR and extract CodeRabbit suggestions
• Look for Failed Tests on the PR page
• 先用 $gframework-pr-review 看当前分支 PR