skills.rest
hypeJunction
hypeJunctionCOMMUNITY
Explore all skills by this author →
GitHub

review

Review current branch code against the base branch with severity ratings.

1|Updated Dec 1, 2025
Search Tags:#quality assurance#code review#maintainability#security audit#performance analysis#pre-merge check
One-click install
npx skills add https://github.com/hypeJunction/ai-assistant-starter --skill review-hypejunction
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/hypeJunction/ai-assistant-starter/tree/main/skills/review
Command: npx skills add https://github.com/hypeJunction/ai-assistant-starter --skill review-hypejunction

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a thorough, read-only code review of your current branch against the base branch, identifying potential issues and offering actionable feedback to improve code quality before merging.

Core Features & Use Cases

  • Comprehensive Analysis: Scans all changed files for correctness, security, performance, testing, and maintainability issues.
  • Severity-Rated Findings: Classifies issues into P0 (Critical) to P3 (Low) with confidence levels.
  • Actionable Feedback: Provides specific evidence, suggested fixes, and positive notes.
  • Use Case: Before merging a new feature, run /review to catch potential bugs, security vulnerabilities, or performance regressions, ensuring a higher quality codebase.

Quick Start

Run the review skill on your current branch to check code quality.

Frequently Asked Questions about review

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

FAQPage Schema
How do I run a comprehensive code review on my current branch before merging?▼

Run a comprehensive code review on your current branch to scan changed files against the base branch. It identifies correctness, security, performance, testing, and maintainability issues, providing actionable feedback before merging.

What severity levels are used to classify issues during a pre-merge code check?▼

A pre-merge code check classifies issues into P0 (Critical), P1, P2, and P3 (Low) severity levels. Each finding includes a confidence rating and specific evidence to help prioritize fixes for maintainability and security.

Can I scope a code review to specific files or pull requests?▼

Yes, you can scope a code review to specific files or pull requests using scope flags. This limits the read-only analysis to targeted changes, ensuring the security audit and performance analysis focus only on your specified codebase areas.

Does automated code review analyze security vulnerabilities and performance regressions?▼

Automated code review analyzes security vulnerabilities and performance regressions by scanning all changed files. It evaluates code for security flaws and performance drops, offering suggested fixes and positive notes to ensure a higher quality codebase.

What is the best way to audit code maintainability without modifying the codebase?▼

The best way to audit code maintainability is using a read-only code review. It analyzes the current branch against the base branch without modifying the codebase, providing actionable feedback and severity-rated findings for maintainability.

Related Skills

Explore More Software Engineering Skills→
detorresramosdetorresramos
3

catching-up

Summarize current branch code changes relative to the base branch.

Community
Intermediate
StartaleGroupStartaleGroup
3

audit

Audit frontend projects for accessibility, performance, theming, and responsiveness issues.

Official
Advanced
lehuuhau1231lehuuhau1231

lint-and-validate

Run linting and type checking across multiple programming ecosystems.

Community
Intermediate
arbazkhan971arbazkhan971
26

devsecops

Integrate security scanning into CI/CD pipelines with blocking gates.

Community
Advanced