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

LoopX PR Program Manager

by loopx-project in loopx-project/loopx

Tracks a group of pull or merge requests across repositories as durable LoopX state: inventory, reconcile changes, keep priorities and a roadmap, and monitor over time.

Apache-2.0Auto-check passedDevelopment

Install LoopX PR Program Manager

skills CLI
$ npx skills add loopx-project/loopx --skill loopx-pr-program -a claude-code

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

GitHub CLI
$ gh skill install loopx-project/loopx loopx-pr-program --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/loopx-project/loopx.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/loopx-pr-program .claude/skills/loopx-pr-program && 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
loopx-pr-program
GitHub stars
6.2k
Token cost
~1.9k tokens
SKILL.md length
953 words
Files
5 (incl. scripts, references)
Skills in repo
12
Repo updated
First seen
Licence
Apache-2.0

At a glance

Tracks a group of pull or merge requests across repositories as durable LoopX state: inventory, reconcile changes, keep priorities and a roadmap, and monitor over time.

  • Works in 3 steps: completed work, grouped by product theme; → pending work, grouped by product theme,… → merge priority, ordered first by…
  • Keeping track of a set of related pull requests across several repositories
  • SKILL.md covers Route The Request, Start From LoopX State, Acquire A Complete Snapshot and Reconcile Material Changes, plus 4 more sections
  • Runs Python scripts from its folder; calls python and git

What it does

This skill manages a delivery program made of several pull requests or merge requests, in one or more repositories, as saved LoopX state instead of a queue rebuilt from chat memory. It inventories open change requests, reconciles new, merged, closed or retargeted ones, keeps requirement and dependency priorities, and maintains a roadmap document. Deep review goes to the loopx-pr-review skill, and approvals, comments, reruns, retargeting, closing or merging go to the normal provider-specific workflow.

The program is represented by one advancement todo and one grouped continuous_monitor todo with a stable identity, not one monitor per request. Observations are normalized into a provider-neutral snapshot described in `references/snapshot-contract.md`, and a snapshot counts as complete only once the inventory is proven exhaustive; an incomplete one must not advance the baseline. Quiet monitor polls keep the monitor alive without counting as progress. The bundle includes `scripts/diff_snapshot.py`. Updating the roadmap or starting a monitor counts as a write, while ordinary status questions stay read-only.

When your agent uses it

  • Keeping track of a set of related pull requests across several repositories
  • Updating a roadmap document after PRs merge, close or get retargeted
  • Setting up one grouped monitor for check and review changes

Example prompts

  • “Inventory all open PRs for the billing migration across the api and web repos and update the roadmap.”
  • “Reconcile the program since yesterday: which PRs merged, closed or were retargeted?”
  • “Keep monitoring this PR program and only tell me about material changes.”

Requirements

  • LoopX
  • A read interface to the source-control provider

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. completed work, grouped by product theme;
  2. pending work, grouped by product theme, with archived or superseded
  3. merge priority, ordered first by explicit product priority, then dependency,

What it can do on your machine

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

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python
    • git

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

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    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

LoopX PR Program Manager loads about 1.9k tokens when it runs, and up to ~3.2k if it reads all its reference files. Until then it costs about 121 tokens; SKILL.md has 953 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~121
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.2k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from loopx-project/loopx at commit 8205c8b, republished under its Apache-2.0 licence (© loopx-project). 953 words, ~1,950 tokens.

Download SKILL.mdSave it as .claude/skills/loopx-pr-program/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
loopx-pr-program
description
Use when LoopX must manage a multi-PR or multi-MR delivery program across one or more repositories: inventory current change requests, reconcile new/merged/closed or retargeted work, preserve requirement and dependency priorities, maintain a roadmap document, or monitor material lifecycle/check/review changes over time. Use provider-neutral snapshots and one grouped continuous monitor; do not use for deep per-PR code review, approval, commenting, or merge actions.

LoopX PR Program

Manage a delivery program as durable LoopX state instead of rebuilding a queue from chat memory. Keep source acquisition provider-local, normalize observations into one public contract, and write back only material transitions.

