agentleFS
wrm3wrm3/ai_project_template/.claude/skills/fstrent-code-reviewer/SKILL.md

fstrent-code-reviewer

Skill1 starsChanged 13 months agoMITView on GitHub

Comprehensive code review following company standards with focus on security, performance, maintainability, and best practices

The file

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:

    Ask for a code review

    line 26
  2. Distinctive:

    Check code before committing

    line 30
  3. Distinctive:

    fstrent-task-management: Create tasks for review findings

    line 154

≈ “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

fstrent Code Reviewer

Perform thorough code reviews following company-specific templates, security guidelines, and best practices.

Overview

This skill provides comprehensive code review capabilities with structured checklists, security scanning, performance analysis, and maintainability assessments. It ensures consistent code quality across your projects by following standardized review procedures.

When to Use

This skill activates automatically when you:

  • Ask for a code review
  • Request security scanning
  • Need quality assessment
  • Review pull requests
  • Check code before committing

Capabilities

1. Security Review

  • SQL injection vulnerability detection
  • XSS attack vector identification
  • Authentication/authorization checks
  • Sensitive data exposure prevention
  • Input validation review
  • Secret/credential detection

2. Code Quality Assessment

  • Code style compliance
  • Naming conventions
  • Documentation completeness
  • Error handling patterns
  • Code complexity analysis
  • DRY principle adherence

3. Performance Analysis

  • Algorithm efficiency
  • Database query optimization
  • Memory usage patterns
  • Network request efficiency
  • Caching opportunities
  • Resource cleanup

4. Maintainability Review

  • Code organization
  • Function/class size (target: <100 lines, warn: >200 lines)
  • Cyclomatic complexity
  • Test coverage
  • Documentation quality
  • Technical debt identification

5. Best Practices

  • Language-specific idioms
  • Framework conventions
  • Design patterns
  • SOLID principles
  • Clean code principles
  • Team coding standards

Review Types

Quick Review

For small changes (<100 lines):

  • Security scan
  • Style check
  • Basic quality assessment
  • ~2-5 minutes

Standard Review

For typical changes (100-500 lines):

  • Full security scan
  • Code quality analysis
  • Performance check
  • Documentation review
  • ~10-20 minutes

Comprehensive Review

For large changes (>500 lines) or critical code:

  • In-depth security analysis
  • Detailed performance profiling
  • Architecture review
  • Test coverage analysis
  • Technical debt assessment
  • ~30-60 minutes

Output Format

Reviews generate:

  1. Summary: Overall assessment (Approve/Request Changes/Comment)
  2. Security Issues: Critical/High/Medium/Low with recommendations
  3. Quality Issues: Categorized by severity
  4. Performance Concerns: Identified bottlenecks
  5. Best Practices: Suggestions for improvement
  6. Action Items: Specific tasks to address findings

Integration

Works with:

  • GitHub Pull Requests
  • GitLab Merge Requests
  • Local file reviews
  • Diff-based reviews
  • Multi-file reviews

Examples

Quick Review:

"Review this authentication function for security issues"
→ Focused security scan with recommendations

Full PR Review:

"Review PR #123 for code quality and security"
→ Comprehensive review with checklist and ratings

Pre-Commit Check:

"Check this code before I commit"
→ Quick scan for obvious issues

Company Standards

This skill enforces your specific:

  • Coding standards
  • Security requirements
  • Testing requirements
  • Documentation standards
  • Performance SLAs

For detailed review procedures, see rules.md.

For examples and templates, see examples/ folder.

Related Skills

  • fstrent-task-management: Create tasks for review findings
  • fstrent-qa: Track bugs found during review
  • fstrent-planning: Plan refactoring based on review

Version: 1.0.0 Last Updated: 2025-10-19 Part of: fstrent-spec-tasks system

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.