How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/lilmgenius/paperthin --skill re0-mergeBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
Land a contribution fairly: credit preserved, the maintainer's changes legible, accepted on the record.
Goal
A review must respect the contribution and its permanent carrying cost. re0-merge guides any collaborator or maintainer, not just the author, through judging a pull request against the suite's thesis, landing it by the smallest of three outcomes it needs (as it is, with follow-up commits on its own branch, or carried into a new PR), preserving contributor authorship, keeping maintainer edits in separate commits, and closing with approval and credit.
Workflow
- Gate before landing. Decline additions by default: the addition must show the suite is worse without it. Judge each PR alone, never as a batch. A bug-fix removes a defect and is the easy yes; tooling earns a place only if it mechanizes a rule already enforced by hand; a new skill must close a real gap no existing skill covers. A well-reasoned decline is a completed outcome.
- Cold-read it first. Before deciding, read the entire contribution as a stranger would, calling the Skill tool with "shower" when it is installed. A name or claim clear to its author may confuse another reader.
- 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.
- Approve as you accept. Submit approval when you decide to accept, before landing. This verdict on the contributor's code records the PR as accepted even when it later closes as superseded rather than merged.
- Land by the smallest outcome the PR needs:
- As it is. It needs no change, and every check it triggers ran and passed (a job whose real steps were all skipped did not run), so land it by step 7, since its head already contains the base.
- Follow-up commits. It needs changes the maintainer can make (an update from the base branch, a fix, a test, a rename). Push them onto the contributor's branch as separate maintainer commits, then land it by step 7. This needs the PR setting that lets a maintainer push to the contributor's branch ("allow edits by maintainers" on GitHub); when it is off, ask the contributor to turn it on. When the base moved, ask the contributor to rebase onto it, since a merge commit cannot land on a linear history and a maintainer's rebase makes the maintainer the committer of their commits; when they cannot, rebase it yourself with each commit's author kept, push with
--force-with-leaseso nothing they pushed since is dropped, and tell them. Prefer this to closing: the PR, its review and its author stay where they started, and their commits land under their own name, where a carry would count them only as a co-author. - Carry. It needs a rewrite, targets the wrong base branch, or its branch cannot take the maintainer's push. Open a new PR from a maintainer branch (
carry/pr-<n>) that cherry-picks the contributor's commits with their authorship kept (you become the committer) or, where their code is rewritten, credits them with aCo-authored-bytrailer. Its body links the original (Carries #123 by @handle) and says what differs and why; each maintainer change is a separate commit. Once the carry lands, close the original as superseded with a comment that thanks the author, links the carry, and explains the difference.
- Link every issue it resolves. The PR body names each issue with its own closing keyword (
Fixes #123, fixes #124), since a bare#123mention or a list under one keyword links nothing, and an issue closed by hand keeps no record of what fixed it. GitHub honors the keywords only for a PR into the default branch, so a PR into any other branch, or an issue the body missed, is linked from the issue's Development section, which accepts a merged PR as well; a keyword edited into a merged PR's body still links when its base is the default branch. Read each link back from the issue'sclosedByPullRequestsReferencesbefore calling the work landed. - Land the checked head by fast-forward, which keeps the history linear and lands every commit exactly as the head the checks passed on holds it: a host's squash re-creates the PR as one commit under the host's signature, and GitHub's rebase merge re-creates each commit unsigned. Where the repository's commit form names the pull request in the subject it lands under (in paperthin, the PR's title followed by
(#<n>)), the commit that lands last carries it: its subject is that title and number, stating what the whole PR makes true, and its bullets say what that commit itself changes. The contributor amends their head once the PR has a number, the maintainer's last follow-up commit carries it, or the maintainer amends the contributor's head subject, keeping its author and becoming its committer; a number already on an earlier commit stays, since rewriting it changes a contributor's commit for nothing. Fetch the head (git fetch origin pull/<n>/head), confirm it is the PR's head (gh pr view <n> --json headRefOid) and contains the base (git merge-base --is-ancestor origin/<default> <head-sha>), wait for the required checks on it, and push it (git push origin <head-sha>:refs/heads/<default>); then fetch and confirm the default branch points at that head and the host shows the PR merged. On GitHub that push passes a pull-request rule only while the ruleset allows the rebase method alone, which refuses the squash and merge buttons, and the repository's merge settings turn rebase off, which hides the one button left; check what your host allows before relying on it. An as-is or follow-up PR lands as the contributor's commits with the maintainer's after them, and a carry as the maintainer's branch. When a branch commit's message needs cleaning before landing, tell the user to run/re0-giton it. - Complete a new skill before landing. Give it a plain real word or tight compression as its name, never an opaque coinage; choose the right model- or user-invocation lane and home. Register it on every roster surface the repository's contributor guide lists (in this repository,
plugin.json, the README Index in root and every localized copy, andre0-upgrade's Current catalog) so no drift-guard trips. - Comment after the release confirms. Wait for the release containing the contribution to land, then comment on each landed PR, a superseded original included, with a credit that links the release. Never close silently. Step 4's approval already records acceptance; this step credits and explains.
- Credit and explain warmly. Credit the contribution in the release notes with its original PR number and author handle, naming what the work accomplished. If anything was renamed or reframed, the comment thanks the author, explains what changed and why, links the release it shipped in, and credits them for the core idea.
Rules
- User-invoked on purpose: reviewing and landing a contribution is a deliberate maintainer act, and a review reflex in reach would bias the agent toward merging.
- Default-deny for surface, but decline well: a reason tied to the thesis, the branch kept, never a silent close (negatives-as-corpus).
- A reply written to one contributor, a decline included, opens with
Thanks, @handle.and goes straight to the point. Write the handle in when the reply is posted, since not every host notifies a mention added by an edit. - Preserve authorship. The contributor authors their commits, which land as the checked head holds them, and a rebase onto the base or a numbered head subject keeps their author while the maintainer becomes the committer; every maintainer edit is a separate commit under the maintainer's name; a carry keeps the contributor's commits or names them in
Co-authored-by. - Land the smallest outcome that fits: as it is before follow-up commits, follow-up commits before a carry. A carry closes its original only as superseded, with a credit comment.
- Approve on acceptance, before landing, separately from the landing and the release comment. Approval judges the contributor's code even if the release later fails. Any collaborator or maintainer with review access can do this.
- Explain every deviation to the author, in their favor. A rename, reframe or carry they did not ask for gets its reason.
- Call the Skill tool with "shower" when it is installed and perform its steps by hand when it is not.
re0-gitandre0-releaseare user-invoked, so this skill never calls them: it tells the user to run/re0-giton the message to clean and/re0-releasefor the release to cut.
Verification
Before finishing:
- The PR was approved before it landed or was superseded.
- It landed by the smallest outcome that fits, and the PR record says which and why.
- Every issue it resolves lists it under Development, read back from
closedByPullRequestsReferences. - Every landed contribution kept its author's credit (their own commits for an as-is or follow-up PR, the kept commits or a
Co-authored-bytrailer for a carry), with maintainer edits as separate commits on top of the contributor's, none of which was rewritten beyond a rebase onto the base or the number on the head subject. - The default branch moved by fast-forward to the PR's checked head, the subject it landed under follows the repository's commit form, and every commit landed exactly as that head held it.
- A carried original is closed as superseded with a comment linking the carry, and every landed PR has a credit comment linking the release.
- A new skill is registered on every roster surface, checks green.
- Every decline names a thesis-tied reason and keeps its branch.
- Any rename, reframe or carry was explained to the author.