review

Review code changes for defects, security risks, and missing test coverage.

1|Updated May 18, 2026
One-click install
npx skills add https://github.com/linenoize/topia --skill review-linenoize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/linenoize/topia/tree/main/skills/review
Command: npx skills add https://github.com/linenoize/topia --skill review-linenoize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill catches defects, security risks, and regressions in code changes before they reach production, helping teams review faster without missing important issues.

Core Features & Use Cases

  • Bug detection: Finds logic errors, edge cases, race conditions, and broken behavior in changed code.
  • Security review: Flags unsafe input handling, auth gaps, secrets exposure, and other high-risk patterns.
  • Quality gating: Checks test coverage, API compatibility, blast radius, and spec compliance for pull requests and refactors.
  • Use case: A developer asks for a pre-merge review of a feature branch and gets severity-ranked findings with precise file and line references.

Quick Start

Review the attached code changes and return a severity-ranked report that separates spec compliance from code quality.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review code changes for security risks and missing test coverage before merging?

Code review for pull requests checks logic errors, unsafe input handling, and missing test coverage. It returns a severity-ranked report with exact file and line references, separating spec compliance from code quality.

What is the best way to catch performance regressions and bugs in a feature branch?

The best way to catch performance regressions is to review the changed code for logic errors, race conditions, and broken behavior. This process provides severity-ranked findings with remediation guidance before the branch reaches production.

Can I use this for refactoring shared libraries and checking API compatibility?

Yes, you can review refactors across application code, APIs, and shared libraries. It performs quality gating by checking API compatibility, blast radius awareness, and spec compliance to ensure safe refactoring.

How does a pre-merge code review identify blast radius in production-critical changes?

A pre-merge code review identifies blast radius by requiring file-level evidence and checking spec compliance. It flags production-critical implementation changes, returning severity-ranked findings with remediation guidance.

What kind of code quality issues can I find when reviewing pull requests?

Reviewing pull requests can find logic errors, edge cases, race conditions, auth gaps, and secrets exposure. The review checks spec compliance and returns severity-ranked findings with specific file references and remediation guidance.