New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Authorized PR Merge Workflow

by diegosouzapw in diegosouzapw/OmniRoute

Works through analyzed pull request plans, repairs approved fixes while keeping contributor credit, validates candidates and merges only owner-authorized groups.

MITAuto-check passedDevelopment

Install Authorized PR Merge Workflow

skills CLI
$ npx skills add diegosouzapw/OmniRoute --skill merge-prs -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install diegosouzapw/OmniRoute merge-prs --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/diegosouzapw/OmniRoute.git skills-src && mkdir -p .claude/skills && cp -r skills-src/config/quality/skill-templates/merge-prs .claude/skills/merge-prs && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
merge-prs
GitHub stars
74k
Token cost
~1.3k tokens
SKILL.md length
632 words
Files
1
Skills in repo
50
Repo updated
First seen
Licence
MIT

At a glance

Works through analyzed pull request plans, repairs approved fixes while keeping contributor credit, validates candidates and merges only owner-authorized groups.

  • Works in 4 steps: Reconcile and choose → Repair without losing credit → Validate and admit → …
  • Merging a batch of reviewed pull requests that the owner has approved
  • SKILL.md covers 1. Reconcile and choose, 2. Repair without losing credit, 3. Validate and admit and 4. Reconcile the outcome
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

This skill executes plans produced by an earlier PR review stage. Before acting it reads the shared base-green, validation-gate, merge-gates, protected-surfaces and credit-preservation documents, whose rules apply throughout. It refreshes live PR states, heads and bases, worktree ownership, freeze state and existing plans in the analyzed folder, and returns to review if no plan exists.

It presents a report grouped by readiness and contributor or theme, with each PR's rating, scope, risks, mandatory fixes and recommendation. The owner picks items or groups and receives a merge dossier covering what enters, leaves or changes, authorship, dependencies, validation, risks, rollback, order and the final candidate. Merging needs explicit authorization for that group; general permission to keep developing does not count.

Repairs happen in an isolated worktree at the contributor's head, after verifying identity and rechecking the remote before every push. Only approved mandatory items are implemented, with red-to-green test proof, and original authorship is preserved alongside maintainer co-authorship. The skill does not stash, reset a contributor branch or force-push over concurrent work, and unknown or failing required checks keep a PR on hold.

When your agent uses it

  • Merging a batch of reviewed pull requests that the owner has approved
  • Applying mandatory fixes to a contributor's PR while keeping their authorship
  • Producing a merge dossier before the owner authorizes a group
  • Holding PRs whose required checks are unknown or failing

Example prompts

  • “Merge the analyzed PRs I approve, the two docs fixes, after you produce the merge dossier.”
  • “Show the readiness report for all analyzed pull requests, grouped by contributor.”
  • “Apply the mandatory fixes on the contributor's PR in a separate worktree and keep their commit credit.”
  • “Check why this PR is still on HOLD and which required checks are missing.”

Requirements

  • A repository using the shared pipeline layout, with analyzed PR plans under _tasks/pipeline/prs
  • Prior review evidence for each pull request

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Reconcile and choose
  2. Repair without losing credit
  3. Validate and admit
  4. Reconcile the outcome

What it can do on your machine

Read from SKILL.md and the folder at commit 4ea24a2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Authorized PR Merge Workflow loads about 1.3k tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 632 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~71
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from diegosouzapw/OmniRoute at commit 4ea24a2, republished under its MIT licence (© diegosouzapw). 632 words, ~1,261 tokens.