Route The Request

Use this workflow when the user asks to manage, prioritize, reconcile, document, or monitor several pull requests or merge requests. Route a deep review of each selected PR to loopx-pr-review. Route approval, comments, reruns, branch retargeting, closing, or merging to the normal provider-specific workflow and require the corresponding authority.

Treat document maintenance and monitor creation as writes. A request to update the roadmap or keep monitoring the program authorizes those scoped writes; an ordinary status question remains read-only.

Start From LoopX State

Start or join the project goal before material work. Represent the program with one advancement todo for the current reconciliation and one continuous_monitor todo for recurring observation. Do not create one monitor todo per change request.

Use a stable monitor identity:

text
task_class=continuous_monitor
action_kind=pr_program_reconcile
target_key=pr-program-<stable-program-id>
cadence=<user cadence or 30m>

Preserve claimed_by, last_checked_at, next_due_at, result_hash, consecutive_no_change, and material_change. Quiet monitor polls keep liveness but do not count as delivery progress, rewrite roadmap documents, or spend progress quota.

Acquire A Complete Snapshot

Use any authorized source-control read interface available in the current environment. Prefer one batch query for inventory and targeted reads for the items that changed. Never encode a private transport command, executable name, credential, internal hostname, or document token in this skill, repository examples, committed fixtures, or public evidence.

Normalize observations using references/snapshot-contract.md. Mark result_completeness.complete=true only after proving the requested repository, author, state, and time-window inventory is exhaustive. An incomplete current snapshot must not make absent rows look closed or removed. Persist the structured scope fingerprint with the baseline. Do not advance the durable baseline or grouped-monitor result_hash from an incomplete snapshot or when the previous and current scope fingerprints differ; otherwise a partial page or narrowed query can create false remove/re-add transitions on the next poll.

Store raw and normalized snapshots under an ignored owner-local directory such as .local/loopx/pr-program/<program-id>/. Verify the path with git check-ignore before writing. If no ignored path is available, use a temporary directory and keep only a redacted evidence summary in LoopX state.

Reconcile Material Changes

Run the bundled delta helper before manually comparing rows:

bash
python skills/loopx-pr-program/scripts/diff_snapshot.py \
  --previous <previous.json> \
  --current <current.json> \
  --output <delta.json>

Omit --previous for the first baseline. The helper treats lifecycle, draft, target branch, head revision, checks, review, work item, requirement, theme, priority, and dependency changes as material. Timestamp-only movement is observation noise. Read the actual description, latest review context, checks, and changed-file evidence for every added or materially changed row before updating the program judgment.

Do not infer motivation or priority from title, number, author, age, or green CI alone. Product requirements set priority. Correctness dependencies and real merge gates determine order within a priority. Record a requirement gap explicitly when no change request implements part of the requested behavior; do not call the requirement complete because a neighboring parameter or feature landed.

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

Compose With An Integration Branch

When several selected change requests belong to one repository, compose this program view with LoopX's integration-branch-reconcile capability. Keep the ownership split explicit:

  • this skill decides which changes belong in the candidate and why;
  • the integration-branch plan records their ordered local source refs and proves what exact code is composed.

Do not populate the plan from every open or P0 change request automatically. Select sources from explicit program scope, dependency order, and current review intent. Refresh the local refs through the authorized host workflow, then verify that each selected ref resolves to the observed head_sha before configuring or syncing the integration branch. A mismatch is source evidence drift, not permission to merge a stale local ref.

Use the same grouped program monitor to read both the normalized change-request delta and loopx integration-branch status --format json. Treat base/source movement, an unexpected integration head, and merge conflict as material program evidence. A monitor poll remains read-only: it may report that the candidate needs reconciliation, but it must not run sync --execute by itself. That command is a separate, explicit local write and never grants authority to push, retarget, approve, or merge a remote change request.

Project The Program

Keep one canonical program projection with three sections:

  1. completed work, grouped by product theme;
  2. pending work, grouped by product theme, with archived or superseded development stacks nested under the surviving change request;
  3. merge priority, ordered first by explicit product priority, then dependency, correctness risk, and current merge gate.

