Agent skill · Code Review & Quality

approve

Approve a pull request using gh pr review --approve

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

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

Facts
Files in the skill folder: 1
SKILL.md size: 2 KB
Bundled scripts: none
Path: .rulesync/skills/approve/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

# Approve Pull Request Approve a pull request using `gh pr review --approve`. ## Input ``` the user's request ``` ## Step 1: Determine the Target PR Parse `the user's request` to identify the PR to approve: ### Case A: PR number or URL is provided - Extract the PR number from the argument - Examples: `123`, `#123`, `https://github.com/owner/repo/pull/123` ### Case B: No argument provided - Get the PR associated with the current branch: ```bash gh pr view --json number,title,state ``` ### Case C: Unable to determine the PR If the PR cannot be determined (e.g., no PR exists for the current branch, or the argument is ambiguous), **ask the user** to specify which PR to approve. ## Step 2: Verify the PR Before approving, confirm the PR details: ```bash gh pr view <pr_number> --json number,title,state,author,baseRefName,headRefName,isDraft ``` Check: 1. The PR state is `OPEN` 2. The PR is not a draft (`isDraft` is `false`) 3. Display the PR title, number, and author to the user for confirmation If the PR is not open or is a draft, inform the user and stop. ## Step 3: Approve the PR Execute the approve command: ```bash gh pr review <pr_number> --approve ``` **Important**: Only approve ONE

What's inside
Steps it walks through
  1. Input
  2. Step 1: Determine the Target PR
  3. Case A: PR number or URL is provided
  4. Case B: No argument provided
  5. Case C: Unable to determine the PR
  6. Step 2: Verify the PR
  7. Step 3: Approve the PR
  8. Step 4: Report Result
Commands it runs
gh pr view --json number,title,state
gh pr view <pr_number> --json number,title,state,author,baseRefName,headRefName,isDraft
gh pr review <pr_number> --approve
gh pr review <pr_number> --approve --body "<approval_comment>"
More from rulesync
All skills →
About this skill
What does the approve skill do?

Approve a pull request using gh pr review --approve

How do I install it?

Run `npx skills add dyoshikawa/rulesync --skill approve --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