Agent skill · Code Review & Quality

goal-pr

Drive a pull request to a clean state and merge it: run the `review-pr` skill, fix every mid-or-above finding, and repeat until no mid-or-above findings remain, then merge. Use when the user wants to finish a PR by reviewing, fixing, and merging it, or triggers on "the `goal-pr` skill".

dyoshikawa1,265★ · +16/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add dyoshikawa/rulesync --skill goal-pr --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: .rulesync/skills/goal-pr/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,285 · +20 this week
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Goal PR target_pr = the user's request This skill drives a pull request all the way to merge. It repeatedly runs the `review-pr` skill, fixes every finding of severity `mid` or above, and merges the PR once a review round reports no `mid`-or-above findings. ## 0. Determine and Prepare the Target PR 1. If `target_pr` is provided (e.g. `123`, `#123`, or a PR URL), use it. 2. Otherwise, look for the PR of the current branch: ```bash gh pr view --json number,title,state,headRefName 2>/dev/null ``` 3. If no PR exists yet, create one (this satisfies the "PR is the goal" intent): - Use the `commit-push-pr` skill to commit the current changes, push the branch, and open a PR. - Then resolve `target_pr` to the freshly created PR number. Confirm that the current local branch is the PR's head branch, because the fix phase below must commit and push fixes onto that branch. If they differ, ask the user how to proceed and stop. ## 1. Exit Condition The loop exits when a single review round satisfies **both** of: - **0** findings of severity `mid`, `high`, or `critical` (only `low` findings, or none at all, may remain). - The PR's GitHub Actions checks are **green** — no check is `fail` or `pend

What's inside
Steps it walks through
  1. 0. Determine and Prepare the Target PR
  2. 1. Exit Condition
  3. 2. Iteration Loop
  4. 2-1. Review Phase
  5. 2-2. Evaluate the Exit Condition
  6. 2-3. Fix Phase
  7. 3. Merge
  8. 4. Final Report
Commands it runs
gh pr view --json number,title,state,headRefName 2>/dev/null
git status
git add <changed files>
git commit -m "<message>"
git push origin HEAD
More from rulesync
All skills →
About this skill
What does the goal-pr skill do?

Drive a pull request to a clean state and merge it: run the `review-pr` skill, fix every mid-or-above finding, and repeat until no mid-or-above findings remain, then merge. Use when the user wants to finish a PR by reviewing, fixing, and merging it, or triggers on "the `goal-pr` skill".

How do I install it?

Run `npx skills add dyoshikawa/rulesync --skill goal-pr --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From dyoshikawa/rulesync, a repository with 1,285 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going