review-status
Skill0 starsChanged 48 days agoMITView on GitHub
Show where every review in the current cycle stands and suggest what to do next. Read only.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- review-evidenceSkill
- review-setupSkill
- reviewSkill
- review-voiceSkill
- review-evidenceSkill
- review-setupSkill
- reviewSkill
- review-statusSkill
- review-voiceSkill
The file
Files
Follow harness/workflows/status.md exactly.
AGENTS.md and the harness/ directory sit at the root of this repository. If this skill was installed as a Claude Code plugin, they sit at ${CLAUDE_PLUGIN_ROOT} instead; read that AGENTS.md first. Resolve the workspace from the folder you were started in as AGENTS.md says (that folder if it holds config.yml, else workspace/ under it); it is never a folder inside the plugin.
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.

