pr-simplify
Skill395k starsChanged todayMITView on GitHub
Simplify your own change to its smallest complete fix. Use before opening a PR, before pushing large repairs to one, or when asked to shrink a PR or clean up slop.
10 other projects use a version of this, 5 of them edited; 1 new project in the last 4 weeks, against 4 the 4 before.
How people change it
All 7 edited versions we compared keep every one of its 2 rules.
Of the 7 edited versions we compared: 7 keep every rule.
We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.
Adopted by
Cooling: 1 new project took it in the last 4 weeks, 0.3× the 4 weeks before.thin data
Most recently taken up by
- shanselman/openclaw-windows-hubtheir own version, first seen Nov 2, 2026
- openclaw/openclaw-windows-nodetheir own version, first seen Nov 1, 2026
- openclaw/openclawword for word, first seen Nov 1, 2026
- Djarvur/go-ultimateedited, first seen Nov 1, 2026
- bighamx/openclaw-android-node-apkedited, first seen Oct 17, 2026
- steipete/warelayword for word, first seen Oct 17, 2026
Who's talking about molt-bot/clawdbot
- deepwiki.com“Bootstrap Files | molt-bot/clawdbot | DeepWiki”the web · Mar 7, 2026
- medium.com“My First Three Days with Clawdbot (now Moltbot)”the web · Feb 20, 2026
- linkedin.com“Clawdbot Review: Powerful but Security Concerns”the web · Feb 20, 2026
- sidsaladi.substack.com“OpenClaw/Moltbot/ClawdBot 101: The Complete Guide”the web · Feb 11, 2026
- resecurity.com“Clawdbot / Moltbot: The Autonomous AI Butler That Could ...”the web · Feb 6, 2026
The biggest 5 of 18 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 18
Talked about on the web (18 times).
On the web · 18
- Mar 7, 2026Bootstrap Files | molt-bot/clawdbot | DeepWiki — deepwiki.com
- Feb 20, 2026My First Three Days with Clawdbot (now Moltbot) — medium.com
- Feb 20, 2026Clawdbot Review: Powerful but Security Concerns — linkedin.com
- Feb 11, 2026OpenClaw/Moltbot/ClawdBot 101: The Complete Guide — sidsaladi.substack.com
- Feb 6, 2026Clawdbot / Moltbot: The Autonomous AI Butler That Could ... — resecurity.com
13 more on the web
- Feb 5, 2026Is OpenClaw Worth the Hype? I Spent 10 Days Finding Out — aimaker.substack.com
- Feb 4, 2026Can someone explain OpenClaw AI (formerly Clawdbot ... — beginrescueend.com
- Feb 2, 2026Full Setup Guide Clawdbot Moltbot OpenClaw — dev.to
- Feb 1, 2026Tales from the jar side: Clawdbot née Moltbot née OpenClaw, Moltbook and emergent behavior, The Boss still rules, and the usual Social Media silliness — kenkousen.substack.com
- Feb 1, 2026One Week Later with OpenClaw (prev. ClawdBot, prev. MoltBot): A Product Designer's Honest Take — nervegna.substack.com
- Jan 31, 2026In-Depth Moltbot Analysis for AI Developers — blog.promptlayer.com
- Jan 31, 2026I Used Clawdbot (OpenClaw) for 6 Hours so You Don't Have to Buy a Mac Mini - #108 — theagilevc.substack.com
- Jan 29, 2026Moltbot Hands-On Review: A Magical AI Assistant with Serious Red Flags | by Erik.C — medium.com
- Jan 29, 2026Moltbot (formerly Clawdbot): I Put an AI Agent on My Linux Server and Gave It My WhatsApp. Here's What Happened — mvidmar.substack.com
- Jan 29, 2026Falling in and out of love with Moltbot — platformer.news
- Jan 27, 2026Build Your Own AI Assistant with Molt Bot (Clawdbot) and ... — builder.aws.com
- Jan 27, 2026I Tried OpenClaw (Moltbot/ClawdBot) for Data Engineering and Here’s the Honest Truth | by Reliable Data Engineering — medium.com
- Jan 26, 2026MoltBot (ClawdBot) Review & Setup Guide — uxwritinghub.com
Other versions10 projects use a version of this.
Word for word · 3
- steipete/warelay★ 395k100% same
- moltbot/clawdbot★ 395k100% same
- openclaw/openclaw★ 395k100% same
Edited · 5
- steipete/clawdis★ 394k98% same
- moltbot/moltbot★ 394k98% same
- clawdbot/clawdbot★ 394k98% same
- bighamx/openclaw-android-node-apk★ 5798% same
- Djarvur/go-ultimate★ 3195% same
Wrote their own version · 2
- openclaw/openclaw-windows-node★ 2.2ksame name
- shanselman/openclaw-windows-hub★ 2.2ksame name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository113 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- extensions/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- test/AGENTS.mdAGENTS.md
- ui/AGENTS.mdAGENTS.md
- agent-transcriptSkill
- auto-qaSkill
- autoreviewSkill
- channel-message-flowsSkill
- clawdtributorSkill
- claw-scoreSkill
- clawsweeperSkill
- control-ui-e2eSkill
- crabboxSkill
- discord-clawdSkill
- discord-e2eSkill
- discord-user-postSkill
- discrawlSkill
- gitcrawlSkill
- graincrawlSkill
- ios-e2eSkill
- labs-graduationSkill
- notcrawlSkill
- openclaw-changelog-updateSkill
- openclaw-ci-limitsSkill
- openclaw-debuggingSkill
- openclaw-docker-e2e-authoringSkill
- openclaw-ghsa-maintainerSkill
- openclaw-live-updaterSkill
- openclaw-parallels-smokeSkill
- openclaw-performanceSkill
- openclaw-pr-maintainerSkill
- openclaw-qa-testingSkill
- openclaw-refactor-docsSkill
- openclaw-release-validationSkill
- openclaw-repair-sweepSkill
- openclaw-secret-scanning-maintainerSkill
- openclaw-test-heap-leaksSkill
- openclaw-testingSkill
- openclaw-test-performanceSkill
- openclaw-updateSkill
- parallels-discord-roundtripSkill
- plugin-sdk-impactSkill
- proof-videoSkill
- prototype-openclaw-tuiSkill
- release-openclaw-announcementSkill
- release-openclaw-ciSkill
- release-openclaw-macSkill
- release-openclaw-maintainerSkill
- release-openclaw-plugin-testingSkill
- security-triageSkill
- slack-e2eSkill
- slacrawlSkill
- solidSkill
- tag-duplicate-prs-issuesSkill
- technical-documentationSkill
- telegram-e2e-userbotSkill
- test-auditSkill
- update-team-serverSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. 2 are common, 0 are distinctive, and 0 are very specific to this project.
2
Common
Most of the 7 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 16
Read the user's outcome and latest scope, the complete diff against the target merge base, and retained proof.
- Common: line 34
Delete the redundant path: Remove parallel renderers, duplicated parsers, fake lifecycle operations used only to obtain a result, derived …
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Simplify the change
An editing pass by the change's author: run it on your own branch before you open the PR, and again before you push large repairs. It precedes review and never replaces it. Inherit the task's scope and repair authority; a review-only request gets findings instead of edits. The chosen maintainer workflow owns publication, review and merge.
The diff is a proposal. Passing tests show it works, not that its architecture or every added test is needed.
Rules: the root AGENTS.md sections "Choose good compromises", "Design priorities", "One owner, complete cutover", "Runtime and code safeguards" and "Product and validation", plus the nearest scoped AGENTS.md. Steps 2 and 3 apply every rule to every changed file.
1. Re-derive the smallest complete fix
Read the user's outcome and latest scope, the complete diff against the target merge base, and retained proof. Reuse session context already gathered. Then ask:
Starting from the base, what is the smallest complete fix using the owners already present? Would I still introduce this architecture?
Inspect the largest added modules, state, adapters and test scaffolding first. Read their direct callers and relevant history: apparently redundant behavior may protect a shipped configuration or an earlier regression. Scope is the changed system and the paths it replaces.
Trace every changed hunk to the stated outcome. A hunk that serves another goal leaves this change: drop it or move it to its own PR.
Count the non-mechanical changed lines. Above about 800, or about 500 for complex logic, name the smallest coherent stage that can land first and cut the change to that stage.
Done when you can state the defect, the required invariant, and the smallest complete fix in one sentence each, and every remaining hunk serves that fix.
2. Remove unnecessary architecture
Apply each supported simplification in the diff:
- One decision owner. Move repeated caller-side policy into the operation that owns the decision. Migrate affected callers and remove the old implementations, exports and repair branches. Different transports can share a decision while keeping their own delivery contracts.
- Existing state first. Challenge new schemas, managers, caches and combined representations. Reuse an existing owner when its lifetime, authority, atomicity and cleanup fit. Remove a proposed migration only when it is genuinely unnecessary; keep the migration that keeps existing config and state working after update. New state belongs in a field that means it.
- Delete the redundant path. Remove parallel renderers, duplicated parsers, fake lifecycle operations used only to obtain a result, derived state callers can already obtain, and wrappers that merely forward or rename. Prefer one simpler representation over fallback modes around the old one.
- Polish last. In every changed hunk, keep only what a maintainer of the surrounding file would write:
- comments that explain ownership, lifecycle, ordering or constraints;
- checks and
try/catchblocks that match the surrounding module and guard real states; - real types instead of laundering casts (
as any,as unknown as T, widen-then-assert); - variables and helpers that add domain meaning, remove duplication or simplify control flow;
- shims, aliases, retries and fallbacks backed by a named shipped contract and removal plan;
- naming, control flow, imports and formatting that match the surrounding file.
Preserve the requested fix and supported behavior, not the proposal's accidental design. Keep real domain differences and justified public compatibility. When history (git log -p -S <symbol>) leaves a path's purpose unclear, keep it and report it. Report new product decisions, breaking contracts, unrelated cleanup and destructive branch replacement as findings for the owner.
3. Keep tests for failures
For each added or changed test group and its setup helpers, name the distinct observable failure it catches.
Keep regressions for the actual defect and distinct boundaries: ordering, cancellation, restart, rejection, real errors, authority checked when work starts, and affected consumer differences. Remove tests of a change that arrives while one request is in progress, unless a cited incident needs them. Keep static contract guards that independently protect a real boundary. Remove duplicate same-path cases, mock echoes, incidental field-copy or wording assertions, assertions on statically defined values, tests that only prove removed logic is gone, tests of obsolete implementations, and scaffolding or test-only production hooks. Consolidate useful cases in an existing owner suite.
Removing tests never weakens the assertions, coverage of real boundaries or baselines that remain.
Done when every remaining test group has a named failure.
4. Prove the smaller change and hand it on
Batch the edits, then rerun the reproduction and focused checks for the changed contracts and affected consumers. Reuse proof whose inputs are unchanged. A preserved restart, upgrade or transport claim needs applicable proof. The existing workflow selects broader checks.
Done when the complete diff is inspected, every rule has a verdict for each changed file, supported simplifications are applied, superseded paths are unreachable and affected behavior still has proof. No change is a valid result when the existing shape is justified. Aim for net-negative code, not a deletion quota.
Report in the PR body or existing task evidence: the responsibility or machinery that disappeared, the behavior still protected, and production/test deltas against the merge base. Label a reduction against an earlier revision separately from the whole-change delta. Name any necessary remaining growth or unresolved decision.
Then open or update the PR. After later repairs, simplify only the new changes and the owners they touch before pushing them.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

