architect

Evaluates code diffs for architecture regressions, duplication, and maintainability risks pre-merge.

2|2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/mathiasbourgoin/roster --skill architect-mathiasbourgoin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/mathiasbourgoin/roster/tree/main/.agents/skills/architect
Command: npx skills add https://github.com/mathiasbourgoin/roster --skill architect-mathiasbourgoin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Undetected structural code issues, duplication, and architecture drift often lead to costly technical debt and rework when caught late in the development cycle, after code has already been merged.

Core Features & Use Cases

  • Pre-merge architecture review: Automatically scans code changes for excessive file/function size, deep nesting, cross-module coupling, and duplication hotspots against project architecture constraints.
  • Spec-aligned validation: Checks implementation against feature spec acceptance criteria and entity definitions, flagging spec deviations as critical issues to prevent misalignment.
  • Severity-classified findings: Delivers actionable, prioritized remediation guidance (critical/warning/optional) for tech leads to make informed merge decisions and reduce post-release technical debt.
  • Use case: For a team shipping a new user authentication feature, this skill reviews the PR diff against the project's architecture rules and the feature's spec to surface high-risk design issues like cross-module coupling before merge, avoiding expensive refactors post-release.

Quick Start

Use the architect skill to review the current feature branch diff against your project's architecture constraints and associated feature spec to get a prioritized list of architecture risks and concrete remediation steps.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I check code changes for structural architecture regressions before merging?

Pre-merge architecture review scans code changes for excessive file size, deep nesting, cross-module coupling, and duplication hotspots against project constraints to catch structural regressions early. It classifies findings by severity to help tech leads make informed merge decisions.

What is architecture drift and how does it create technical debt?

Architecture drift occurs when code changes introduce structural regressions like cross-module coupling or duplication that deviate from project guardrails. Detecting these issues late in the development cycle after merging leads to costly rework and accumulated technical debt.

How do I validate implementation against feature spec acceptance criteria?

Spec-aligned validation checks implementation against feature spec acceptance criteria and entity definitions during pre-merge review. It flags spec deviations as critical issues to prevent misalignment between the merged code and documented requirements.

Can I use pre-merge validation to enforce architecture guardrails on pull request diffs?

Pre-merge validation evaluates pull request diffs against configured project architecture constraints and thresholds. It applies deterministic, objective architecture quality checks to respect configured thresholds for file size, nesting depth, and module coupling.

How are structural code issues prioritized for remediation guidance?

Structural code issues are classified by severity as critical, warning, or optional to deliver actionable and prioritized remediation guidance. This severity classification informs merge decisions and helps reduce post-release technical debt.

What are the limitations of automated architecture review for code duplication detection?

Automated architecture review focuses on structural regressions, duplication hotspots, and spec compliance but relies on configured thresholds and documented acceptance criteria. It does not replace manual review for subjective design decisions outside of defined architecture constraints.