code-review

Review code paths and PRs with two-phase analysis and structured findings.

Updated Dec 28, 2025
One-click install
npx skills add https://github.com/mcsdodo/kniha-jazd --skill code-review-mcsdodo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/mcsdodo/kniha-jazd/tree/main/.claude/skills/code-review-skill
Command: npx skills add https://github.com/mcsdodo/kniha-jazd --skill code-review-mcsdodo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review processes are time-consuming and error-prone; this Skill provides a structured, repeatable framework to evaluate code quality, correctness, and adherence to best practices.

Core Features & Use Cases

  • Two-phase review: analyze findings and apply approved fixes in a controlled loop.
  • Baseline test execution and status capture to gate quality before merging.
  • Targeted guidance for senior reviewers and clear iterative steps to drive consistent outcomes.

Quick Start

Provide a target and reference to begin a structured code review and generate a _code-review.md with findings.

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 pull requests?

Automate code review for pull requests by using a two-phase workflow that identifies defects, enforces best practices, and generates a structured findings report to ensure quality and maintainability.

What is a structured code review process?

A structured code review process systematically evaluates code quality, correctness, and adherence to best practices across code paths, PRs, and refactors, documenting findings for consistent project improvements.

How do I enforce best practices and document findings during a code review?

Enforce best practices and document findings by running a two-phase review loop that analyzes target and reference inputs, capturing baseline test status and reporting structured outcomes in a _code-review.md file.

Does this code review workflow require specific dependencies or environment setup?

This code review workflow requires no external dependencies, allowing you to provide a target and reference input directly to begin analyzing findings and applying approved fixes in a controlled loop.

What's the best way to gate code quality before merging a pull request?

Gate code quality before merging by capturing baseline test execution status within the review workflow, ensuring that only code meeting project standards and passing tests progresses through the iterative findings loop.

Can I use this to review code refactors and not just new features?

You can use this to review code refactors, as the skill guides reviews across code paths, PRs, and refactoring efforts to ensure quality, correctness, and maintainability throughout the project lifecycle.