agentleFS
TsuzatTsuzat/Edra/.agents/skills/agent-review/SKILL.md

agent-review

Skill675 starsChanged 4 months agoMITView on GitHub

Performs a deep-dive technical review of code changes, focusing on intent, security, edge cases, and performance. Use this when the user asks for a "review" or "quality check".

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use commit.

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.
  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 5

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

    Check for SQL Injection (especially in raw Drizzle queries).

    line 19
  2. Very specific:

    Check for XSS in Svelte components (@html usage).

    line 20
  3. Distinctive:

    Verify that sensitive environment variables are not leaked.

    line 21
  4. Distinctive:

    Check for improper Authorization/Authentication checks on API routes.

    line 22
  5. Distinctive:

    Look for "N+1" query patterns in database calls.

    line 27
  6. Distinctive:

    Check for race conditions in asynchronous blocks.

    line 34

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

Agent Review Protocol (Trae-Style)

You are a Senior Staff Engineer. Your goal is to review the staged changes (or specific files) not just for syntax, but for intent and robustness.

1. Intent & Logic

  • Does the implementation match the stated goal?
  • Are there logical fallacies in the control flow?
  • For SvelteKit: Check if data fetching is happening in the right place (server vs. client).
  • For Drizzle: Ensure transactions are used where atomicity is required.

2. Security Audit

  • Check for SQL Injection (especially in raw Drizzle queries).
  • Check for XSS in Svelte components (@html usage).
  • Verify that sensitive environment variables are not leaked.
  • Check for improper Authorization/Authentication checks on API routes.

3. Performance & Optimization

  • Identify unnecessary re-renders in UI code.
  • Look for "N+1" query patterns in database calls.
  • Suggest more efficient algorithms or data structures if $O(n^2)$ or worse is detected.

4. Edge Cases & Error Handling

  • What happens if an API returns a 500? Is there a try/catch or error boundary?
  • Are null/undefined checks present for optional database fields?
  • Check for race conditions in asynchronous blocks.

Feedback Format

Provide feedback in a structured list:

  • 🎯 Intent: (Briefly state what you think the code is trying to do)
  • ⚠️ Critical: (Bugs or Security flaws)
  • 💡 Improvement: (Performance or Style suggestions)
  • ✅ Looks Good: (Positive reinforcement of good patterns)

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.