requesting-code-review

Review git diffs for spec compliance and security boundaries.

Updated Jul 4, 2026
One-click install
npx skills add https://github.com/kimen-dev/kimen --skill requesting-code-review-kimen-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/kimen-dev/kimen/tree/main/.agents/skills/requesting-code-review
Command: npx skills add https://github.com/kimen-dev/kimen --skill requesting-code-review-kimen-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the need for independent, high-quality verification of complex or sensitive code changes without the overhead of blocking CI pipelines or multi-pass review cycles.

Core Features & Use Cases

  • Clean-Context Analysis: Evaluates code changes in isolation to ensure objective assessment of spec compliance and security boundaries.
  • Targeted Review: Focuses on high-risk areas such as public API changes, accessibility patterns, and complex logic.
  • Use Case: Use this when submitting a large refactor or a new accessibility interaction pattern to ensure it meets quality standards before final approval.

Quick Start

Provide the git diff and relevant context to the agent to perform a one-pass review of the current changes.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I perform a clean-context code review for a complex pull request?

A clean-context code review evaluates complex pull request changes in isolation to ensure objective assessment of spec compliance and security boundaries. You provide the git diff and relevant context to the agent for a single-pass review.

What is a single-pass code review and when do I need it for security-sensitive changes?

A single-pass code review is an independent verification process for security-sensitive software changes that avoids blocking CI pipelines or multi-pass cycles. It is needed when submitting complex refactors or new public API modifications.

How do I review accessibility patterns and public API modifications in a git diff?

To review accessibility patterns and public API modifications, provide the git diff, test results, and visual evidence to the agent. It performs targeted analysis focusing on these high-risk areas to ensure architectural integrity.

Does this code review process require test results and visual evidence for spec compliance?

Yes, verifying spec compliance requires inputting git diffs, test results, and visual evidence. This ensures the single-pass review accurately validates complex or security-sensitive changes against architectural and quality standards.

What is the best way to verify high-complexity logic without blocking CI pipelines?

The best way to verify high-complexity logic without blocking CI pipelines is using an independent, single-pass code review. This approach assesses spec compliance and security boundaries in isolation without integration overhead.