weave-review
Skill5 starsChanged 2 months agoMITView on GitHub
Review the current diff for avoidable complexity and scope drift: duplicated mechanisms, speculative abstractions, reinvented stdlib, dependencies the platform already covers, and changes outside the request contract. One line per finding. Use when the user says "weave review", "/weave-review", "simplification review", "what can we remove from this change", or "is this over-engineered". Reports only, edits nothing.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- tony/skillstheir own version, first seen Oct 31, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- tony/skills★ 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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/weave.mdcCursor rule
- weave-auditSkill
- weave-debtSkill
- weave-gainSkill
- weave-helpSkill
- weave-planSkill
- weave-promptSkill
- weaveSkill
The file
Files
Weave Review
Review only the current diff (git diff plus staged changes) and the direct
callers it touches. Do not edit files.
Format
<file>:L<line>: <tag> <what>. <replacement>.
Tags:
delete:dead code, unused option, speculative feature. Replacement: nothing.reuse:re-implements something already in this repo. Name the existing helper and its path.stdlib:hand-rolled thing the standard library ships. Name the function.native:dependency or code doing what the platform already does. Name the feature.yagni:abstraction with one implementation, config nobody sets, layer with one caller.shrink:same logic, fewer lines. Show the shorter form.shared:fix applied at one call site while the cause lives in a shared function. Name the function.scope:change not required by the request contract in.weave/state.md(or the user's request). Revert it.
Examples
core/date.js:L12-30: native: moment imported for one format call. Intl.DateTimeFormat, 0 deps.api/users.js:L44: reuse: new pagination helper. lib/paginate.js already does this.checkout.js:L88: shared: null guard added here only. Guard once in getCart(), all 4 callers covered.README.md:L10-40: scope: unrelated rewrite of the install section. Not requested; revert.
Scoring
Rank by impact, biggest first. End with net: -<N> lines possible.
Nothing to cut: Lean already. Ship.
Boundaries
Complexity and scope only. Correctness bugs and security issues go to a normal review; mention them in one line at the end if you saw one, without analysis. A small test or self-check is the minimum, never flag it for deletion. Lists findings, applies nothing.
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.