code-review

Review code changes for security, performance, and correctness issues.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/FoundationForge/cowork-plugins --skill code-review-foundationforge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/FoundationForge/cowork-plugins/tree/main/plugins/engineering/skills/code-review
Command: npx skills add https://github.com/FoundationForge/cowork-plugins --skill code-review-foundationforge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers and reviewers quickly identify security vulnerabilities, performance regressions, correctness bugs, and maintainability issues in code changes so teams can ship safer, faster, and more reliable software.

Core Features & Use Cases

  • Security audits: Detect OWASP top-10 risks, injection vectors, credential leaks, and auth/authorization flaws in diffs or PRs.
  • Performance analysis: Surface N+1 queries, costly allocations, missing indexes, and algorithmic inefficiencies.
  • Correctness & maintainability: Highlight edge cases, race conditions, error handling gaps, and suggest actionable fixes with code examples; useful for PR reviews, pre-merge checks, and training new reviewers.

Quick Start

Ask the skill to review a pull request or paste a diff and request security, performance, and maintainability feedback.

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check a pull request for OWASP security vulnerabilities?

Reviewing a pull request for OWASP vulnerabilities involves scanning diffs to detect injection vectors, credential leaks, and auth flaws, then producing actionable suggestions and a verdict to fix them.

How do I find N+1 queries and performance anti-patterns in a code diff?

Finding N+1 queries and performance anti-patterns in a code diff requires analyzing changes to surface costly allocations, missing indexes, and algorithmic inefficiencies, yielding actionable optimization suggestions.

What is the best way to review code changes for edge-case correctness and error handling?

Reviewing code changes for edge-case correctness and error handling highlights race conditions and gaps, providing actionable fixes with code examples to improve software reliability and maintainability.

Can I assess maintainability concerns when reviewing file paths instead of full pull requests?

Assessing maintainability concerns when reviewing file paths instead of full pull requests works by applying the same analysis to detect error handling gaps and edge cases, yielding actionable suggestions and a verdict.

Does automated code review work for pre-merge checks and training new reviewers?

Automated code review works for pre-merge checks and training new reviewers by evaluating security, performance, and correctness in diffs, producing actionable fixes with code examples to guide learning.