agentleFS
Sign inStart free
bighamxbighamx/openclaw-android-node-apk/.agents/skills/autoreview/SKILL.md

autoreview

Skill59 starsChanged 16 days agoMITView on GitHub

Structured code review through the shared OpenClaw agent-skills installation.

We split this skill into the rules it gives an agent

5 rules. 0 are common, 0 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 24 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the canonical autoreview skill.

    line 8
  2. Very specific:

    Read the complete installed ~/.agents/skills/autoreview/SKILL.md and the references it requires before reviewing.

    line 9
  3. Very specific:

    If the skill is missing, reuse or clone https://github.com/openclaw/agent-skills and run python3 scripts/install-skills autoreview from …

    line 13
  4. Very specific:

    Run the shared scripts/autoreview helper with Python from the repository being reviewed, preserving its working directory.

    line 17
  5. Very specific:

    Keep shared fixes and instructions upstream in openclaw/agent-skills.

    line 21

“Common” is measured: kept by at least 6 in 10 of the 24 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Auto Review

Use the canonical autoreview skill. Read the complete installed ~/.agents/skills/autoreview/SKILL.md and the references it requires before reviewing. If installed at another operator-selected location, use that installation. This repository entrypoint contains no review implementation.

If the skill is missing, reuse or clone https://github.com/openclaw/agent-skills and run python3 scripts/install-skills autoreview from that checkout. On Windows, use python; --mode copy is available when symlinks are unavailable.

Run the shared scripts/autoreview helper with Python from the repository being reviewed, preserving its working directory. Follow this repository's review requirements in addition to the canonical skill.

Keep shared fixes and instructions upstream in openclaw/agent-skills. Update the shared checkout once for all symlinked consumers; reinstall copy-mode skills after updating their source. Do not add repository-local helpers or test copies.

Download now (ZIP)

Trending

Surging: 3 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 3 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 3 in all, so this is a hint, not a trend.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free