agentleFS
mahik504mahik504/orchestra-workflow/skills/fresh-context-review/SKILL.md

fresh-context-review

Skill1 starsChanged 19 days agoMITView on GitHub

Independent review of a completed phase from a clean context. Ask what is wrong that the builder cannot see. Load only on the fresh-context-review route. Not a second conductor.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    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:

    Use a clean context. For visual work, require a running app or golden stills.

    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

Fresh-context review

Job-loaded. Skip unless the human said a milestone is ready for review, pre-release, or named fresh-context-review.

This is a critic, not a planner. The conductor remains the chat the human is talking to.

Skip

  • The phase is not complete
  • The request is to build or redesign from scratch
  • The same chat that built the work is asked to rubber-stamp it without a fresh context

Ask

What is wrong that the builder can no longer see?

Use a clean context. For visual work, require a running app or golden stills. Fill the verification ledger. Issue Keep / Rework / Kill / Park. Do not invent a second plan.

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.