issue-review-code

Enforce design-consistent code reviews with lint, mypy, and pytest validation.

12|1|Updated Dec 27, 2025
One-click install
npx skills add https://github.com/apokamo/kaji --skill issue-review-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-review-code
Source: https://github.com/apokamo/kaji/tree/main/.claude/skills/issue-review-code
Command: npx skills add https://github.com/apokamo/kaji --skill issue-review-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates a rigorous post-implementation review process to verify that produced artifacts align with design specifications and quality standards.

Core Features & Use Cases

  • Enforces design-consistent interfaces and robust code quality after implementation.
  • Guides independent verification workflows, including baseline checks, lint/format/mypy runs, and pytest validation.
  • Supports audit trails and compliance with the i-dev-final-check workflow in kaji.

Quick Start

Run a post-implementation review for a completed feature to verify design integrity and run lint, mypy, and pytest checks.

Frequently Asked Questions about issue-review-code

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

FAQPage Schema
How do I automate post-implementation code review with lint, mypy, and pytest checks?

Run a post-implementation review workflow that enforces design consistency and quality by applying baseline checks, lint/format/mypy runs, and pytest validation. This process verifies that produced artifacts align with design specifications and quality standards.

What is a baseline check in post-implementation code review?

A baseline check in post-implementation code review is an independent verification step that validates code quality before running lint, mypy, and pytest checks. It ensures the code meets fundamental design requirements before deeper validation.

How do I verify code traceability to original design documents after implementation?

Verify code traceability by applying a rigorous post-implementation review workflow that checks design-consistent interfaces and enforces quality standards. This process ensures the implementation maps directly back to original design documents through independent testing and hard gates.

Can I use independent testing and hard gates in my code review workflow?

Yes, you can guide independent verification workflows that include baseline checks, lint/format/mypy runs, and pytest validation with hard gates. This enforces robust code quality and design consistency after implementation completion.

What is the best way to enforce quality gates across implement, review, and fix workflows?

The best way is applying an end-to-end review workflow across implement, review-code, fix-code, and verify-code stages with independent testing and hard gates. This enforces design-consistent interfaces and robust code quality throughout the entire process.

Why does my post-implementation review fail to catch design inconsistencies?

Post-implementation review may miss design inconsistencies if it lacks independent testing, hard gates, and traceability checks to original design documents. Enforcing lint/format/mypy checks and pytest validation ensures artifacts align with design specifications.