architecture-reviewer

Review changed files or modules against repository engineering principles and rubric.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/h-4vok/diagram-tours --skill architecture-reviewer-h-4vok
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-reviewer
Source: https://github.com/h-4vok/diagram-tours/tree/main/.agents/skills/architecture-reviewer
Command: npx skills add https://github.com/h-4vok/diagram-tours --skill architecture-reviewer-h-4vok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review changed files or a named module against the repository's engineering principles and review rubric, then return findings and a verdict.

Core Features & Use Cases

  • Applies to change reviews and module reviews, evaluating the current diff or a named module, and providing targeted findings within the defined scope.
  • Adheres to the repository's principles and rubric to ensure cohesive, well-scoped reviews and clear naming.

Quick Start

Review the current diff or a named module to generate a formal architecture assessment and findings.

Frequently Asked Questions about architecture-reviewer

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

FAQPage Schema
How do I automate architecture review for code changes and diffs?

Automate architecture review by analyzing the current diff against the repository's engineering principles and review rubric, returning targeted findings and a clear verdict within the defined scope.

What is a module review against engineering principles?

A module review evaluates a named area or touched files against repository engineering principles and a review rubric, providing a formal architecture assessment with explicit criteria and actionable notes.

Can I review just the touched files instead of the entire repository?

Yes, you can apply the review to the current diff, touched files, or a named module to receive a focused architecture assessment with actionable notes and a verdict.

Does the architecture review output include a formal pass or fail decision?

Yes, the architecture review protocol ensures the output includes a clear Verdict alongside explicit criteria, boundaries, and findings based on the repository's rubric.

What's the best way to ensure code reviews follow repository engineering principles?

The best way is applying an automated diff analysis that evaluates changed files against the repository's engineering principles and review rubric, ensuring cohesive and well-scoped assessments.

When do I need a formal architecture assessment for my pull request?

You need a formal architecture assessment when you want to evaluate code changes against engineering principles, ensuring the diff adheres to boundaries and clear naming conventions before merging.