agentleFS
Sign inStart free
tokarixtokarix/memory-server/skills/review-request/SKILL.md

review-request

Skill1 starsChanged 8 months agoApache-2.0View on GitHub

Quick command to request a review for recent work by storing a review-needed memory

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. rlajous/claude-code-commands★ 30same name
    2. sentimony/skills★ 7same name
    3. EvildoerXiaoyy/reasonix-skills★ 4same name
    4. digitalgym/aipathway-standards★ 0same 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 repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    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
  1. Distinctive:

    Keep summary to one line. Include enough content for a reviewer to act.

    line 19
  2. Distinctive:

    Do not do anything else.

    line 22

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

Your task

Store a memory tagged review-needed so another agent can review it.

  1. Gather git context by running these commands via Bash in the project directory:
    • git branch --show-current
    • git log --oneline -10
    • git diff HEAD --stat
  2. Determine review type from user input or ask briefly: plan or code?
  3. Call memory_store:
    • Plan: category plan, tags ["review-needed", "author:claude"]
    • Code: category context, tags ["review-needed", "code-review", "author:claude"]
  4. Auto-fill git range and file list from the git context gathered in step 1.
  5. Keep summary to one line. Include enough content for a reviewer to act.
  6. Print the memory ID.

Do not do anything else.

Download now (ZIP)

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