archi-diff

Review code changes for architecture risks, coupling, and maintainability issues.

17|2|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/SeemSeam/agent-roles-spec --skill archi-diff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: archi-diff
Source: https://github.com/SeemSeam/agent-roles-spec/tree/main/roles/archi/skills/archi-diff
Command: npx skills add https://github.com/SeemSeam/agent-roles-spec --skill archi-diff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a streamlined review of architecture risk for code changes, helping to identify potential issues before they impact the system.

Core Features & Use Cases

  • Change-Specific Architecture Review: Focuses on architecture risk for specific code changes.
  • Review Workflow Guidance: Offers a step-by-step process to conduct an effective review.
  • Output Verdict: Provides a clear summary of the review outcome, including blocking issues, impacted areas, and required changes.
  • Use Case: Ideal for architects and developers who want to ensure that their code changes do not introduce architecture risks.

Quick Start

Run the archi-diff skill to review the latest changes in your codebase for architecture impact.

Frequently Asked Questions about archi-diff

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

FAQPage Schema
How do I review code changes for architecture risks before merging?▼

To review code changes for architecture risks, run the archi-diff skill to identify boundary pressure, coupling, duplication, and maintainability issues in your latest commits. It provides a step-by-step workflow and outputs a clear verdict on blocking issues and impacted areas.

What is architecture risk assessment in software engineering?▼

Architecture risk assessment is the process of evaluating code changes to identify potential issues like boundary pressure, coupling, and maintainability problems. It ensures long-term system health by catching structural risks before they impact the overall software architecture.

How do I assess coupling and duplication impact from a recent code change?▼

Assess coupling and duplication impact by conducting a change-specific architecture review using the archi-diff skill. It analyzes your code changes and highlights maintainability issues and boundary pressure, providing a summary of required modifications.

Does archi-diff work for large software projects with complex boundaries?▼

Yes, archi-diff is designed for developers and architects working on software projects of varying complexity to ensure long-term architectural health. It specifically evaluates boundary pressure and coupling to manage structural integrity in large systems.

What is the best way to identify boundary pressure in a code change?▼

The best way to identify boundary pressure is to run a targeted architecture review using archi-diff. It evaluates your specific code changes and outputs a clear verdict detailing impacted areas and blocking issues related to boundary constraints.

What limitations should I expect when conducting automated change management reviews?▼

When conducting automated change management reviews with archi-diff, expect that it focuses specifically on architecture risks like coupling and maintainability rather than general code correctness or runtime performance. It provides guidance and a verdict but requires developer interpretation for complex context.