code-review

Review code changes for logic errors, security issues, and anti-patterns.

13|3|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/heaptracetechnology/heaptrace-skills --skill code-review-heaptracetechnology
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/heaptracetechnology/heaptrace-skills/tree/main/code-review
Command: npx skills add https://github.com/heaptracetechnology/heaptrace-skills --skill code-review-heaptracetechnology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews code changes for logic errors, security issues, performance problems, duplication, and best practice violations. Use before merging a PR, after completing a feature, or when reviewing a teammate's work.

Core Features & Use Cases

  • Multi-pass review methodology — logic, security, performance, naming, tests, patterns, UX, docs
  • Security and quality checks — authentication, authorization, data exposure, input validation, error handling
  • Structured feedback & governance — severity levels, actionable fixes, and consistency with project standards
  • Code review automation guidance — gather context from diffs, enforce standards, and surface anti-patterns

Quick Start

Review the latest diff with the 8-pass framework to surface issues and drive fixes.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review a pull request for security and performance issues?

Review a pull request for security and performance by applying a structured 8-pass process that checks logic, error handling, duplication, and consistency. This surfaces anti-patterns, assigns severity levels, and provides actionable fix guidance.

What is the best way to find logic errors and anti-patterns before merging code?

Finding logic errors and anti-patterns before merging requires analyzing code diffs across multi-pass checks for naming, readability, and testing. The process enforces project standards and ensures maintainability and correctness across backend, frontend, and infrastructure.

Can I use an automated code review to check for data exposure and input validation?

Yes, automated code review can check for data exposure and input validation by gathering context from diffs. It enforces standards by identifying authentication, authorization, and error handling issues with structured feedback and clear severity levels.

How do I ensure code changes maintain consistency with existing project patterns?

Ensure code changes maintain consistency with existing project patterns by running a final consistency check pass during the review. This verifies that new code adheres to established architectural standards and prevents pattern drift.

Does structured code review work for both frontend and backend infrastructure changes?

Structured code review works for frontend, backend, and infrastructure changes. It applies a uniform 8-pass methodology to evaluate maintainability and correctness across different tech stacks and environments.

When do I need to run a multi-pass code review on a completed feature?

Run a multi-pass code review on a completed feature right before merging a pull request. It catches logic and security issues, validates testing coverage, and ensures the implementation aligns with project best practices.