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

Re0 Merge

by LilMGenius in LilMGenius/paperthin

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve…

MITAuto-check passedDevelopment

Install Re0 Merge

skills CLI
$ npx skills add LilMGenius/paperthin --skill re0-merge -a claude-code

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

GitHub CLI
$ gh skill install LilMGenius/paperthin re0-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/LilMGenius/paperthin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/depth/re0-merge .claude/skills/re0-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
re0-merge
GitHub stars
1.1k
Token cost
~1.2k tokens
SKILL.md length
708 words
Files
1
Skills in repo
28
Repo updated
First seen
Licence
MIT

At a glance

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve…

  • Works in 7 steps: Gate before landing. An additive… → Cold-read it first. Read the… → Verify, do not re-fix. Where the author… → …
  • Reviewing a pull request
  • SKILL.md covers Goal, Workflow, Rules and Verification
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Re0 Merge is an agent skill from LilMGenius/paperthin. Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the author.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Essays and academic help and Pull requests. The repository describes itself as: Low-level agentic design patterns. Turning old engineering wisdom into reflexes your agent reaches for on its own—on any agent. The licence is MIT.

When your agent uses it

  • Reviewing a pull request
  • As any collaborator
  • Not only the author

Example prompts

  • “/re0-merge”

Workflow steps

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

  1. Gate before landing. An additive contribution is declined by default; the burden is on the addition to show the suite is worse without it…
  2. Cold-read it first. Read the contribution end to end with fresh eyes (a shower pass when installed) before deciding; a name or claim that…
  3. Verify, do not re-fix. Where the author already pushed a fix, prove it with a throwaway regression case rather than rewriting it; the…
  4. Approve as you accept, then land on a land/pr- branch (a range only for a genuine multi-PR batch). Submit the approving review the moment…
  5. Complete a new skill, don't merge it raw. Get the name right (a plain real word or tight compression, no opaque coinage), the invocation…
  6. After the release the contribution shipped in confirms, close the PR with the comment. Close it in the same motion as a comment that…
  7. The comment credits and explains, warmly. Shout the contribution out in the release notes with its PR number and author handle; and if you…

What it can do on your machine

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

Re0 Merge loads about 1.2k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 708 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~84
When it runs · the whole SKILL.md, loaded when a task matches
~1.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); files beside SKILL.md are not scanned.

SKILL.md

The full file from LilMGenius/paperthin at commit 7d5dc62, republished under its MIT licence (© LilMGenius). 708 words, ~1,177 tokens.

Download SKILL.mdSave it as .claude/skills/re0-merge/SKILL.md (or your agent's skills folder).
name
re0-merge
description
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the author.
disable-model-invocation
true

Land a contribution fairly: credit preserved, the maintainer's changes legible, accepted on the record.

Goal

A contribution is a gift with a permanent carrying cost, and a review either honors both or fails one. re0-merge walks whoever reviews — any collaborator or maintainer, not just the author — through accepting a pull request the way this suite does: judged against the thesis, landed with the author's authorship intact, the maintainer's own edits kept as separate commits, and closed with an approval and a credit rather than a silent rejection.

Workflow

  1. Gate before landing. An additive contribution is declined by default; the burden is on the addition to show the suite is worse without it, not on you to justify a no. Judge each PR alone, never as a batch: a bug-fix subtracts a defect and is the easy yes; new tooling earns a place only if it mechanizes a rule already enforced by hand; a new skill lands only if it closes a real gap no existing one covers. A well-reasoned decline is a shipped outcome, not a failure.
  2. Cold-read it first. Read the contribution end to end with fresh eyes (a shower pass when installed) before deciding; a name or claim that reads clean to its author may not to a stranger.
  3. Verify, do not re-fix. Where the author already pushed a fix, prove it with a throwaway regression case rather than rewriting it; the credit for the fix is theirs.
  4. Approve as you accept, then land on a land/pr-<n> branch (a range only for a genuine multi-PR batch). Submit the approving review the moment you decide to accept, before the land — it is a verdict on the contributor's code, not a receipt for a release, and giving it now (not bundled with the later close) is what keeps a closed-not-merged PR reading as accepted. Then accept each contributor commit with its authorship preserved (you become the committer; clean the message with re0-git), add every maintainer change as its own separate commit so the credit split stays legible, and fast-forward into main.
  5. Complete a new skill, don't merge it raw. Get the name right (a plain real word or tight compression, no opaque coinage), the invocation right (model- vs user-invoked), and the home right; then register it on every roster surface (plugin.json, the README Index in root and every localized copy, re0-upgrade's Current catalog, scripts/catalog.cjs) so no drift-guard trips.
  6. After the release the contribution shipped in confirms, close the PR with the comment. Close it in the same motion as a comment that credits and explains — never a silent close, and never before the release lands. The approval from step 4 already records it as accepted; this step only closes and explains.
  7. The comment credits and explains, warmly. Shout the contribution out in the release notes with its PR number and author handle; and if you renamed or reframed anything, the closing comment thanks the author, says what changed and why, points at the release it shipped in, and hands the credit for the core idea back to them.
