agentleFS
roborracleroborracle/agent-workflow-kit/skills/code-reviewer/SKILL.md

code-reviewer

Skill0 starsChanged 3 months agoMITView on GitHub

Comprehensive code review from senior engineering perspective following OWASP standards and industry best practices. Use after completing code development, before merging PRs, or when seeking quality assurance feedback.

182 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects 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 5 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 5 projects that use this

  • JeffallanSkill

    shopify-expert

    Builds and debugs Shopify themes (.liquid files, theme.json, sections), develops custom Shopify apps (shopify.app.toml, OAuth, webhooks), and implements Storefront API integrations for headless storefronts. Use when building or customizing Shopify themes, creating Hydrogen or custom React storefronts, developing Shopify apps, implementing checkout UI extensions or Shopify Functions, optimizing performance, or integrating third-party services. Invoke for Liquid templating, Storefront API, app development, checkout customization, Shopify Plus features, App Bridge, Polaris, or Shopify CLI workflows.

    Also in 5 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 6 projects that use this

  • +4 more from u9401066
  • +4 more from Jeffallan

The file

Files
SKILL.md

Code Reviewer

Comprehensive code review following "Security-First, Performance-Second" principle.

Review Phases

Phase 1: Security Audit (OWASP Top 10, current edition)

  • Broken access control, including insecure direct object references
  • Injection: SQL (parameterized queries), XSS, command injection
  • Cryptographic failures and sensitive data exposure
  • Authentication and session management flaws
  • Security misconfiguration
  • Vulnerable or outdated dependencies
  • Server-side request forgery (SSRF)
  • CSRF on state-changing requests

Phase 2: Logic and Correctness

  • Algorithm correctness and efficiency
  • Edge case handling, null/undefined checks
  • Race conditions and concurrency issues
  • Resource cleanup and memory management

Phase 3: Performance Analysis

  • Time/space complexity (Big O)
  • Database query optimization (N+1 problems)
  • Caching opportunities
  • Unnecessary re-renders or computations

Phase 4: Code Quality

  • SOLID principle adherence, DRY violations
  • Naming conventions and clarity
  • Function/class cohesion, cyclomatic complexity
  • Documentation completeness

Phase 5: Testing Coverage

  • Unit test coverage and quality
  • Integration test scenarios
  • Edge case test coverage

Severity Triage

LevelMeaningAction
🔴 CriticalSecurity vulnerabilities or data loss risksBlocks deployment
🟠 HighBugs that will cause failures in productionMust fix before merge
🟡 MediumPerformance issues or maintenance concernsShould address soon
🟢 LowCode style or minor optimizationsNice-to-have

Issue Format

**Severity**: [🔴/🟠/🟡/🟢]
**Location**: `path/to/file.ext:L42-L45`
**Problem**: Clear description
**Impact**: How this affects users or system
**Solution**: Concrete code example

Also Highlight

  • Well-implemented patterns
  • Good architectural decisions
  • Effective use of best practices

Additional Resources

  • For the full review checklist (security, logic, performance, quality, testing), see reference/review-checklist.md

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.

Reviews can't be read right now.

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.