# Loopx PR Program

Use when LoopX must manage a multi-PR or multi-MR delivery program across one or more...

- Repository: https://github.com/loopx-project/loopx (6526 stars)
- Category: Git and review
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add loopx-project/loopx --skill loopx-pr-program -g -a claude-code -y`
Codex: `npx skills add loopx-project/loopx --skill loopx-pr-program -g -a codex -y`
Cursor: `npx skills add loopx-project/loopx --skill loopx-pr-program -g -a cursor -y`
Gemini CLI: `npx skills add loopx-project/loopx --skill loopx-pr-program -g -a gemini-cli -y`

## 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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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.

The rest: https://github.com/loopx-project/loopx/blob/HEAD/skills/loopx-pr-program/SKILL.md