New: 97,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

Green PR Queue

by diegosouzapw in diegosouzapw/OmniRoute

Prepares a maintainer's selected pull request queue against its exact current base, repairs authorized defects while keeping contributor credit, and reports full versus partial validation.

MITAuto-check passedDevelopment

Install Green PR Queue

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

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

GitHub CLI
$ gh skill install diegosouzapw/OmniRoute green-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/green-prs .claude/skills/green-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
green-prs
GitHub stars
74k
Token cost
~991 tokens
SKILL.md length
493 words
Files
1
Skills in repo
50
Repo updated
First seen
Licence
MIT

At a glance

Prepares a maintainer's selected pull request queue against its exact current base, repairs authorized defects while keeping contributor credit, and reports full versus partial validation.

  • Works in 3 steps: Resolve scope and ownership → Prepare and validate → Evidence and handoff
  • Pre-greening a queue of contributor pull requests before a release
  • SKILL.md covers 1. Resolve scope and ownership, 2. Prepare and validate and 3. Evidence and handoff
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Shared policy files come first: base-green.md and validation-gate.md before anything else, and protected-surfaces.md before any instruction-surface change or merge. Scope is the owner's PR list, or the eligible merge-ready and fix-in-place plans in the pipeline folder, with the whole queue only on request. For each PR the agent records state, author, head SHA, base branch and SHA, freeze status and worktree ownership, and treats an in-flight worktree owned by another session as a HOLD. It inspects the exact base first and repairs confirmed base defects in a separate PR.

Each PR gets its own branch and worktree. The agent checks the local SHA matches the live head before editing and that the remote is unchanged before pushing, keeps the original author's work with co-authorship, and never overwrites or closes a PR to take credit. It reproduces the failure, applies the fix, runs focused and affected suites and keeps raw logs. Fast checks cannot grant merge readiness, baselines and thresholds are not loosened, and merging itself needs separate owner authorization.

When your agent uses it

  • Pre-greening a queue of contributor pull requests before a release
  • Repairing a contributor's failing PR without taking over the credit
  • Deciding whether a failing check comes from the base branch or from the PR
  • Reporting whether a PR passed full or only partial validation

Example prompts

  • “Green the PRs on my approved list against the current release base and report what is fully validated.”
  • “This contributor PR also fails on the base, so fix the base defect in its own PR first.”
  • “Prepare the analyzed PR plans, but hold anything whose worktree belongs to another session.”

Requirements

  • The shared policy files base-green.md, validation-gate.md and protected-surfaces.md
  • Git with worktree support

Workflow steps

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

  1. Resolve scope and ownership
  2. Prepare and validate
  3. Evidence and handoff

What it can do on your machine

Read from SKILL.md and the folder at commit 8ad6b1c. 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

Green PR Queue loads about 991 tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 493 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
~991

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 8ad6b1c, republished under its MIT licence (© diegosouzapw). 493 words, ~991 tokens.