Download SKILL.mdSave it as .claude/skills/merge-prs/SKILL.md (or your agent's skills folder).
name
merge-prs
description
Consume analyzed PR plans, implement authorized fixes with contributor credit, validate exact candidates, and merge only owner-selected and explicitly authorized groups through the shared gates. Requires prior review evidence; unknown or failing required checks remain HOLD.

Execute analyzed PR plans

Read ../_shared/base-green.md, ../_shared/validation-gate.md, ../_shared/merge-gates.md, ../_shared/protected-surfaces.md and ../_shared/credit-preservation.md before execution. Their authority and evidence boundaries apply throughout; no throughput exception waives required checks.

1. Reconcile and choose

Refresh live PR states/heads/bases, worktree ownership, freeze state and existing plans under _tasks/pipeline/prs/1-analyzed/. Preserve other sessions' claims. No plan means return to review; an explicit owner request for inline review may authorize a bounded mini-analysis, not skip validation or merge authorization.

Present the organization report by readiness and contributor/theme, including review rating, scope, risks, mandatory fixes and recommendation. Sound ideas that need substantial work may be offered for uplift; do not dispatch it without the owner's choice. The owner selects the items/groups, then receives a merge dossier: what enters, leaves or changes; authorship; dependencies; validation; risks; rollback; order and final candidate identity. Obtain explicit authorization for that group. General permission to continue development is not merge permission. An explicit owner instruction naming PRs and requesting their merge can satisfy the selection/dossier decision; record the scope, but retain all safety gates.

Claim only selected eligible plans via the pipeline's atomic move into 2-implementing/; if another session wins, stop that item. Stage owned paths only in the separate private _tasks repo and regenerate its index when appropriate. Merged items go to 3-done/ with actual evidence; closed/unmerged items are not reported as delivered. Age alone does not establish that a claim is abandoned.

2. Repair without losing credit

Create an isolated worktree at the observed contributor head. Verify identity before changing anything and recheck the remote predecessor before every push. Implement only the approved mandatory items, with RED-to-GREEN proof and affected suites. Preserve original authorship and appropriate maintainer co-authorship. Do not stash, reset a contributor branch, overwrite unrelated edits or force-push over concurrent work. Reconstruct only in a separate recovery branch after owner review; locked forks follow the credit-preservation protocol and stay open.

Use fragments-first changelog entries where supported. During synchronization, verify sibling entries remain intact; do not overwrite the complete changelog. Live validation or credentials that are genuinely required remain an explicit HOLD, with a durable release-drain record; they are not optional because CI passed.

Show full SKILL.md (279 more words)Show less

3. Validate and admit

Use the exact-candidate contract from the shared validation/merge rules. Local fast checks, head-only pre_greened stamps, a previous day's full train, an empty incident list, or DRIFT alone never grant admission. Do not run a fallback command after a failed gate to manufacture success. Missing/contradictory artifacts and incomplete build/package evidence remain failures or HOLD.

Base failures require exact-base reproduction and repair in their own PR; they do not justify an administrative bypass. Fork action_required requires a reviewed trust decision for the exact head/workflow and explicit approval authority. Never auto-approve every pushed fork run. A cancelled/slow check is not automatically flaky or infrastructure-related; establish the cause from evidence.

When the owner has authorized the group and all required checks pass, merge only through ../_shared/merge-gates.md, serialized. Immediately recheck freeze, PR head, base, candidate and protected surfaces. Any movement or retarget invalidates the receipt. A full train tip cannot authorize different intermediate squash trees. Skip held items without silently expanding the approved batch.

4. Reconcile the outcome

Read back actual merged state/SHA and credit, refresh the base, retain artifacts and update only owned private plans. Track the post-merge base validation separately. Do not mark prepared/draft PRs or unmerged patches complete.

Closing/defer/subsumed dispositions need separate explicit per-item owner approval. Prove supersession by affected behavior and direction, not an issue-number match. Keep reporter/contributor credit and explain the precise scope in any authorized public response. Do not close a PR merely because its code was cherry-picked.

End with counts of merged, prepared, held and still-failing items plus exact evidence. Teardown only owned clean backed-up worktrees under the shared teardown protocol. Preserve the shared checkout and do not update memory without a request.

© diegosouzapw, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in config/quality/skill-templates/merge-prs of diegosouzapw/OmniRoute.

Open the folder on GitHubat commit 4ea24a2

Compare with similar skills

Authorized PR Merge Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Authorized PR Merge Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Authorized PR Merge Workflow this skilldiegosouzapw/OmniRoute74k—~1.3kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Git Branch Namingmakeplane/plane61k—~594Automated safety check: PassAGPL-3.0
Creating Description For Gh PRredis/jedis12k—~838Automated safety check: PassMIT

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Git Branch Naming

    makeplane/plane

    Names a new Git branch with a type prefix, the lowercased work item ID and a short kebab-case description, so the ID can be extracted later from the branch name.

    61k GitHub stars~594 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Creating Description For Gh PR

    redis/jedis

    Official

    Generate a clear, concise GitHub PR title and description from the diff between two local git branches, and save it to prDescription.md in the repo root.

    12k GitHub stars~838 tokensUpdated today
    DevelopmentAuto-check passed

  • Create Pull Request with Work Item ID

    makeplane/plane

    Opens a pull request for the current branch using the repo's template, a work item ID in the title and a description filled in from the actual diff.

    61k GitHub stars~824 tokensUpdated yesterday
    DevelopmentAuto-check passed

More from diegosouzapw/OmniRoute

All 50 skills in this repo

  • OmniRoute Backup and Sync CLI

    diegosouzapw/OmniRoute

    Backup and restore OmniRoute data from the CLI. Trigger incremental snapshots, sync to cloud storage, manage backup schedules, and restore from archive files.

    74k GitHub stars~948 tokensUpdated yesterday
    Auto-check passed

  • Quality Scan

    diegosouzapw/OmniRoute

    Runs a scoped, read-only quality scan on a repository candidate and reports exact evidence, failures and frozen debt, without treating a static scan as release acceptance.

    74k GitHub stars~748 tokensUpdated yesterday
    Auto-check passed

  • OmniRoute Provider Management

    diegosouzapw/OmniRoute

    Manages AI provider connections, API keys, OAuth flows and connection tests through OmniRoute's REST API across its 327-provider catalog.

    74k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed

  • OmniRoute Settings API

    diegosouzapw/OmniRoute

    Read and update global application settings: system prompts, thinking budget, IP filters, payload rules, combo defaults, and require-login configuration.

    74k GitHub stars~3.6k tokensUpdated yesterday
    Auto-check passed

  • OmniRoute Database Backups

    diegosouzapw/OmniRoute

    Trigger system backups, restore from backup files, and manage the SQLite database lifecycle. Supports export, import, and incremental snapshot strategies.

    74k GitHub stars~395 tokensUpdated yesterday
    Auto-check passed

  • OmniRoute Batch CLI

    diegosouzapw/OmniRoute

    Submit and monitor batch inference jobs from the CLI. Upload and manage files for batch processing, retrieve results, and integrate batch pipelines with CI/CD…

    74k GitHub stars~565 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Authorized PR Merge Workflow

What does Authorized PR Merge Workflow do?

Works through analyzed pull request plans, repairs approved fixes while keeping contributor credit, validates candidates and merges only owner-authorized groups. This skill executes plans produced by an earlier PR review stage. Before acting it reads the shared base-green, validation-gate, merge-gates, protected-surfaces and credit-preservation documents, whose rules apply throughout.

When should I use Authorized PR Merge Workflow?

Authorized PR Merge Workflow fits situations like: merging a batch of reviewed pull requests that the owner has approved; applying mandatory fixes to a contributor's PR while keeping their authorship; producing a merge dossier before the owner authorizes a group; holding PRs whose required checks are unknown or failing.

How do I install Authorized PR Merge Workflow in Claude Code?

Run `npx skills add diegosouzapw/OmniRoute --skill merge-prs -a claude-code`. Or copy the skill folder (config/quality/skill-templates/merge-prs in diegosouzapw/OmniRoute) into .claude/skills/merge-prs in your project. Claude Code loads it when a task matches its description.

How do I install Authorized PR Merge Workflow in Codex?

Run `npx skills add diegosouzapw/OmniRoute --skill merge-prs -a codex`. Or copy the skill folder (config/quality/skill-templates/merge-prs in diegosouzapw/OmniRoute) into .agents/skills/merge-prs in your project. Codex loads it when a task matches its description.

Can I use Authorized PR Merge Workflow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add diegosouzapw/OmniRoute --skill merge-prs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/merge-prs, .gemini/skills/merge-prs, .github/skills/merge-prs and .opencode/skills/merge-prs in your project.

What does Authorized PR Merge Workflow need to run?

SKILL.md names no scripts, command-line tools or credentials: Authorized PR Merge Workflow is instructions for the agent only. Our summary lists: A repository using the shared pipeline layout, with analyzed PR plans under _tasks/pipeline/prs; Prior review evidence for each pull request.

Does Authorized PR Merge Workflow access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Authorized PR Merge Workflow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Authorized PR Merge Workflow use?

Authorized PR Merge Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Authorized PR Merge Workflow use?

About 1.3k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Authorized PR Merge Workflow?

Skills that share tags, products or a category with Authorized PR Merge Workflow: Finishing a Development Branch (obra/superpowers, 297k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars) and Git Branch Naming (makeplane/plane, 61k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Authorized PR Merge Workflow?

diegosouzapw (a GitHub user) maintains it in diegosouzapw/OmniRoute, which has 74,424 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 8, 2026.

Source: diegosouzapw/OmniRoute on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.