Keep links at the end of each compact row. Preserve the target document's existing heading, color, callout, and strike-through conventions. Update only the affected blocks, refetch them after writing, and verify that unrelated content and resource blocks remain unchanged.

For every priority row, distinguish these facts:

  • shipped behavior and requirement coverage;
  • dependency or recommended merge order;
  • current checks, review, and external work-item gates;
  • missing implementation or validation that no existing change request covers.

Write Back And Continue

After a validated material change:

  1. update the grouped monitor result_hash and reset consecutive_no_change=0;
  2. update the roadmap and refetch the changed sections;
  3. complete the reconciliation todo with compact evidence and create a successor only when concrete follow-up remains;
  4. refresh LoopX state with the actual delivery classification and outcome;
  5. spend quota only after the state and document writeback are validated.

After a quiet poll, update monitor scheduling metadata and increment consecutive_no_change; do not produce a synthetic progress event.

Public And Private Boundary

Commit only the provider-neutral contract, algorithm, and redacted fixtures. Keep private provider adapters, source commands, raw comments, internal URLs, document ids, snapshots, and organization-specific prioritization outside the public repository. Before staging changes to this skill or its resources, scan the exact paths for private hostnames, executable names, credentials, local absolute paths, and raw operating context.

© loopx-project, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (scripts, references) in skills/loopx-pr-program of loopx-project/loopx.

  • SKILL.md
  • .loopx-skill-scope
  • agents/openai.yaml
  • references/snapshot-contract.md
  • scripts/diff_snapshot.py

Open the folder on GitHubat commit 8205c8b

Compare with similar skills

LoopX PR Program Manager 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.

LoopX PR Program Manager compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
LoopX PR Program Manager this skillloopx-project/loopx6.2k—~1.9kAutomated safety check: PassApache-2.0
Releases-morgan-jeffries/apple-mail-fast-mcp104—~1.3kAutomated safety check: PassMIT
PR Review Merge Prepsymfony/symfony31k—~4.4kAutomated safety check: PassMIT
Create PRwanteddev/montage-web117—~6.3kAutomated safety check: NotesMIT
Gh Read Inspectoreclipse-rdf4j/rdf4j420—~950Automated safety check: PassBSD-3-Clause
Create PRyonatangross/orchestkit288—~4.5kAutomated safety check: NotesMIT

Similar skills

  • Release

    s-morgan-jeffries/apple-mail-fast-mcp

    A skill your agent uses when the user wants to release a new version.

    104 GitHub stars~1.3k tokensUpdated 28 days ago
    DevelopmentAuto-check passed

  • PR Review Merge Prep

    symfony/symfony

    Principles for rigorously reviewing a pull request and making it merge-ready.

    31k GitHub stars~4.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Create PR

    wanteddev/montage-web

    Create a GitHub pull request from the current branch. An agent skill from wanteddev/montage-web.

    117 GitHub stars~6.3k tokensUpdated today
    DevelopmentAuto-check: notes

  • Gh Read Inspector

    eclipse-rdf4j/rdf4j

    Retrieve GitHub issues, pull requests, and milestones with read-only, whitelisted gh commands only.

    420 GitHub stars~950 tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Create PR

    yonatangross/orchestkit

    Creates GitHub pull requests with pre-flight validation, conventional title formatting, and structured summary generation.

    288 GitHub stars~4.5k tokensUpdated yesterday
    DevelopmentAuto-check: notes

  • Forgejo CLI

    magnus919/agent-skills

    A skill your agent uses when managing a Forgejo or Gitea server from the terminal: issues, pull requests, repositories, file contents, labels, milestones, releases, webhooks, user settings, or any…

    111 GitHub stars~645 tokensUpdated yesterday
    Backend & APIsAuto-check passed

More from loopx-project/loopx