Download SKILL.mdSave it as .claude/skills/green-prs/SKILL.md (or your agent's skills folder).
name
green-prs
description
Inspect and prepare the selected PR queue against its exact current base, repair authorized defects with contributor credit, and report full versus partial validation. Use for maintainer pre-greening; merging requires separate owner authorization and the shared merge gates.

Green the selected PR queue

Read ../_shared/base-green.md and ../_shared/validation-gate.md first. Read ../_shared/protected-surfaces.md before any instruction-surface change or merge. The current candidate's workflows and versioned policy define required gates; do not assume release PRs are fast-only or use a handwritten gate count.

1. Resolve scope and ownership

Use the owner's PR list. Otherwise consume eligible merge-ready / fix-in-place plans in _tasks/pipeline/prs/1-analyzed/; use the whole queue only when requested or no pipeline items exist. Report drafts separately unless the owner included them. Record current state, author, head SHA, base branch/SHA, freeze and worktree ownership. An in-flight worktree belonging to another session means HOLD for that item. Never work in the shared checkout, stash, or silently retarget a frozen release.

Inspect the exact base first. An incident is diagnostic history, not proof of inheritance. Match each failure signature against the exact base under comparable runtime and configuration. Repair confirmed base defects in a dedicated PR before using them to assess contributor changes. Base-red does not waive a required gate.

2. Prepare and validate

Use one isolated branch/worktree per PR. Before editing a contributor branch, verify the checked-out SHA equals its observed live head. Before pushing, verify the remote still equals the observed predecessor; a concurrent change means HOLD. Keep the original author's work and attribution, add appropriate co-authorship, and never overwrite or close the PR to take credit. A locked fork needs the owner-reviewed credit-preserving fallback, not a destructive reconstruction.

Run a RED reproduction, implement the proven fix, then focused and affected suites. Dependencies must match the candidate lockfile/toolchain; borrowed tools are diagnostic only. A build needs physical dependencies, not an external symlink. Preserve raw logs, exits, artifacts, test discovery and all existing assertions.

Fast checks may prioritize work, but cannot grant merge readiness. Full acceptance covers every applicable required lane, including both test runners, coverage, security and build/package/boot where required. DRIFT is a diagnosis, not PASS; do not increase baselines, lower thresholds or accept flaky required checks. Fork action_required is a trust/approval HOLD, never a code failure or automatic approval instruction. Re-running an old run does not move its recorded candidate.

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

3. Evidence and handoff

Do not claim/move pipeline plans on behalf of the merge executor. Record a structured receipt containing base SHA, head SHA, candidate SHA/tree, policy/profile, run IDs/attempts, artifact references, validation level and timestamp. A legacy pre_greened head-only stamp or fast-gates-only note is partial evidence only. Any relevant identity/policy change invalidates admission and requires revalidation.

Report each PR's causal classification, repairs, exact evidence and remaining lanes. Separate PASS, PARTIAL, BASE-RED, PR-RED, INFRA-RED and ACTION_REQUIRED/HOLD. This skill prepares the queue and never closes PRs. If the owner explicitly asks to merge identified items, first follow the complete ../_shared/merge-gates.md protocol, including protected-surface and per-group authorization. Do not bypass required checks because the same failure affects many PRs.

Preserve work until its commits and evidence are safely retained. Teardown only owned, clean, fully backed-up worktrees under ../_shared/worktree-teardown.md. Do not delete contributor remote branches or another session's work.

© 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/green-prs of diegosouzapw/OmniRoute.

Open the folder on GitHubat commit 8ad6b1c

Compare with similar skills

Green PR Queue 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.

Green PR Queue compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Green PR Queue this skilldiegosouzapw/OmniRoute74k—~991Automated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Pre-Release PR Triagejamiepine/voicebox57k—~3.1kAutomated safety check: PassMIT
React Router PR Finish Lineremix-run/react-router57k—~1.4kAutomated safety check: PassMIT
Verdaccio PR Reviewverdaccio/verdaccio18k—~1.7kAutomated safety check: PassMIT
Ansible Backport Creatoransible/ansible71k—~1.2kAutomated safety check: PassGPL-3.0

Similar skills

  • 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

  • Pre-Release PR Triage

    jamiepine/voicebox

    Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.

    57k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check passed

  • React Router PR Finish Line

    remix-run/react-router

    Takes a blocked community pull request in React Router and adds the missing tests, change file or docs so it can merge, working on the contributor's branch.

    57k GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Verdaccio PR Review

    verdaccio/verdaccio

    Reviews an existing verdaccio/verdaccio pull request end to end, verifies each finding and reports whether it is mergeable, optionally fixing it on the PR branch.

    18k GitHub stars~1.7k tokensUpdated today
    DevelopmentAuto-check passed

  • Ansible Backport Creator

    ansible/ansible

    Creates backports of a merged Ansible devel pull request onto the right stable branches by cherry-picking its merge commit onto new backport branches.

    71k GitHub stars~1.2k tokensUpdated today
    DevelopmentAuto-check passed

  • Codewhale Landing Workflow

    codewhale-hq/Codewhale

    Decides how verified work should reach main, directly, in a worktree or on an integration branch, while keeping contributor credit and respecting merge gates.

    41k GitHub stars~1.6k tokensUpdated today
    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 today
    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 starsUsed in 1 repo~3.6k tokens
    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 today
    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 starsUsed in 1 repo~395 tokens
    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 today
    Auto-check passed

  • OmniRoute LLM Cache

    diegosouzapw/OmniRoute

    Documents OmniRoute's cache endpoints for reading cache statistics and clearing entries, statistics or the reasoning cache, with notes on TTL and similarity settings.

    74k GitHub starsUsed in 1 repo~529 tokens
    Auto-check passed

Categories

Questions about Green PR Queue

What does Green PR Queue do?

Prepares a maintainer's selected pull request queue against its exact current base, repairs authorized defects while keeping contributor credit, and reports full versus partial validation. md before any instruction-surface change or merge. Scope is the owner's PR list, or the eligible merge-ready and fix-in-place plans in the pipeline folder, with the whole queue only on request.

When should I use Green PR Queue?

Green PR Queue fits situations like: pre-greening a queue of contributor pull requests before a release; repairing a contributor's failing PR without taking over the credit; deciding whether a failing check comes from the base branch or from the PR; reporting whether a PR passed full or only partial validation.

How do I install Green PR Queue in Claude Code?

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

How do I install Green PR Queue in Codex?

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

Can I use Green PR Queue 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 green-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/green-prs, .gemini/skills/green-prs, .github/skills/green-prs and .opencode/skills/green-prs in your project.

What does Green PR Queue need to run?

SKILL.md names no scripts, command-line tools or credentials: Green PR Queue is instructions for the agent only. Our summary lists: The shared policy files base-green.md, validation-gate.md and protected-surfaces.md; Git with worktree support.

Does Green PR Queue 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 Green PR Queue 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 Green PR Queue use?

Green PR Queue 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 Green PR Queue use?

About 991 tokens (SKILL.md is roughly 4k 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 Green PR Queue?

Skills that share tags, products or a category with Green PR Queue: Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Pre-Release PR Triage (jamiepine/voicebox, 57k stars), React Router PR Finish Line (remix-run/react-router, 57k stars) and Verdaccio PR Review (verdaccio/verdaccio, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Green PR Queue?

diegosouzapw (a GitHub user) maintains it in diegosouzapw/OmniRoute, which has 73,701 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 6, 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.