Fstrent code reviewer

Skill wrm3/ai_project_template/plugins/fstrent-spec-tasks/skills/fstrent-code-reviewer

Comprehensive code review following company standards with focus on security, performance, maintainability, and best practicesFrom its SKILL.md

Install

npx -y skills add wrm3/ai_project_template --skill fstrent-code-reviewer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.8 KB, 763 tokens by cl100k_base, as published. Nobody here has run it

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:

Summary: Overall assessment (Approve/Request Changes/Comment)
Security Issues: Critical/High/Medium/Low with recommendations
Quality Issues: Categorized by severity
Performance Concerns: Identified bottlenecks
Best Practices: Suggestions for improvement
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

What ships with it: 3 files

30.7 KB alongside SKILL.md

examples/

sample_review.md7.8 KB

reference/

security_checklist.md9.1 KB

rules.md13.8 KB

Gives 0 of the 12 instructions most code review skills give in 763 tokens

Counted across 610 of the 674 authors here whose files we hold, read 2026-08-07

Push back with technical reasoning if wrongin 60 of 610, across 26 files
Ask for clarification on unclear itemsin 50 of 610, across 16 files
Fix critical issues immediatelyin 45 of 610, across 29 files
Implement one item at a timein 45 of 610, across 11 files
Group findings by severityin 44 of 610, across 43 files
Verify feedback against the codebasein 42 of 610, across 9 files
Dispatch a code reviewer subagentin 39 of 610, across 23 files
Fix important issues before proceedingin 37 of 610, across 22 files
Test each fix individuallyin 35 of 610, across 8 files
Reply in GitHub comment threadsin 33 of 610, across 5 files
Check for security vulnerabilitiesin 31 of 610, across 27 files
Factualize corrections without over-explainingin 30 of 610, across 2 files

Said here and by no other author read

identify xss attack vectors
review input validation
detect secrets and credentials
check documentation completeness
review error handling patterns

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.