agentleFS
davidsolheimdavidsolheim/skills/project-review/SKILL.md

project-review

Skill1 starsChanged 38 days agoNo licenceView on GitHub

Fully agentic project review: walk the current repo and (when available) live app, invent findings without a human laundry list, and file atomic solve-ready `.wcp/issues/` files so /solve can implement them end-to-end. Covers completeness, functional bugs, UI consistency, taste/feel, edge cases, responsiveness, accessibility, content, and cross-feature consistency. Supports fast (high-signal P0/P1 single-agent) and deep (exhaustive multi-agent orchestrator with full inventory coverage, local issue-candidates package, then one file and Notion publish). Default writes `.wcp/issues/` and Notion; --draft keeps markdown only. Use when the user runs /project-review, says review this project, quality pass, UI audit, bug hunt, find issues for solve, audit the app, or wants the agent to discover and queue work for /solve.

15 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 13

    Distinctive

    This author's own choices. Worth a look.

  • 13

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.