Show full SKILL.md (193 more words)Show less

Rules

  • Default-deny for surface, but decline well: a reason tied to the thesis, the branch kept, never a silent close (negatives-as-corpus).
  • Preserve authorship. The contributor authors their commit; every maintainer edit is a separate commit under the maintainer's name.
  • Approve as you accept, before the land — not bundled with the close after the release. The approval is a verdict on the contributor's code, not a receipt for a release that could fail. Any collaborator or maintainer with review access does this, not one fixed reviewer.
  • Explain every deviation to the author, in their favor. A rename or reframe they did not ask for gets its reason.
  • Reviewer-agnostic and self-degrading: run whatever pipeline skills are installed (shower, re0-git, re0-release), and do their step by hand when they are not.

Verification

Before finishing:

  1. Every landed contribution kept its author's authorship, with maintainer edits as separate commits.
  2. The PR was approved before it was closed, and closed with a credit comment.
  3. A new skill is registered on every roster surface, checks green.
  4. Every decline names a thesis-tied reason and keeps its branch.
  5. Any rename or reframe was explained to the author.

© LilMGenius, 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 skills/depth/re0-merge of LilMGenius/paperthin.

Open the folder on GitHubat commit 7d5dc62

Compare with similar skills

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

Re0 Merge compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Re0 Merge this skillLilMGenius/paperthin1.1k—~1.2kAutomated safety check: PassMIT
Vibe Slop Filterash1794/vibe-engineering163—~2.3kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 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
PR Design DocOpenHands/OpenHands91k—~2.4kAutomated safety check: PassMIT

Similar skills

  • Vibe Slop Filter

    ash1794/vibe-engineering

    Strips AI-generation "smell" from prose before it ships (READMEs, docs, release notes, PR descriptions, posts, emails).

    163 GitHub stars~2.3k tokensUpdated 3 days ago
    DevelopmentAuto-check passed

  • 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

  • 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

  • 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…

    91k 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 LilMGenius/paperthin

All 28 skills in this repo

  • Modelchk

    LilMGenius/paperthin

    Size a task's run before spending it: the cheapest sufficient capability tier (fast, standard, frontier) and the reasoning effort within it, on a neutral scale that binds to whatever levels the…

    1.1k GitHub stars~1.6k tokensUpdated 10 days ago
    Auto-check passed

  • Re0 Loop

    LilMGenius/paperthin

    Run repeated build - QA - re0-memo - re0-work cycles while preserving learning and letting code die.

    1.1k GitHub stars~579 tokensUpdated 10 days ago
    Auto-check passed

  • Autobahn

    LilMGenius/paperthin

    Carve guardrail-adjacent items out of scope with safe alternatives before risk-adjacent work starts, then run the safe remainder at full strength in a fresh subagent that only ever sees the carved…

    1.1k GitHub stars~2.1k tokensUpdated 10 days ago
    Auto-check passed

  • Catchup

    LilMGenius/paperthin

    Rebuild the human's lost context on a project from live state, in plain language: what needs them, what changed, what new words mean.

    1.1k GitHub stars~785 tokensUpdated 10 days ago
    Auto-check passed

  • Debloat

    LilMGenius/paperthin

    Compress an artifact that has accreted into bloat — padding, over-qualification, fused sentences, walls of enumeration, adjacent restatement — down to its load-bearing density, meaning preserved.

    1.1k GitHub stars~813 tokensUpdated 10 days ago
    Auto-check passed

  • Factchk

    LilMGenius/paperthin

    Verify reality-grounded claims against external sources in both directions before they ship — could the 'absurd' be real, could the 'obvious' be false or long-established?

    1.1k GitHub stars~717 tokensUpdated 10 days ago
    Auto-check passed

Categories

Questions about Re0 Merge

What does Re0 Merge do?

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve…. Re0 Merge is an agent skill from LilMGenius/paperthin. Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing.

When should I use Re0 Merge?

Re0 Merge fits situations like: reviewing a pull request; as any collaborator; not only the author.

How do I install Re0 Merge in Claude Code?

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

How do I install Re0 Merge in Codex?

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

Can I use Re0 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 LilMGenius/paperthin --skill re0-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/re0-merge, .gemini/skills/re0-merge, .github/skills/re0-merge and .opencode/skills/re0-merge in your project.

What does Re0 Merge need to run?

SKILL.md names no scripts, command-line tools or credentials: Re0 Merge is instructions for the agent only.

Does Re0 Merge 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 Re0 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 Re0 Merge use?

Re0 Merge 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 Re0 Merge use?

About 1.2k tokens (SKILL.md is roughly 4.7k 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 Re0 Merge?

Skills that share tags, products or a category with Re0 Merge: Vibe Slop Filter (ash1794/vibe-engineering, 163 stars), Finishing a Development Branch (obra/superpowers, 297k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars) and Check PR (onyx-dot-app/onyx, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Re0 Merge?

LilMGenius (a GitHub user) maintains it in LilMGenius/paperthin, which has 1,130 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 1, 2026.

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