code-review

Automate layered code review for pull requests in CI pipelines.

3|2|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/Open-Paws/structured-coding-with-ai --skill code-review-open-paws
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Open-Paws/structured-coding-with-ai/tree/main/kilo-code/.kilocode/skills/code-review
Command: npx skills add https://github.com/Open-Paws/structured-coding-with-ai --skill code-review-open-paws

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates layered code review to catch issues before code merges, focusing on AI-generated and complex code to improve safety, quality, and maintainability.

Core Features & Use Cases

  • Layer 1: Automated Checks (formatting, linting, static analysis, security scanning, and tests)
  • Layer 2: AI-Assisted First-Pass Review (flagging common issues in error handling, conventions, and performance)
  • Layer 3: Human Review — Design Quality (Ousterhout red flags and maintainability concerns)
  • Layer 4: AI-Specific Failure Pattern Review (DRY violations, unsafe dependencies, and hallucinated APIs)
  • Layer 5: Advocacy-Specific Review (data privacy, safety, and boundary considerations)

Quick Start

Copy this skill into your project and run it as part of your pull request checks.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate code review for AI-generated code in pull requests?

Automated code review for AI-generated code applies a layered pipeline to pull requests, running linting, static analysis, and AI-assisted checks to catch hallucinated APIs and unsafe dependencies before merging.

What is a layered code review pipeline and when do I need it?

A layered code review pipeline sequentially applies automated checks, AI-assisted first-pass reviews, and human design evaluations to catch issues in complex codebases. You need it when merging AI-generated code requires safety, maintainability, and advocacy checks.

Can I use static analysis and linting to catch AI code hallucinations?

Static analysis and linting serve as the first automated layer to catch formatting and syntax issues, while a subsequent AI-specific failure pattern review layer targets hallucinated APIs, DRY violations, and unsafe dependencies in AI-generated code.

Does this code review pipeline handle security analysis and data privacy checks?

This code review pipeline includes security scanning in its automated checks layer and dedicates a final advocacy-specific review layer to evaluate data privacy, safety, and boundary considerations for the submitted code.

What's the best way to check Ousterhout red flags during a pull request review?

The best way to check Ousterhout red flags is through the human design quality review layer, which specifically evaluates maintainability concerns and design red flags after automated and AI-assisted checks pass.

Why does AI-assisted code review need a separate failure pattern layer?

AI-assisted code review needs a separate failure pattern layer because AI-generated code frequently introduces subtle issues like DRY violations, hallucinated APIs, and unsafe dependencies that standard static analysis and linting often miss.