code-reviewlisted

Reviews existing code and pull requests using multi-agent swarm analysis covering security, performance, style, test coverage, and documentation quality. Extracts and prioritizes PR comments, performs security audits, and generates actionable fix plans with file:line references. Use when the user asks to review code, review a PR, audit code for security, assess code quality, analyze pull request comments, get feedback on existing code, or perform a code audit. NOT for writing new code or implementing features (use other development skills), NOT for finding and fixing runtime bugs or errors (use debugging), NOT for writing tests or setting up test infrastructure (use testing-framework), NOT for TDD methodology (use test-driven-development).
viktorbezdek/skillstack · ★ 9 · Code & Development · score 79

Install: claude install-skill viktorbezdek/skillstack

# Comprehensive Code Review Skill This skill is a curated merge of four complementary code review skills: 1. **Evidence-Based Code Review**: Evidence-based multi-agent swarm review with specialized reviewers 2. **PR Comment Analysis**: Extract, consolidate, and prioritize GitHub PR comments 3. **Development Workflow Specialist**: TDD, debugging, performance optimization, and automated code review 4. **Consultant**: AI-powered deep analysis for complex architectural and security reviews --- ## When to Use **Use this skill when:** - Reviewing PRs systematically with multiple quality dimensions - Extracting and consolidating feedback from multiple reviewers - Need evidence-based findings with file:line references - Assessing security vulnerabilities, performance bottlenecks, or code quality - Creating action plans from PR comments - Complex architectural decisions requiring deep analysis - Audit requirements mandate systematic review (compliance, release gates) **Do NOT use for:** - Simple formatting fixes (use linter/prettier directly) - Non-code files (documentation, configuration without logic) - Trivial changes (typo fixes, comment updates) - Generated code (build artifacts, vendor dependencies) --- ## Core Capabilities ### 1. Evidence-Based Code Review Every finding MUST include: - Code location: `[file:line]` with surrounding context (5 lines before/after) - Evidence type: DIRECT, STYLE_RULE, or BEST_PRACTICE - Severity: CRITICAL, MAJOR, MINOR, or NIT - Confidence