New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Elegance-Focused Code Review

by eric-tramel in eric-tramel/moraine

Looks at a pull request for the smallest good design, hunting for simplifications and architectural moves that remove whole classes of problems.

Apache-2.0Auto-check passedDevelopment

Install Elegance-Focused Code Review

skills CLI
$ npx skills add eric-tramel/moraine --skill code-review-elegance -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install eric-tramel/moraine code-review-elegance --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/eric-tramel/moraine.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/moraine-dev/skills/code-review-elegance .claude/skills/code-review-elegance && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
code-review-elegance
GitHub stars
117
Token cost
~473 tokens
SKILL.md length
186 words
Files
2
Skills in repo
19
Repo updated
First seen
Licence
Apache-2.0

At a glance

Looks at a pull request for the smallest good design, hunting for simplifications and architectural moves that remove whole classes of problems.

  • Reviewing a PR for minimal design and unnecessary moving parts
  • SKILL.md covers Persona, Focus, Non-Goals and Output
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Looking for a design change that sidesteps a whole class of bugs

What it does

Review runs through a persona called CodeReviewElegance, which asks whether the PR is the minimal solution, whether an abstraction really reduces complexity, and whether a different architecture could remove a whole class of failure modes. It favors fewer concepts, smaller state surfaces and clearer data flow, and points to spots where a helper, type boundary, schema shape or ownership boundary would simplify the rest of the patch.

Formatting, naming taste and idioms are out of scope unless they hurt design clarity, and the reviewer should not demand a grand abstraction when a direct local change is enough. Output leads with findings ordered by impact, each with a priority label such as P2, a title and a tight file and line reference. When nothing qualifies, the review says the PR is already minimal for its scope and notes any residual design risk. An `agents/openai.yaml` file is included.

When your agent uses it

  • Reviewing a PR for minimal design and unnecessary moving parts
  • Looking for a design change that sidesteps a whole class of bugs
  • Checking whether a new abstraction earns its keep

Example prompts

  • “Go over this PR with an eye for elegance and tell me what could be simpler.”
  • “Is there a smaller design for the retry logic in this patch?”
  • “Find repeated state repair in the session module that a single invariant would remove.”

What it can do on your machine

Read from SKILL.md and the folder at commit 2fb4aec. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Elegance-Focused Code Review loads about 473 tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 186 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~73
When it runs · the whole SKILL.md, loaded when a task matches
~473

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from eric-tramel/moraine at commit 2fb4aec, republished under its Apache-2.0 licence (© eric-tramel). 186 words, ~473 tokens.

Download SKILL.mdSave it as .claude/skills/code-review-elegance/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
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.

© eric-tramel, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in plugins/moraine-dev/skills/code-review-elegance of eric-tramel/moraine.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 2fb4aec

Compare with similar skills

Elegance-Focused Code Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Elegance-Focused Code Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Elegance-Focused Code Review this skilleric-tramel/moraine117—~473Automated safety check: PassApache-2.0
Chisle ReviewJayPokale/Chisle628—~362Automated safety check: PassMIT
Pragmatic Reviewheyitsnoah/claudesidian2.6k—~2.6kAutomated safety check: PassMIT
SimplifySeifBenayed/cloclo114—~430Automated safety check: NotesMIT
Codebase DesignPrismer-AI/PrismerCloud1.6k—~1.7kAutomated safety check: PassMIT
Review And Simplify ChangesDimillian/Skills4k—~2kAutomated safety check: PassMIT

Similar skills

  • Chisle Review

    JayPokale/Chisle

    Review a diff or file through the Chisle lens: flag over-engineering, speculative abstractions, reinvented stdlib, and verbose code that a lazier approach would shrink.

    628 GitHub stars~362 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Pragmatic Review

    heyitsnoah/claudesidian

    Interactive pragmatic code review focusing on YAGNI and KISS principles.

    2.6k GitHub stars~2.6k tokensUpdated 5 mo ago
    DevelopmentAuto-check passed

  • Simplify

    SeifBenayed/cloclo

    Review code for unnecessary complexity and simplify it. An agent skill from SeifBenayed/cloclo.

    114 GitHub stars~430 tokensUpdated 6 mo ago
    DevelopmentAuto-check: notes

  • Codebase Design

    Prismer-AI/PrismerCloud

    Designs deep modules with small interfaces, reviews scoped code changes and simplifies implementations while checking that behavior stays the same.

    1.6k GitHub stars~1.7k tokensUpdated 7 days ago
    DevelopmentAuto-check passed

  • Review And Simplify Changes

    Dimillian/Skills

    Review a git diff or explicit file scope for reuse, code quality, efficiency, clarity, and standards issues, then optionally apply safe Codex-driven fixes.

    4k GitHub stars~2k tokensUpdated 6 mo ago
    DevelopmentAuto-check passed

  • Honey Review

    Green-PT/honey-for-devs

    Review a diff for what Honey would cut — over-engineering (speculative generality, hand-rolled stdlib, single-caller abstractions) and over-verbosity (dead code, narration, redundant comments).

    310 GitHub stars~478 tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

