code-review

Review modified code for correctness, security, performance, and architecture flaws.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standard code reviews often miss critical security flaws, performance bottlenecks, and architecture issues that lead to production outages and costly technical debt, leaving teams to fix preventable problems after deployment.

Core Features & Use Cases

  • Principal-Engineer-Depth Review: Evaluates code across 5 key dimensions: correctness, security, performance, maintainability, and architecture.
  • Pre-Merge Validation: Use for pull request reviews, task completion checks, and final validation before merging code to catch issues early in the development cycle.
  • Confidence-Scored Findings: All issues are tagged with confidence levels (high/medium/low) to distinguish blocking problems from minor suggestions for follow-up work.

Quick Start

Use the code-review skill to evaluate the changes in open pull request #42 for security vulnerabilities and performance bottlenecks.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I catch security vulnerabilities and performance bottlenecks before merging a pull request?

Deep code reviews identify correctness, security, performance, maintainability, and architecture flaws in modified code. This principal-engineer-level analysis evaluates pull requests to catch critical bugs, security vulnerabilities, and unplanned technical debt before production deployment.

How do I distinguish blocking code issues from minor suggestions during a pull request review?

Distinguish blocking code issues from minor suggestions using confidence-scored findings. Reviews tag all identified issues with high, medium, or low confidence levels to clearly separate critical blocking problems from minor suggestions for follow-up work.

What is the best way to audit modified code for technical debt before deployment?

The best way to audit modified code for technical debt is running pre-merge validation checks on task completion. This principal-engineer-level review identifies architecture issues and prevents costly technical debt before code is deployed to production.

Can I use a principal-engineer-level review for post-task completion checks in production workflows?

Yes, you can use principal-engineer-level reviews for post-task completion checks in production software engineering workflows. This validates final code changes to catch critical bugs and security vulnerabilities before deployment.

Why does standard code review miss critical security flaws and architecture issues?

Standard code review misses critical security flaws because it lacks deep evaluation across correctness, performance, maintainability, and architecture. Applying principal-engineer-level analysis identifies these issues pre-merge to prevent production outages.