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 Merge

by loopx-project in loopx-project/loopx

Optional maintainer workflow for the approval, merge-readiness, or authorized self-merge decision on a LoopX pull request.

Apache-2.0Auto-check passedDevelopment

Install Loopx PR Merge

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

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

GitHub CLI
$ gh skill install loopx-project/loopx loopx-pr-merge --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-merge .claude/skills/loopx-pr-merge && 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-merge
GitHub stars
6.2k
Token cost
~1.6k tokens
SKILL.md length
868 words
Files
2
Skills in repo
12
Repo updated
First seen
Licence
Apache-2.0

At a glance

Optional maintainer workflow for the approval, merge-readiness, or authorized self-merge decision on a LoopX pull request.

  • Works in 3 steps: Run loopx --format json pr-review… → Apply completion_gate literally, and… → Immediately before the merge, run `loopx…
  • Tasks that involve Pull requests
  • SKILL.md covers Decision Precondition, Configured CI Waiting, Decision Workflow and Product And Architecture…, plus 3 more sections
  • Calls git and gh

What it does

Loopx PR Merge is an agent skill from loopx-project/loopx. Optional maintainer workflow for the approval, merge-readiness, or authorized self-merge decision on a LoopX pull request. Requires the exact-head review evidence from loopx pr-review. Review depth, verdicts, review comments, and the published review format belong to loopx-pr-review.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Development, covering Pull requests. The repository describes itself as: A control plane with a durable state kernel for long-horizon agents and teams. Keep work moving and improving across sessions, with less human attention. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Pull requests

Example prompts

  • “/loopx-pr-merge”

Workflow steps

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

  1. Run loopx --format json pr-review --state all, or use the installed
  2. Apply completion_gate literally, and re-read the remote head immediately
  3. Immediately before the merge, run `loopx --format json pr-review --goal-id

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

    Shell commands in SKILL.md call:

    • git
    • gh

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

  • Network

    No URLs in SKILL.md. Its commands use git and gh, 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 Merge loads about 1.6k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 868 words of instructions outside code blocks.

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

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 loopx-project/loopx at commit 8205c8b, republished under its Apache-2.0 licence (© loopx-project). 868 words, ~1,619 tokens.

Download SKILL.mdSave it as .claude/skills/loopx-pr-merge/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
loopx-pr-merge
description
Optional maintainer workflow for the approval, merge-readiness, or authorized self-merge decision on a LoopX pull request. Requires the exact-head review evidence from `loopx pr-review`. Review depth, verdicts, review comments, and the published review format belong to loopx-pr-review.

LoopX PR Merge

Optional maintainer workflow. It lives in the repository and stays outside the default installed skill set, so a host that never merges LoopX pull requests is not affected by it. Install or copy it deliberately when a host needs to make merge decisions.

The built-in pull-request-review capability owns review depth, evidence requirements, completeness, and verdict policy. This skill owns one narrower decision: whether this pull request may be approved or merged now, under which authority, and with what recorded validation.

Decision Precondition

A merge, approval, self-merge, or admin-bypass decision requires review evidence for the exact head being merged. A merge decision without this evidence is not authorized: a diff read, green CI, or pull-request metadata is not a substitute.

  1. Run loopx --format json pr-review --state all, or use the installed loopx-pr-review skill, and preserve agent_response_contract.review_execution_contract. Execute the review plan, review_template, and evidence_commands it names for every changed surface.
  2. Apply completion_gate literally, and re-read the remote head immediately before the decision.
  3. Immediately before the merge, run loopx --format json pr-review --goal-id GOAL --repo OWNER/REPO --check-merge-readiness NUMBER@HEAD_OID. Merge only when it returns ready=true for that unchanged head; this records the compact Goal readiness observation consumed by future review queues.

A rebase or head update restarts review, and admin bypass never overrides this gate: it needs explicit owner authorization and never substitutes for the evidence.

Configured CI Waiting

Pass --goal-id GOAL for managed merges and follow resolved wait_for_ci. The default is true. When false, do not query, poll, or wait for CI; complete required local validation and exact-head review/thread checks. GitHub BLOCKED then reports separately authorized admin bypass, never permission to merge.

