pr-review

Review pull requests and branch diffs against Clean Architecture and dependency rules.

1|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/agnaldo4j/kanban-vision-api-kt --skill pr-review-agnaldo4j
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/agnaldo4j/kanban-vision-api-kt/tree/main/.claude/skills/pr-review
Command: npx skills add https://github.com/agnaldo4j/kanban-vision-api-kt --skill pr-review-agnaldo4j

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill addresses the challenge of maintaining high code quality and architectural integrity by providing a standardized, rigorous harness for reviewing pull requests and branch diffs against project-specific constraints.

Core Features & Use Cases

  • Automated Harness Dispatch: Executes a comprehensive review rubric covering dependency rules, quality guards, and business logic consistency.
  • Contextual Analysis: Evaluates PRs based on the Kanban simulator domain, ensuring changes align with Clean Architecture and Arrow-kt standards.
  • Use Case: Before merging a feature branch, use this skill to perform a deep-dive audit of the implementation, ensuring that all architectural boundaries and quality gates are respected without manual oversight.

Quick Start

Invoke the pr-review skill to analyze the current pull request or branch for compliance with the project harness.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I automate code review for Clean Architecture and dependency rules in a Kotlin pull request?

Automated code review for Clean Architecture in a Kotlin pull request evaluates branch diffs against project-specific dependency rules and quality standards. It dispatches a review rubric to validate architectural boundaries and business logic consistency without manual oversight.

What is a context-aware pull request review and how does it enforce quality gates?

Context-aware pull request review enforces quality gates by analyzing code changes against the specific domain constraints of a project. It ensures implementations respect Definition of Done criteria, architectural boundaries, and business logic consistency before merging.

Can I use an automated review harness to check a Kotlin Kanban simulator branch diff?

Yes, you can use an automated review harness to check a Kotlin Kanban simulator branch diff. The review process is tailored to evaluate changes against the Kanban domain, ensuring compliance with Arrow-kt standards and Clean Architecture dependency rules.

What's the best way to validate Definition of Done compliance before merging a feature branch?

Validating Definition of Done compliance before merging a feature branch is best achieved by running a rigorous peer-review simulation. This audits the implementation against project-specific quality guards, architectural constraints, and business logic consistency.

Does this code review process work without manual peer oversight for branch diffs?

Yes, this code review process works without manual peer oversight by executing a comprehensive review rubric. It performs a deep-dive audit of branch diffs to ensure all architectural boundaries and quality gates are respected automatically.