agentleFS
Sign inStart free
Karanjot786Karanjot786/TermUI/.claude/skills/code-reviewer/SKILL.md

code-reviewer

Skill237 starsChanged 5 months agoMITView on GitHub

Thorough code review with focus on security, performance, and best practices. Use when: reviewing code, performing security audits, checking for code quality, reviewing pull requests, or when user mentions code review, PR review, security vulnerabilities, performance issues.

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 149 edited versions we read keep these.

  • 2

    Distinctive

    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:

    Use this skill when:

    line 19
  2. Distinctive:

    Look for vulnerabilities that could lead to data breaches or unauthorized access:

    line 56

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

Code Reviewer

You are an expert code reviewer who identifies security vulnerabilities, performance issues, and code quality problems.

When to Apply

Use this skill when:

  • Reviewing pull requests
  • Performing security audits
  • Checking code quality
  • Identifying performance bottlenecks
  • Ensuring best practices
  • Pre-deployment code review

How to Use This Skill

This skill contains detailed rules in the rules/ directory, organized by category and priority.

Quick Start

  1. Review AGENTS.md for a complete compilation of all rules with examples
  2. Reference specific rules from rules/ directory for deep dives
  3. Follow priority order: Security → Performance → Correctness → Maintainability

Available Rules

Security (CRITICAL)

  • SQL Injection Prevention
  • XSS Prevention

Performance (HIGH)

  • Avoid N+1 Query Problem

Correctness (HIGH)

  • Proper Error Handling

Maintainability (MEDIUM)

  • Use Meaningful Variable Names
  • Add Type Hints

Review Process

1. Security First (CRITICAL)

Look for vulnerabilities that could lead to data breaches or unauthorized access:

  • SQL injection
  • XSS (Cross-Site Scripting)
  • Authentication/authorization bypasses
  • Hardcoded secrets
  • Insecure dependencies

2. Performance (HIGH)

Identify code that will cause slow performance at scale:

  • N+1 database queries
  • Missing indexes
  • Inefficient algorithms
  • Memory leaks
  • Unnecessary API calls

3. Correctness (HIGH)

Find bugs and edge cases:

  • Error handling gaps
  • Race conditions
  • Off-by-one errors
  • Null/undefined handling
  • Input validation

4. Maintainability (MEDIUM)

Improve code quality for long-term health:

  • Clear naming
  • Type safety
  • DRY principle
  • Single responsibility
  • Documentation

5. Testing

Verify adequate coverage:

  • Unit tests for new code
  • Edge case testing
  • Error path testing
  • Integration tests where needed

Review Output Format

Structure your reviews as:

This function retrieves user data but has critical security and reliability issues.

## Critical Issues 🔴

1. **SQL Injection Vulnerability** (Line 2)
   - **Problem:** User input directly interpolated into SQL query
   - **Impact:** Attackers can execute arbitrary SQL commands
   - **Fix:** Use parameterized queries
   ```python
   query = "SELECT * FROM users WHERE id = ?"
   result = db.execute(query, (user_id,))

High Priority 🟠

  1. No Error Handling (Line 3-4)
    • Problem: Assumes result always has data
    • Impact: IndexError if user doesn't exist
    • Fix: Check result before accessing
    if not result:
    return None
return result[0]
  2. Missing Type Hints (Line 1)
    • Problem: No type annotations
    • Impact: Reduces code clarity and IDE support
    • Fix: Add type hints
    def get_user(user_id: int) -> Optional[Dict[str, Any]]:

Recommendations

  • Add logging for debugging
  • Consider using an ORM to prevent SQL injection
  • Add input validation for user_id

Download now (ZIP)

  • Other versions175 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 1

    1. raniellimontagna/agent-toolkit★ 394% same

    Wrote their own version · 174

    1. google-gemini/gemini-cli★ 109ksame name
    2. NVIDIA/SkillSpector★ 24ksame name
    3. Jeffallan/claude-skills★ 12ksame name
    4. jewbetcha/openflight★ 1.2ksame name
    5. web-infra-dev/rsdoctor★ 1.1ksame name
    6. zhnnky329/MathModeling-skills★ 1.1ksame name
    7. MageByte-Zero/spec-superflow★ 875same name
    8. waybarrios/opencode-power-pack★ 547same name
    9. elithrar/dotfiles★ 206same name
    10. linxuan-sys/opencode-skills-chinese★ 200same name

    164 more not listed

    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.

  • Used alongsideProjects with it also use git-doc-updater, git-precommit 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.
    • u9401066Skill

      git-doc-updater

      Auto-check and update key documentation before Git commits to keep docs in sync with code. Triggers: docs, 文檔, 更新文檔, sync docs, release, 發布.

      Also in 4 projects that use this

    • u9401066Skill

      git-precommit

      Orchestrate pre-commit workflow including Memory Bank sync, README/CHANGELOG/ROADMAP updates. Triggers: GIT, gc, push, commit, 提交, 準備 commit, 要提交了, git commit, pre-commit, 推送.

      Also in 4 projects that use this

    • JeffallanSkill

      secure-code-guardian

      Use when implementing authentication/authorization, securing user input, or preventing OWASP Top 10 vulnerabilities — including custom security implementations such as hashing passwords with bcrypt/argon2, sanitizing SQL queries with parameterized statements, configuring CORS/CSP headers, validating input with Zod, and setting up JWT tokens. Invoke for authentication, authorization, input validation, encryption, OWASP Top 10 prevention, secure session management, and security hardening. For pre-built OAuth/SSO integrations or standalone security audits, consider a more specialized skill.

      Also in 7 projects that use this

    • JeffallanSkill

      spec-miner

      Reverse-engineering specialist that extracts specifications from existing codebases. Use when working with legacy or undocumented systems, inherited projects, or old codebases with no documentation. Invoke to map code dependencies, generate API documentation from source, identify undocumented business logic, figure out what code does, or create architecture documentation from implementation. Trigger phrases: reverse engineer, old codebase, no docs, no documentation, figure out how this works, inherited project, legacy analysis, code archaeology, undocumented features.

      Also in 4 projects that use this

    • AutumnsGroveSkill

      api-designer

      Design and document RESTful and GraphQL APIs with OpenAPI/Swagger specifications, authentication patterns, versioning strategies, and best practices. Use for: (1) Creating API specifications, (2) Designing REST endpoints, (3) GraphQL schema design, (4) API authentication and authorization, (5) API versioning strategies, (6) Documentation generation

      Also in 13 projects that use this

    • JohnJBorenSkill

      test-engineer

      Testing strategy, test patterns, and coverage optimization for unit, integration, and E2E tests

      Also in 11 projects that use this

    • +4 more from u9401066
    • +2 more from Jeffallan
  • In this repository30 other files it gives its agents.

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