review
Skill2.4k starsChanged 2 days agoApache-2.0View on GitHub
Exhaustively review every line in a diff from a fixed point along two independent axes—repository standards and the originating spec—with evidenced findings, explicit coverage, and bounded fix verification.
192 other projects use a version of this.
Trending
More talk lately.about the whole repository
Most recently taken up by
- dzhng/skillstheir own version, first seen Nov 15, 2026
- macro-inc/macrotheir own version, first seen Nov 15, 2026
- igoroliveirg/claude-copytheir own version, first seen Nov 15, 2026
- yagizdo/quivertheir own version, first seen Nov 15, 2026
- markmhendrickson/neotomatheir own version, first seen Nov 15, 2026
- felipeam86/pipe-skillstheir own version, first seen Nov 15, 2026
Who's talking about muxy-app/muxy
- A Hacker News story“Muxy is a lightweight terminal for Mac with a mobile app for remote control”Hacker News · May 20, 2026 · 3 points
- A Hacker News story“Muxy – A macOS terminal built with SwiftUI and libghostty”Hacker News · Apr 22, 2026 · 3 points
- @tom-doerr.bsky.social“https://github.com/muxy-app/muxy”Bluesky · Apr 20, 2026 · 1 likes
- A Hacker News story“Ghostty, but with Vertical tabs, lightweight and native”Hacker News · Apr 3, 2026 · 1 points
- sudosubin/agents.nix“agent-skills.github.muxy-app.muxy: 2.4.0 → 2.5.0”GitHub · Nov 13, 2026
The biggest 5 of 20 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 20
Talked about on GitHub, Hacker News and Bluesky (20 times).
On GitHub · 16
- Nov 13, 2026agent-skills.github.muxy-app.muxy: 2.4.0 → 2.5.0 — sudosubin/agents.nix0 reactions
- Nov 7, 2026agent-skills.github.muxy-app.muxy: 2.3.0 → 2.4.0 — sudosubin/agents.nix0 reactions
- Oct 31, 2026agent-skills.github.muxy-app.muxy: 2.2.0 → 2.3.0 — sudosubin/agents.nix0 reactions
- Oct 29, 2026Add Muxy — AppImage/appimage.github.io0 reactions · 1 comment
- Oct 17, 2026agent-skills.github.muxy-app.muxy: 2.1.0 → 2.2.0 — sudosubin/agents.nix0 reactions
11 more on GitHub
- Oct 14, 2026wr-agent: page scrollback to reattaching clients instead of repainting it whole — joelmoss/workroom0 reactions · 3 comments
- Oct 14, 2026agent-skills.github.muxy-app.muxy: 0-unstable-2026-08-28 → 2.1.0 — sudosubin/agents.nix0 reactions
- Oct 3, 2026agent-skills.github.muxy-app.muxy: 1.6.1 → 0-unstable-2026-08-28 — sudosubin/agents.nix0 reactions
- Sep 30, 2026agent-skills.github.muxy-app.muxy: init at 1.6.1 — sudosubin/agents.nix0 reactions
- Jul 29, 2026Feature Request: Native Terminal AI Agent Support (ACP Integration & Third-Party CLI Orchestration) — github/app0 reactions · 3 comments
- Jul 10, 2026github 0.1.1 — muxy-app/extensions0 reactions · 6 comments
- May 26, 2026Fix Pi notification pill showing wrong provider name — maxschulmeister/muxy0 reactions
- May 21, 2026https://github.com/muxy-app/muxy — weihubeats/Asuna0 reactions · 1 comment
- May 14, 2026Custom project picker for adding/opening projects — sadiksaifi/muxy0 reactions
- Apr 11, 2026佈局持久化(Daemon Layout API + Restore Reconciliation) — zac15987/zplex0 reactions · 3 comments
- Apr 6, 2026Add Muxy to Terminal section — iCHAIT/awesome-macOS0 reactions · 1 comment
On Hacker News · 3
- May 20, 2026Muxy is a lightweight terminal for Mac with a mobile app for remote control3 points
- Apr 22, 2026Muxy – A macOS terminal built with SwiftUI and libghostty3 points · 1 comment
- Apr 3, 2026Ghostty, but with Vertical tabs, lightweight and native1 point · 1 comment
On Bluesky · 1
- Apr 20, 2026https://github.com/muxy-app/muxy — @tom-doerr.bsky.social1 likes and repost
Used with
Projects with it also use close-spec, daily-arxiv and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
dzhngSkillclose-spec
When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).
Also in 5 projects that use this
LambenthanSkilldaily-arxiv
每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新
Also in 5 projects that use this
dzhngSkilldesign-with-images
Explore UI and visual design with image generation, then iterate the real implementation against the user-selected concept. Use when brainstorming visual directions, offering mockup variants, or implementing an approved generated design; do not stop at the mockups or the first code approximation.
Also in 5 projects that use this
LambenthanSkillexp-eval
实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges
Also in 5 projects that use this
- +5 more from Lambenthan
- +3 more from dzhng
Other versions192 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 192
- garrytan/gstack★ 142ksame name
- ansible/ansible★ 71ksame name
- docling-project/docling★ 71ksame name
- traefik/traefik★ 66ksame name
- ClickHouse/ClickHouse★ 51ksame name
- temporalio/temporal★ 24ksame name
- ccch1mneyyy/dsh-Go★ 24ksame name
- tisfeng/Easydict★ 15ksame name
- juicedata/juicefs★ 15ksame name
- elie222/inbox-zero★ 13ksame name
182 more not listed
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 repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- code-and-architecture-improvementSkill
- e2e-testSkill
- implementSkill
- issues-triageSkill
- release-highlightsSkill
- report-taskSkill
- visual-testingSkill
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 156 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
- Distinctive: line 36
Do not report advisories unless user asks for them.
“Common” is measured: kept by at least 6 in 10 of the 156 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.
Files
Code Review
Review one immutable diff against:
- Standards — repository instructions and documented coding standards.
- Spec — the originating issue, PRD, or acceptance criteria.
Prepare
- Pin the requested input. Resolve committed endpoints to SHAs; if staged or working-tree changes are included, capture one patch snapshot. Give every reviewer that same immutable diff. Stop on invalid or empty input.
- Find the spec from commit references, a user-provided path, or matching files under
docs/,specs/, or.scratch/. If none exists, mark the Spec axis unavailable. - Find applicable repository instructions and standards such as
CLAUDE.md,AGENTS.md,CONTRIBUTING.md, andCODING_STANDARDS.md. - Inventory the complete diff: files, hunks, additions, deletions, renames, and binary files. Never rely on one possibly truncated diff output.
- Find the specs of the changes. what feature it delivers, or what issue it solves. Use PR summary or linked issues or user provided context. If not sure, Ask user before proceeding. Sometimes its possible to understand the spec from the code changes as well.
Review
- Inspect every added, changed, and deleted line in every file, including tests, docs, configuration, migrations, lock/generated files, renames, and binaries. Read surrounding code and call sites where needed.
- Maintain a file-and-hunk checklist against the inventory. Inspect file by file or in smaller batches so output cannot hide lines through truncation. Do not finish with an unchecked line or hunk.
- Report only issues introduced by the diff. A blocker requires evidence of an acceptance, correctness, security, data-loss, compatibility, or explicit required-standard violation. Style preferences, generic code smells, speculative hardening, optional refactors, and unrelated debt are non-blocking advisories.
- For findings, provide severity,
file:line, the violated spec/rule or invariant, a concrete failure scenario, evidence, and the smallest valid fix. Do not report vague possibilities. - Return
PASSorCHANGES NEEDED, then blockers, advisories, and coverage totals.PASSmeans zero blockers, not zero possible improvements.
Compare both coverage reports with the inventory. If anything is missing, review only the missing batches before reporting; an incomplete review cannot pass.
Report
- Present
## Standardsand## Specseparately. End with blocker and advisory counts per axis. Do not let advisories change a pass into failure. - Also when presenting, each findings should have severity, High, Medium, Low and clarify which ones must be fixed before proceeding.
- Recommend
FIX BEFORE PROCEEDING,CONSIDER FIXING, orPROCEEDfrom the evidenced severity, confidence, and risk, and name the findings that drive the recommendation. The review is read-only: the user decides whether to fix. Ask for that decision and do not edit or dispatch a fixer without explicit approval. - Do not report advisories unless user asks for them.
- Provide a TL;DR section in the end in short in a table
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.

