Skill

Context

Waits for AI code review on GitHub PRs, analyzes top finding from comments, and generates TDD fix plan without user prompt. Use after submitting PRs for review.

Git

Github

Python

git-workflow

code-quality

npx claudepluginhub oxidian/cc-plugins --plugin oxgh

Tool Access

This skill is limited to using the following tools:

Bash(python3 ${CLAUDE_PLUGIN_ROOT}/scripts/wait_for_ai_review.py:*)Bash(gh pr view:*)Bash(gh pr checkout:*)Bash(gh api:*)Bash(git remote get-url origin)

Preview

- Git remote: !`git remote get-url origin`

SKILL.md

Similar Skills

Context

Automates GitHub PR workflow: detects PR, checks out branch, waits for AI code review, auto-merges if clean, or creates TDD fix plan for top issue.

6 tools

oxgh

Context

Waits for AI code review on GitLab MR, checks out branch, analyzes top finding from notes, and generates TDD fix plan. Use after MR submission.

6 tools

oxgl

git-pr-autofix

Automates GitHub PR review-fix loops: requests bot reviews via @mentions, polls comments with GitHub CLI, analyzes issues, fixes code, runs internal review, pushes changes, repeats until no critical issues.

git-pr-autofix

Stats

Parent Repo Stars11

Parent Repo Forks0

Last CommitMar 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Context

Git remote: !git remote get-url origin

Your Task

Get PR number: Use $ARGUMENTS if provided, otherwise detect from current branch with gh pr view --json number --jq '.number'
Checkout PR branch: Run gh pr checkout <PR_NUMBER> to ensure you're on the PR's branch (safe to run even if already on the branch)
Wait for AI review: Run python3 ${CLAUDE_PLUGIN_ROOT}/scripts/wait_for_ai_review.py <PR_NUMBER> (use 45 minute timeout)
Read all PR comments: Parse the owner/repo from the git remote above, then run gh api repos/{owner}/{repo}/issues/<PR_NUMBER>/comments
Analyze and respond:
- If there are findings: identify the highest priority review comment only. Investigate the codebase to understand that specific issue, then immediately create an implementation plan to fix it using TDD. Do NOT ask the user whether they want to fix the issue - assume they do. Write the full plan directly. Ignore lower priority comments for now.
- If no findings: report success