autoreview
Skill176 starsChanged 7 months agoMITView on GitHub
Perform a structured final code review of a local diff, commit, branch, or pull request. Use only when the user explicitly asks for autoreview, a second review, or a final review before commit, merge, or release, or when repository instructions require one. Do not trigger automatically for ordinary non-trivial edits.
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 38 edited versions we read keep these.
5
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
- Distinctive: line 15
Do not push, rewrite history, or manufacture a diff merely to make review possible.
- Distinctive: line 28
Prefer concrete defects with a reproducible path.
- Distinctive: line 32
Treat every finding as advisory until confirmed against the real code path.
- Distinctive: line 33
Read adjacent code, types, tests, and authoritative dependency documentation when needed.
- Distinctive: line 38
Stop when no confirmed actionable findings remain.
“Common” is measured: kept by at least 6 in 10 of the 38 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
Auto Review
Review the completed change as a closeout check. Use the review capability available in the current environment; do not make completion depend on a particular helper, model, service, or installation.
Select the real change
- For dirty work, review the staged, unstaged, and relevant untracked diff.
- For a commit, review that commit and its immediate context.
- For branch or pull-request work, compare against the actual base branch.
- Do not push, rewrite history, or manufacture a diff merely to make review possible.
Review priorities
Inspect the changed code and adjacent ownership boundaries for:
- correctness and violated invariants;
- security, privacy, authorization, and unsafe data handling;
- error handling, retries, concurrency, cleanup, and partial failure;
- compatibility with persisted state and public contracts;
- missing or misleading tests;
- unnecessary complexity introduced by the change.
Prefer concrete defects with a reproducible path. Reject speculative edge cases, style-only churn, unrelated rewrites, and fixes that cost more complexity than the risk warrants.
Verify findings
- Treat every finding as advisory until confirmed against the real code path.
- Read adjacent code, types, tests, and authoritative dependency documentation when needed.
- Fix accepted findings at the narrowest correct ownership boundary.
- Rerun affected tests after review-driven edits.
- Re-review only the changed result when a fix could have introduced another defect.
Stop when no confirmed actionable findings remain. Do not seek extra reviewers or repeat a clean review solely for more reassuring wording.
Report
Include:
- the target reviewed;
- findings accepted and rejected, with brief reasons;
- fixes made and tests run;
- remaining risks or verification gaps.
Other versions38 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 38
- moltbot/moltbot★ 393ksame name
- clawdbot/clawdbot★ 393ksame name
- steipete/warelay★ 392ksame name
- moltbot/clawdbot★ 392ksame name
- steipete/clawdis★ 392ksame name
- molt-bot/clawdbot★ 391ksame name
- openclaw/openclaw★ 391ksame name
- openclaw/clawhub★ 9.5ksame name
- moltbot/molthub★ 9.5ksame name
- clawdbot/clawdhub★ 9.5ksame name
28 more not listed
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.
Used alongsideProjects with it also use auto-qa, discord-e2e and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
supermansuper563-opsSkillauto-qa
Continuously audit, live-test, and stress-test the current OpenClaw codebase across at least ten independently scoped subsystem lanes; default to 100 independently verified, landed root-cause fixes, maintain an evidence-backed report, and announce each merged pull request immediately. Use for OpenClaw-wide autonomous QA, live-provider campaigns, gateway, CLI, web, plugin, native-app, scenario, packaging, and extended soak testing.
Also in 11 projects that use this
molt-botSkilldiscord-e2e
Test Discord with Convex-leased QA bots: check credentials without a Gateway, exercise owned messages, or prove OpenClaw replies, files, threads, reactions, streaming, and typing. Distinguish API and Gateway evidence from manual user interactions.
Also in 10 projects that use this
molt-botSkillopenclaw-repair-sweep
Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.
Also in 10 projects that use this
openclawSkillopenclaw-brand
Apply OpenClaw visual identity to logos, typography, imagery, voice, documents, presentations, social graphics, and launch materials. Use when the task changes brand identity rather than ordinary product UI or public-page composition.
Also in 5 projects that use this
openclawSkillopenclaw-carapace
Build or modify OpenClaw application UI using canonical semantic tokens, themes, shared CSS foundations, consumer adapters, and established local primitives. Use for product interfaces, component styling, theme work, or design-token integration.
Also in 5 projects that use this
clawsoulsSkillchannel-message-flows
Use when running QA Lab channel message flow evidence.
Also in 12 projects that use this
- +2 more from molt-bot
- +4 more from openclaw
In this repository101 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accelevents-apiSkill
- accelevents-speaker-syncSkill
- agents-sdkSkill
- ai-devblogSkill
- ai-engineeringSkill
- ai-readmeSkill
- align-meSkill
- annotated-video-productionSkill
- antislop-codebaseSkill
- app-ux-paradigmsSkill
- babysit-runsSkill
- blog-system-designSkill
- cassandra-creatorSkill
- ceo-creatorSkill
- claude-session-introspectSkill
- cli-uxSkill
- cloudflare-do-turn-based-multiplayerSkill
- cloudflare-email-serviceSkill
- cloudflare-one-migrationsSkill
- cloudflare-oneSkill
- cloudflare-production-builderSkill
- cloudflareSkill
- conference-developer-endpointsSkill
- conference-transcribeSkill
- coordinateSkill
- data-chatbotsSkill
- data-visualization-qualitySkill
- deep-trajectory-analysisSkill
- design-apps-with-imagegenSkill
- design-preferencesSkill
- diy-netlifySkill
- download-videoSkill
- download-x-videoSkill
- durable-objectsSkill
- europe-developer-apiSkill
- face-matchingSkill
- forgeSkill
- future-onlySkill
- generalizeSkill
- gsuite-setupSkill
- keep-it-simpleSkill
- latent-space-thumbnail-directorSkill
- live-ai-pipelinesSkill
- location-inputSkill
- long-running-operation-uxSkill
- media-heavy-workflowsSkill
- media-to-wiki-pipelineSkill
- media-transformSkill
- mobile-nativeSkill
- mobile-webapp-uxSkill
- multimodal-extractionSkill
- new-mac-setupSkill
- next-stepsSkill
- observability-hardeningSkill
- person-profile-writingSkill
- podcast-publishing-assistantSkill
- productionize-app-with-servicesSkill
- programmatic-agentsSkill
- provision-model-keysSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

