code-review-and-quality

Evaluate code changes across correctness, readability, architecture, security, and performance.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/HellKaiser45/Podlet --skill code-review-and-quality-hellkaiser45
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-and-quality
Source: https://github.com/HellKaiser45/Podlet/tree/main/.podlet/skills/code-review-and-quality
Command: npx skills add https://github.com/HellKaiser45/Podlet --skill code-review-and-quality-hellkaiser45

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates rigorous, multi-dimensional code reviews to prevent suboptimal merges and raise overall code health.

Core Features & Use Cases

  • Five-axis evaluation: correctness, readability, architecture, security, and performance.
  • Actionable remediation guidance with concrete improvements.
  • Suitable for pull requests, feature branches, and post-change audits across human or agent reviewers.

Quick Start

Run a five-axis review on the provided change set to identify defects, risks, and improvement opportunities.

Frequently Asked Questions about code-review-and-quality

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

FAQPage Schema
How do I automate a multi-axis code review for a pull request?

Automate a multi-axis code review by evaluating code changes across correctness, readability, architecture, security, and performance. This provides structured feedback with edge-case considerations, security notes, and clear remediation guidance to ensure healthy merges.

What is included in a five-axis code quality assessment?

A five-axis code quality assessment evaluates correctness, readability, architecture, security, and performance. It identifies defects, risks, and improvement opportunities, providing actionable remediation guidance with concrete improvements for feature branches and patches.

Can I use automated code review for post-change audits on feature branches?

Yes, you can use automated code review for post-change audits on feature branches. It applies to pull requests, feature branches, and patch assessments across human or agent reviewers to prevent suboptimal merges and raise overall code health.

What is the best way to check security and performance risks before a merge?

The best way to check security and performance risks before a merge is running a five-axis review on the change set. It identifies defects, evaluates architecture and security, and provides clear remediation guidance to prevent suboptimal merges.

Does this code review approach work for both human and agent reviewers?

Yes, this code review approach works for both human and agent reviewers. It identifies and evaluates code changes across five axes and provides structured feedback with edge-case considerations and security notes suitable for any reviewer type.