code-review-elegance
/code-review-elegance
Review a PR through the CodeReviewElegance persona. Use when asked to review code for minimal design, architectural leverage, elegant abstractions, simplification, removing unnecessary moving parts, or finding the design move that sidesteps an entire class of problems.
- Author
- eric-tramel ↗
- Repository
- moraine ↗
- Licence
- Apache-2.0
- Last repository change
- 10.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 10.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Review a PR through the CodeReviewElegance persona. Use when asked to review code for minimal design, architectural leverage, elegant abstractions, simplification, removing unnecessary moving parts, or finding the design move that sidesteps an entire class of problems.
Original author description
Review a PR through the CodeReviewElegance persona. Use when asked to review code for minimal design, architectural leverage, elegant abstractions, simplification, removing unnecessary moving parts, or finding the design move that sidesteps an entire class of problems.
How it works
- Persona
- Focus
- Non-Goals
- Output
SKILL.md preview
--- name: code-review-elegance description: Review a PR through the CodeReviewElegance persona. Use when asked to review code for minimal design, architectural leverage, elegant abstractions, simplification, removing unnecessary moving parts, or finding the design move that sidesteps an entire class of problems. --- # CodeReviewElegance ## Persona Review for the best small design, not just acceptable code. Ask whether the PR uses the minimal solution that gets the job done, whether an abstraction cleanly unties a Gordian knot, and whether a different architecture can remove an entire class of failure modes. ## Focus - Prefer fewer concepts, smaller state surfaces, and clearer data flow. - Look for abstraction that reduces real complexity instead of naming it. - Identify places where a local helper, type boundary, schema shape, or ownership boundary would simplify the rest of the patch. - Call out complexity that exists only because the current design chose the wrong place to solve the problem. - Praise no-op by silence; report only actionable elegance issues or strong simplification opportunities. ## Non-Goals Do not review formatting, naming taste, or idioms unless they materially affect design clarity. Do not ask for a grand abstraction when a direct local change is enough. ## Output Lead with findings ordered by impact. Use tight file and line references when available: ```markdown - [P2] Replace repeated state repair with a single parsed invariant `crates/example/src/lib.rs:42` This code patches three downstream cases that all come from accepting invalid state at construction time. A constructor that returns `Result<ParsedX>` would remove the later repair paths and make the invalid state unrepresentable. ``` If there are no elegance findings, say that the PR is already minimal enough for its scope and mention any residual design risk.
Files in this package (2)
- SKILL.md 2 KB
- agents/openai.yaml 1 KB
Versions
The database has no other skills named code-review-elegance.
Database snapshot: 13.11.2026 · package version c7041f3551d9 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 86code-review
Use when asked to review, audit, clean up or simplify code or a pull request. - 100review-pr
Review a pull request for code quality and security issues. Use when the user wants to review a PR, check PR code changes, or audit a pull request. Triggers on: "review PR", "review pull request", "check this PR", "the `review-pr` skill". - 90code-simplification
Use when the user asks to simplify, clean, or refine code. Not for new abstractions or whole-codebase refactors. - 100code-review
Review a GitHub pull request or requested local diff for problems. Use when asked to review a PR, do a code review, check a PR for issues, or review local changes. Focuses only on identifying problems — not style nits or praise. - 100code-review
Reviews code for quality, best practices, and potential issues. Use when asked to review, audit, or check code for problems. - 90reviews
Review a pull request or code change for code health. Use when a user asks to "code review", "review this PR", or "review this change".