code-review

Fetch unresolved PR comments and apply categorized changes with DDD standards.

5|Updated May 30, 2023
One-click install
npx skills add https://github.com/VilnaCRM-Org/core-service --skill code-review-vilnacrm-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/VilnaCRM-Org/core-service/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/VilnaCRM-Org/core-service --skill code-review-vilnacrm-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Addressing PR review comments can be error-prone and time-consuming; this skill provides a structured, repeatable workflow to systematically retrieve, categorize, and implement reviewer feedback while enforcing DDD architecture and code-organization standards.

Core Features & Use Cases

  • Retrieve unresolved PR comments using make pr-comments and correlate them to specific files and lines.
  • Categorize feedback (architecture concerns, naming, validation) and apply changes in a consistent, auditable manner.
  • Ensure changes align with DDD patterns and coding standards across the codebase, with traceable commits. Use cases include handling reviewer feedback on PRs, guiding refactors based on comments, and maintaining architectural integrity during reviews.

Quick Start

Run make pr-comments to fetch unresolved PR comments and begin the structured review workflow.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I systematically address unresolved PR comments in a code review workflow?

To address unresolved PR comments systematically, retrieve review feedback using make pr-comments, categorize the feedback into architecture or naming concerns, and apply changes in a controlled, auditable manner to ensure traceable commits.

How does an automated code review enforce DDD architecture and quality standards?

Automated code review enforces DDD architecture by categorizing reviewer feedback, checking changes against domain-driven design patterns, and applying code-organization rules consistently across the codebase during refactoring efforts.

What is the best way to automate the retrieval of unresolved PR comments for refactoring?

The best way to automate retrieving unresolved PR comments is running make pr-comments, which fetches reviewer feedback and correlates it to specific files and lines to guide refactoring efforts based on the provided feedback.

Do I need specific dependencies to apply code review feedback while maintaining architectural integrity?

No specific dependencies are required to apply code review feedback while maintaining architectural integrity, as the workflow systematically categorizes feedback and enforces DDD patterns directly within your existing Git branches.

Can I categorize PR review feedback into architecture concerns and naming validation automatically?

Yes, you can automatically categorize PR review feedback into architecture concerns and naming validation by running the structured workflow, which systematically groups reviewer comments before applying changes.

When should I not use an automated workflow for handling PR review comments?

You should not use an automated workflow for handling PR review comments when changes require subjective architectural decisions outside standard DDD patterns, as the workflow focuses on systematic categorization and enforcing code-organization rules.