skills.rest
cuongtl1992
cuongtl1992COMMUNITY
Explore all skills by this author →
GitHub

code-reviewer

Identify and communicate code change issues with priority-labeled feedback.

10|7|Updated Jan 5, 2026
Search Tags:#architecture#feedback#security#quality#code-review#pull-request#review-checklist
One-click install
npx skills add https://github.com/cuongtl1992/vibe-skills --skill code-reviewer-cuongtl1992
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/cuongtl1992/vibe-skills/tree/main/skills/common/code-reviewer
Command: npx skills add https://github.com/cuongtl1992/vibe-skills --skill code-reviewer-cuongtl1992

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Systematic, consistent code review feedback that improves quality and maintainability across teams.

Core Features & Use Cases

  • Review workflow: Follows a repeatable, checklist-driven process for code changes.
  • Structured feedback: Uses priority prefixes (BLOCKING, SUGGESTION, QUESTION, NIT) to categorize issues.
  • Documentation alignment: References established checklists and patterns for architecture, security, and quality.

Quick Start

Review the attached code changes and produce structured, priority-labeled feedback using BLOCKING, SUGGESTION, QUESTION, and NIT prefixes.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I get structured code review feedback for my pull request?▼

Code review feedback is generated by analyzing code changes against a checklist and returning structured comments with priority labels like BLOCKING, SUGGESTION, QUESTION, and NIT to communicate issue severity.

What is the best way to enforce a consistent code review checklist across a team?▼

A consistent code review checklist is enforced by applying a fixed review workflow that references established patterns for architecture, security, and quality to ensure systematic and repeatable feedback.

Can I use priority labels to categorize issues found during a code review?▼

Yes, you can use priority labels like BLOCKING, SUGGESTION, QUESTION, and NIT to categorize code review issues, providing structured and actionable feedback that clearly communicates severity.

Does this code review process cover both security and architecture checks?▼

Yes, the code review process covers security and architecture checks alongside quality, performance, testing, and documentation, referencing established checklists to evaluate code changes comprehensively.

How do I identify blocking issues versus minor suggestions in a code review?▼

Blocking issues versus minor suggestions are identified through a checklist-driven review process that assigns standardized prefixes like BLOCKING for critical problems and SUGGESTION or NIT for lower-priority feedback.

Related Skills

Explore More Software Engineering Skills→
htayjhtayj

code-review

Analyze code diffs for bugs, security risks, and maintainability issues.

Community
Intermediate
phrazzldphrazzld
13

pr-polish

Review and refine pull requests with code, test, and documentation updates.

Community
Advanced
OirancaOiranca

ci-checks

Executes lint, type-check, test, and build commands for CI validation.

Community
Intermediate
prof-danielcprof-danielc

speckit.checker

Run static analysis tools and aggregate results into a prioritized issue report.

Community
Advanced