code-review

Automate code-quality reviews with linting, static analysis, and security checks.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/pikakit/agent-skills --skill code-review-pikakit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/pikakit/agent-skills/tree/main/.agent/skills/code-review
Command: npx skills add https://github.com/pikakit/agent-skills --skill code-review-pikakit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Code review and quality control covering linting, static analysis, security, and best practices. The system enforces a 5-category review, a 4-level comment taxonomy, and a mandatory quality loop to improve consistency across teams and projects.

Core Features & Use Cases

  • Structured 5-category review checklist (correctness, security, performance, quality, testing)
  • Automated lint, type checks, and security checks integrated into a quality loop
  • PR and CI gate automation to accelerate safe deployments and reduce defects
  • Guidance for governance and compliance in code changes

Quick Start

Start the quality loop on a PR to surface issues and approve changes.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate PR review for code quality and security checks?

Automate PR review by enforcing a 5-category checklist covering correctness, security, performance, quality, and testing. It integrates lint, type checks, and static analysis into a mandatory quality loop to surface issues and accelerate safe deployments.

What is a structured code review checklist for CI gates?

A structured code review checklist for CI gates categorizes static analysis and security checks into five distinct levels. It uses a 4-level comment taxonomy and a mandatory quality loop to enforce best practices and reduce defects across projects.

How do I enforce merge criteria for lint and static analysis in pull requests?

Enforce merge criteria for lint and static analysis by applying deterministic input/output contracts with frontmatter-defined skill references. The automated quality loop blocks PRs from merging until strict review criteria and best practices are fully satisfied.

Does automated code review work with my existing CI-CD pipeline?

Automated code review integrates with CI-CD pipelines through script components applied to PRs, commits, and CI gates. It enforces a 5-category review and mandatory quality loop without requiring external dependencies to ensure safer deployments.

What is the best way to govern compliance and consistency in code changes?

Govern compliance and consistency by enforcing a 4-level comment taxonomy and a 5-category review checklist. This automated approach provides strict merge criteria and well-defined error handling to maintain high code quality across teams.

When should I not use automated static analysis for pull requests?

Avoid using automated static analysis for pull requests when a deterministic input/output contract cannot be established or when frontmatter-defined skill references are missing. The mandatory quality loop requires strict merge criteria to function correctly.