More from eric-tramel/moraine

All 19 skills in this repo

  • Moraine Release Publisher

    eric-tramel/moraine

    Cuts and publishes a Moraine release end to end: version bump PR, tag, GitHub release notes, workflow check and PyPI package verification.

    117 GitHub stars~2.5k tokensUpdated 2 days ago
    Auto-check passed

  • Moraine Release Notes

    eric-tramel/moraine

    Rewrites a moraine GitHub release body into a usage-focused format with install block, what's new, platform table, upgrade notes and one deduplicated changelog.

    117 GitHub stars~2.7k tokensUpdated 2 days ago
    Auto-check passed

  • Multi-Persona Code Review

    eric-tramel/moraine

    Coordinates a delegated review of a Moraine PR or local change by seven focused reviewer subagents, merges their findings and follows up on the fixes.

    117 GitHub stars~1.3k tokensUpdated 2 days ago
    Auto-check passed

  • Idiomatic Code Review

    eric-tramel/moraine

    Reviews a pull request for idiomatic implementation: use of the language, standard library, ecosystem conventions and the repository's own patterns.

    117 GitHub stars~469 tokensUpdated 2 days ago
    Auto-check passed

  • Code Review Security Review

    eric-tramel/moraine

    Review a PR through the CodeReviewSecurityReview persona. An agent skill from eric-tramel/moraine.

    117 GitHub stars~497 tokensUpdated 2 days ago
    Auto-check passed

  • Crystallize

    eric-tramel/moraine

    Turn a rough feature, bug, refactor, architecture, documentation, or operations idea into a ready-to-implement local plan file.

    117 GitHub stars~1.6k tokensUpdated 2 days ago
    Auto-check passed

Categories

Questions about Elegance-Focused Code Review

What does Elegance-Focused Code Review do?

Looks at a pull request for the smallest good design, hunting for simplifications and architectural moves that remove whole classes of problems. Review runs through a persona called CodeReviewElegance, which asks whether the PR is the minimal solution, whether an abstraction really reduces complexity, and whether a different architecture could remove a whole class of failure modes. It favors fewer concepts, smaller state surfaces and clearer data flow, and points to spots where a helper, type boundary, schema shape or ownership boundary would simplify the rest of the patch.

When should I use Elegance-Focused Code Review?

Elegance-Focused Code Review fits situations like: reviewing a PR for minimal design and unnecessary moving parts; looking for a design change that sidesteps a whole class of bugs; checking whether a new abstraction earns its keep.

How do I install Elegance-Focused Code Review in Claude Code?

Run `npx skills add eric-tramel/moraine --skill code-review-elegance -a claude-code`. Or copy the skill folder (plugins/moraine-dev/skills/code-review-elegance in eric-tramel/moraine) into .claude/skills/code-review-elegance in your project. Claude Code loads it when a task matches its description.

How do I install Elegance-Focused Code Review in Codex?

Run `npx skills add eric-tramel/moraine --skill code-review-elegance -a codex`. Or copy the skill folder (plugins/moraine-dev/skills/code-review-elegance in eric-tramel/moraine) into .agents/skills/code-review-elegance in your project. Codex loads it when a task matches its description.

Can I use Elegance-Focused Code Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add eric-tramel/moraine --skill code-review-elegance -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/code-review-elegance, .gemini/skills/code-review-elegance, .github/skills/code-review-elegance and .opencode/skills/code-review-elegance in your project.

What does Elegance-Focused Code Review need to run?

SKILL.md names no scripts, command-line tools or credentials: Elegance-Focused Code Review is instructions for the agent only.

Does Elegance-Focused Code Review access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Elegance-Focused Code Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Elegance-Focused Code Review use?

Elegance-Focused Code Review is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Elegance-Focused Code Review use?

About 473 tokens (SKILL.md is roughly 1.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Elegance-Focused Code Review?

Skills that share tags, products or a category with Elegance-Focused Code Review: Chisle Review (JayPokale/Chisle, 628 stars), Pragmatic Review (heyitsnoah/claudesidian, 2.6k stars), Simplify (SeifBenayed/cloclo, 114 stars) and Codebase Design (Prismer-AI/PrismerCloud, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Elegance-Focused Code Review?

eric-tramel (a GitHub user) maintains it in eric-tramel/moraine, which has 117 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 5, 2026.

Source: eric-tramel/moraine on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.