agentleFS
gologo13gologo13/agent-skills/skills/light-review-existing-diffs/SKILL.md

light-review-existing-diffs

Skill0 starsChanged 9 months agoMITView on GitHub

Perform a quick quality pass on current diffs to surface risky areas, ensure polish, and fla...; keywords: debug, review, test, fix. Use only on explicit request; skip in routine implementation discussions.

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify naming, formatting, and imports follow project standards

    line 21
  2. Distinctive:

    Check that tests or documentation were updated when behavior changed

    line 22
  3. Distinctive:

    Document any quick fixes you can apply immediately

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Light Review Existing Diffs

Overview

Perform a quick quality pass on current diffs to surface risky areas, ensure polish, and flag follow-up actions for deeper review.

Steps

  1. Scan recent changes
    • List open branches or pending commits requiring review
    • Skim side-by-side diffs focusing on new or modified files
    • Note files or modules with large or complex edits
  2. Assess quality signals
    • Watch for TODOs, debug code, or commented blocks needing cleanup
    • Verify naming, formatting, and imports follow project standards
    • Check that tests or documentation were updated when behavior changed
  3. Flag next actions
    • Mark sections that warrant full review or pair programming
    • Capture questions or uncertainties to raise with the author
    • Document any quick fixes you can apply immediately

Review Checklist

  • High-risk files identified
  • Debugging artifacts removed or flagged
  • Style and conventions validated
  • Tests/docs updates confirmed or requested
  • Follow-up items recorded for deeper review

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.