reviewer

Identify bugs, security issues, performance gaps, and readability problems in code reviews.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/mag123c/linkhub --skill reviewer-mag123c
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewer
Source: https://github.com/mag123c/linkhub/tree/main/.claude/skills/reviewer
Command: npx skills add https://github.com/mag123c/linkhub --skill reviewer-mag123c

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

코드 리뷰에서 누락되기 쉬운 버그, 보안, 성능, 가독성 이슈를 식별하고 개선 방향을 제시합니다.

Core Features & Use Cases

  • 체크리스트 기반 리뷰 가이드 제공: 버그, 보안, 성능, 아키텍처, 가독성에 대한 체계적 평가.
  • 우선순위 태그와 리뷰 템플릿을 활용한 협업 촉진.
  • PR 리뷰 및 자기 검토 시 일관된 피드백 품질을 확보.

Quick Start

Run a reviewer pass on the target PR to generate actionable feedback.

Frequently Asked Questions about reviewer

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

FAQPage Schema
How do I identify security and bug issues during a code review?

To identify security and bug issues during a code review, apply a structured checklist that evaluates code for vulnerabilities, performance gaps, and readability. This approach uses prioritized tags and templates to guide engineers through systematic feedback.

What is the best way to structure PR reviews for software projects?

The best way to structure PR reviews is by using a standardized template and prioritized tags. This enforces consistent feedback quality by systematically evaluating architecture, security, performance, and readability across all pull requests.

Can I use a checklist for self-review before submitting a pull request?

Yes, you can use a checklist for self-review before submitting a pull request. It helps independently assess your code for bugs, security flaws, performance gaps, and readability issues to ensure quality before peer review.

How does a structured code review improve software quality?

A structured code review improves software quality by systematically surfacing bugs, security issues, and performance gaps that are easily missed. It provides a consistent template to ensure comprehensive evaluation across architecture and readability.

Do I need specific tools to perform a structured code review?

No specific external tools are required to perform this structured code review. It operates independently without dependencies, using built-in checklists and prioritized tags to guide the evaluation of bugs, security, and readability.