code-review

Analyze codebases for code smells and pragmatic programming violations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps teams ensure consistent code quality by systematically identifying code smells and pragmatic programming violations during reviews.

Core Features & Use Cases

  • PR/diff review: quickly assess changed files focusing on the most relevant lines and context.
  • Full codebase audit: scan entry points and core logic to detect architectural smells and maintainability issues.
  • Structured reporting: produces a Markdown report with severity-based sections and actionable remediation notes.

Quick Start

Ask the AI to review the latest PR diffs or the codebase and return a structured severity report.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I identify code smells and pragmatic programming violations in a pull request diff?

To identify code smells in a pull request diff, analyze the changed files focusing on the most relevant lines and context. This process detects pragmatic programming violations and generates a structured severity report for quick assessment.

What is a structured code review report for a full codebase audit?

A structured code review report is a Markdown document detailing code smells and pragmatic programming violations by severity. It scans entry points and core logic to detect architectural issues and provide actionable remediation notes.

How to perform a full codebase audit for maintainability issues and code smells?

To perform a full codebase audit, prioritize scanning entry points, core logic, and frequently modified files. This detects architectural smells and maintainability issues, outputting a Markdown report with severity sections and actionable remediation notes.

Can I run static analysis for code reviews across multiple programming languages?

Yes, you can run static analysis for code reviews across multiple languages. The review applies to both PR diffs and full repository audits, identifying code smells and pragmatic programming violations regardless of the specific programming language.

Does code review work with markdown reports for pull request quality assurance?

Yes, code review works with markdown reports for quality assurance by producing a CODE_REVIEW.md file. This report organizes identified code smells and pragmatic programming violations into severity sections with actionable remediation notes.