agentleFS
NemesLaszloNemesLaszlo/Agent-Collection/.claude/skills/review/SKILL.md

review

Skill1 starsChanged 15 days agoMITView on GitHub

Code review using Clean Code Architect principles. Reviews staged changes, recent commits, or specific files for quality, security, and maintainability. Use when the user says review, review my code, check this, code review, or before committing significant changes.

193 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use close-spec, design-with-images 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.
  • dzhngSkill

    close-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

  • dzhngSkill

    design-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

  • LambenthanSkill

    daily-arxiv

    每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新

    Also in 5 projects that use this

  • LambenthanSkill

    exp-eval

    实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges

    Also in 5 projects that use this

  • +3 more from dzhng
  • +5 more from Lambenthan

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 157 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If no target is specified, review all staged and unstaged changes.

    line 25

“Common” is measured: kept by at least 6 in 10 of the 157 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Context

  • Current branch: !git branch --show-current || true
  • Staged changes: !git diff --cached --stat || true
  • Unstaged changes: !git diff --stat || true

Your Task

Review the following for code quality, security, and maintainability. This is a review, not an implementation task: do not edit files.

Target: $ARGUMENTS

If no target is specified, review all staged and unstaged changes. If there are none, review the last commit (git diff HEAD~1).

Review Checklist

Clean Code

  • Names are clear and intention-revealing
  • Functions are small and focused (single responsibility)
  • No code duplication
  • Appropriate level of abstraction
  • Code follows existing project patterns and conventions
  • Domain rules live in actions, reusable mechanics in the service layer (/code-structure); no god or leaky services

Quality

  • Error handling is comprehensive and graceful
  • Edge cases are handled (null, empty, boundary conditions)
  • No debugging artifacts left behind (console.log, TODO hacks)
  • Dependencies properly managed
  • Performance considerations addressed where relevant

Security

  • No injection vulnerabilities (SQL, command, XSS)
  • Input validation at system boundaries
  • Sensitive data not exposed (logs, error messages, responses)
  • Auth/authz checked where needed
  • No hardcoded secrets or credentials

Maintainability

  • Code is testable with clear boundaries
  • Changes are backwards compatible (or breaking changes documented)
  • Cognitive complexity is low (minimal nesting, clear flow)
  • Prose the change touched (comments, docs, commit message) passes the /unslop checklist

Output Format

## Code Review

### Summary
[1-2 sentence overview of what was reviewed]

### Issues Found

**Must Fix:**
- [Issue] — `file:line` — [why it matters]

**Should Fix:**
- [Issue] — `file:line` — [why it matters]

**Consider:**
- [Suggestion] — `file:line` — [potential improvement]

### What Looks Good
- [Positive observation]

### Verdict: [APPROVE | APPROVE WITH COMMENTS | REQUEST CHANGES]

Be specific with file paths and line numbers. Focus on substance, not style nitpicks.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.