Decision Workflow

  1. Read the repository AGENTS.md, the pull-request diff, the changed paths, the local validation results, and the latest comments.
  2. Confirm that the repository's own self-merge policy covers the changed surfaces. The usual LoopX shape is single-purpose and validated work with no private state, no public evidence-policy change, no destructive git action, and no unreviewed runtime, permission, benchmark, or storage-authority behavior.
  3. Write the product and architecture judgment below, then produce the exact-scope change-quality receipt when the goal enables that policy.
  4. Decide: approve, self-merge with owner authorization, request changes, or hold for the maintainer path. Record the decision on the pull request with the changed surfaces, the checks that ran, failures and skips, manual holds, and the reason that coverage is enough. Record it as a published review on the exact head, not as a summary in another channel: on an author-owned PR GitHub blocks formal self-approval, so the record is the COMMENTED review carrying the approval conclusion and the English verdict. A self-merge whose head carries no such record is a process gap to repair, not an authorized merge.
  5. After the merge, sync the local default branch, leave unrelated dirty worktree state alone, and update LoopX todo or evidence when the work is tracked.
Show full SKILL.md (384 more words)Show less

Product And Architecture Judgment

  • Motivation: which product or kernel problem the change solves.
  • Solved or not: whether the diff plus validation prove it, and what coverage stays partial.
  • User and operator impact: which bad case becomes safer, clearer, or faster.
  • Main risk: compatibility, hot path, migration, public and private boundary, permission, benchmark validity, or installed-user risk.
  • Design judgment: reusable contract or ad hoc patch, and the cleaner general alternative when one exists.

Findings still lead. This layer decides whether a broad change should be split, held, self-merged with owner authorization, or followed by a focused cleanup.

Validation Checklist

Use the narrowest meaningful validation, but do not skip it:

  • a syntax or compile check for each changed language;
  • the capability-owned smoke or test suite for each changed surface;
  • a CLI or schema smoke when a command, packet, or schema changed;
  • diff hygiene: git diff --check <base>...HEAD or the local equivalent;
  • a public and private boundary scan when public docs, fixtures, evidence, or examples changed;
  • the repository's risk-based pre-merge gate, when it provides one;
  • a real-path check against the production entrypoint for runtime, storage, or authority changes, with a stated evidence gap when that environment is unavailable.

When validation cannot run, say exactly why in both the pull-request decision comment and the chat summary.

Literal-Safe GitHub Text

Treat PR bodies, review comments, issue comments, and release notes as data, not as shell source.

  • Never pass Markdown-rich text through a double-quoted shell --body argument. Backticks trigger command substitution before gh receives the text.
  • Write multiline text into an ignored temporary body file, scan that file for public and private boundary violations, and use --body-file or pipe a JSON body into gh api --input -.
  • For an existing release body, avoid partial byte or character-index slicing, especially with non-ASCII text. Build the complete replacement body, update it atomically, then compare the remote body hash with the reviewed file.
  • After every public text mutation, read the rendered body back and scan for local paths, command output, interpolation artifacts, and damaged adjacent sections before proceeding.

Review Handoff

Use loopx-pr-review for review evidence, key-code explanations, and the published review format; if it is unavailable, repair the LoopX install instead of reconstructing the review manually. This skill adds the decision and its authorization and validation evidence, and never defines a second review format.

© 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 1 other file in skills/loopx-pr-merge of loopx-project/loopx.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 8205c8b

Compare with similar skills

Loopx PR Merge 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 Merge compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Loopx PR Merge this skillloopx-project/loopx6.2k—~1.6kAutomated safety check: PassApache-2.0
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Understand Diff AnalysisEgonex-AI/Understand-Anything85k1 repos~1.4kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated 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.

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

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    85k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed

  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    90k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

More from loopx-project/loopx

All 12 skills in this repo

  • LoopX PR Program Manager

    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.

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

  • 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

Categories

Questions about Loopx PR Merge

What does Loopx PR Merge do?

Optional maintainer workflow for the approval, merge-readiness, or authorized self-merge decision on a LoopX pull request. Loopx PR Merge is an agent skill from loopx-project/loopx. Optional maintainer workflow for the approval, merge-readiness, or authorized self-merge decision on a LoopX pull request.

When should I use Loopx PR Merge?

Loopx PR Merge fits situations like: tasks that involve Pull requests.

How do I install Loopx PR Merge in Claude Code?

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

How do I install Loopx PR Merge in Codex?

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

Can I use Loopx PR Merge 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-merge -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-merge, .gemini/skills/loopx-pr-merge, .github/skills/loopx-pr-merge and .opencode/skills/loopx-pr-merge in your project.

What does Loopx PR Merge need to run?

Going by SKILL.md and its folder, Loopx PR Merge needs the command-line tools its instructions call (git and gh).

Does Loopx PR Merge access the network?

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

Is Loopx PR Merge 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 Loopx PR Merge use?

Loopx PR Merge 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 Merge use?

About 1.6k tokens (SKILL.md is roughly 6.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 Loopx PR Merge?

Skills that share tags, products or a category with Loopx PR Merge: Finishing a Development Branch (obra/superpowers, 296k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 85k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Loopx PR Merge?

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.