grug-review
Review changed code for proven bugs and harmful complection. Use for a diff, pull request, or changed files. Every finding needs a concrete failure or a concrete simpler version.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- grug-review
- description
- Review changed code for proven bugs and harmful complection. Use for a diff, pull request, or changed files. Every finding needs a concrete failure or a concrete simpler version.
03 SKILL.md 正文
Grug review
Grug does not invent findings. If grug cannot prove it, grug drops it.
Read the change
Read the user request, plan, or specification when available, and state the change's intent in one sentence. If you cannot, ask. Check its required behavior, constraints, preserved behavior, and non-goals. Review changed lines and directly affected final code, including old code the change should have deleted.
Ask why odd code exists. Skip generated files, lockfiles, vendored code, and formatter or linter issues.
Prove correctness
Post only when you can name the input or state, reachable path, and observable wrong result. Unauthorized access or data exposure is a wrong result.
Before posting, check whether the same function or caller already handles the case and whether an apparently unused item is used by the type system.
Prove complection
Post only when you can write simpler final code and say what it gives up.
Look for dual authority, policy spread across callers, effects mixed into decisions, or lifecycle state that changes no allowed events.
Look for indirection that hides no work: a name for a value used once, a factory the type already describes, a layer that only renames what it wraps, or a file with one caller. Every read pays for the jump between files.
Three real callers or a trust boundary may justify an abstraction. They do not prove it. A deep module hides hard work behind a small interface. Keep one authority for each decision.
Treat every new comment or explanatory docstring as a complection finding. Replace it with clear names or structure. Keep only legal headers, public API contracts, issue or RFC links, and behavior forced by a dependency we cannot change. A comment explaining our own surprising code means the code should change. A comment saying "do not remove" or "important" is a claim: check it with the grug-explore or why skill, and when it holds, propose a type, test, or lint that enforces it instead.
A new lint or type suppression that silences a correctness rule is a correctness finding.
Report
Post at most five findings, most important first.
- A correctness finding names the file, line, failure, and fix.
- A complection finding names the file, line, simpler version, and tradeoff.
Output findings only. If none pass, write exactly: No issues found.
Finish after the findings. When the user wants fixes, suggest grug-implement. Suggest grug-design only when the review exposes an unresolved design choice.
04 同仓库更多 Skills
code-review
暂无简介
wrangler
Run or troubleshoot Wrangler CLI commands in projects that have a wrangler.jsonc, wrangler.json, or wrangler.toml file, including local development, Previews, deployment, and resource management. For new projects and projects without a Wrangler configuration file, use the cf CLI instead.
workers-best-practices
Cloudflare Workers best practices for production applications. Use when writing, reviewing, or configuring Workers.
why
Use when the user asks to investigate why code is built the way it is: 'why does X work this way', 'why we picked Y', design rationale, regressions, or postmortems. Not for explaining a single error or a quick question. Queries each available evidence source (git and PRs, issues, docs, team chat) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
vendor-skill
Adapt an external skill into this marketplace, or review upstream changes to one already adapted. Use when asked to vendor, import, adapt, mirror, or update a skill from skills.sh, `npx skills add`, or any external GitHub skills repo, especially to work around Claude Code Web only allowing one marketplace per GitHub repo name.