agentleFS
Sign inStart free
grichagricha/dangerous-skills/skills/code-review/SKILL.md

review-staged

Skill38 starsChanged 8 months agoMITView on GitHub

Review staged git changes for bugs, style issues, and best practices. Use when the user asks for a code review or CR.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. microsoft/Agent365-devTools★ 61same name

    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 repository11 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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. Distinctive:

    Run git diff --staged to see what's being committed

    line 14
  2. Distinctive:

    If nothing is staged, run git diff to review unstaged changes

    line 15
  3. Very specific:

    When checking style and readability, refer to the project's coding standards documented in ${CLAUDE_SKILL_DIR}/review-guidelines.md.

    line 24
  4. Distinctive:

    Keep feedback specific and actionable.

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Code Review Skill

Review the currently staged git changes and provide actionable feedback.

Process

  1. Run git diff --staged to see what's being committed
  2. If nothing is staged, run git diff to review unstaged changes
  3. Analyze the diff for:
    • Bugs and logic errors
    • Security vulnerabilities (injection, XSS, hardcoded secrets)
    • Performance issues
    • Style and readability problems
    • Missing error handling
    • Test coverage gaps

When checking style and readability, refer to the project's coding standards documented in ${CLAUDE_SKILL_DIR}/review-guidelines.md.

Output Format

Provide your review as a structured list:

Critical Issues

List any bugs, security problems, or correctness issues that MUST be fixed.

Suggestions

List style, readability, and minor improvement suggestions.

Summary

A one-line overall assessment (e.g., "Looks good with minor nits" or "Has a critical SQL injection — do not merge").

Keep feedback specific and actionable. Reference exact line numbers from the diff. Be concise — developers don't want a wall of text.

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.

Check your setup, free