All 12 skills in this repo

  • LoopX Self Repair

    loopx-project/loopx

    Diagnoses surprising LoopX behavior, such as stale recommendations or tiny progress, assigns it to the responsible layer and repairs it at the lowest durable level.

    6.2k GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • LoopX Auto-Research Worker

    loopx-project/loopx

    Role playbook for a LoopX worker running an auto-research lane, with execution checklists, artifact contracts and stop conditions.

    6.2k GitHub stars~3.5k tokensUpdated today
    Auto-check passed

  • LoopX Benchmark Operator

    loopx-project/loopx

    Operates or analyzes a LoopX-managed benchmark experiment: launching runs, maintaining the experiment board, qualifying integrity, and writing case insights.

    6.2k GitHub stars~3.6k tokensUpdated today
    Auto-check passed

  • LoopX Doc Registry

    loopx-project/loopx

    Registers durable project materials such as design docs, SOPs and research notes in a LoopX project's own registry so future agents can find them without raw URLs or private content.

    6.2k GitHub stars~707 tokensUpdated today
    Auto-check passed

  • LoopX PR Review

    loopx-project/loopx

    Runs an evidence-backed pull request review through the loopx CLI and posts bilingual reviews: a full Chinese review plus one concise English verdict.

    6.2k GitHub stars~3.3k tokensUpdated today
    Auto-check passed

  • LoopX Project Lifecycle

    loopx-project/loopx

    Connects and configures LoopX projects and Goals, repairs project-local state and stale status, syncs registry entries and diagnoses CLI routing.

    6.2k GitHub stars~14k tokensUpdated today
    Auto-check passed

Categories

Questions about LoopX PR Program Manager

What does LoopX PR Program Manager do?

Tracks a group of pull or merge requests across repositories as durable LoopX state: inventory, reconcile changes, keep priorities and a roadmap, and monitor over time. This skill manages a delivery program made of several pull requests or merge requests, in one or more repositories, as saved LoopX state instead of a queue rebuilt from chat memory. It inventories open change requests, reconciles new, merged, closed or retargeted ones, keeps requirement and dependency priorities, and maintains a roadmap document.

When should I use LoopX PR Program Manager?

LoopX PR Program Manager fits situations like: keeping track of a set of related pull requests across several repositories; updating a roadmap document after PRs merge, close or get retargeted; setting up one grouped monitor for check and review changes.

How do I install LoopX PR Program Manager in Claude Code?

Run `npx skills add loopx-project/loopx --skill loopx-pr-program -a claude-code`. Or copy the skill folder (skills/loopx-pr-program in loopx-project/loopx) into .claude/skills/loopx-pr-program in your project. Claude Code loads it when a task matches its description.

How do I install LoopX PR Program Manager in Codex?

Run `npx skills add loopx-project/loopx --skill loopx-pr-program -a codex`. Or copy the skill folder (skills/loopx-pr-program in loopx-project/loopx) into .agents/skills/loopx-pr-program in your project. Codex loads it when a task matches its description.

Can I use LoopX PR Program Manager 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 loopx-project/loopx --skill loopx-pr-program -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/loopx-pr-program, .gemini/skills/loopx-pr-program, .github/skills/loopx-pr-program and .opencode/skills/loopx-pr-program in your project.

What does LoopX PR Program Manager need to run?

Going by SKILL.md and its folder, LoopX PR Program Manager needs Python for the scripts in its folder and the command-line tools its instructions call (python and git). Our summary lists: LoopX; A read interface to the source-control provider.

Does LoopX PR Program Manager access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is LoopX PR Program Manager 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does LoopX PR Program Manager use?

LoopX PR Program Manager is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does LoopX PR Program Manager use?

About 1.9k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.2k tokens, read only when the agent opens those files.

What are the alternatives to LoopX PR Program Manager?

Skills that share tags, products or a category with LoopX PR Program Manager: Release (s-morgan-jeffries/apple-mail-fast-mcp, 104 stars), PR Review Merge Prep (symfony/symfony, 31k stars), Create PR (wanteddev/montage-web, 117 stars) and Gh Read Inspector (eclipse-rdf4j/rdf4j, 420 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains LoopX PR Program Manager?

loopx-project (a GitHub organization) maintains it in loopx-project/loopx, which has 6,167 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 7, 2026.

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