architecture-audit

Audit Umbraco and .NET codebases against seven architectural pillars and generate prioritized markdown reports.

Updated May 26, 2026
One-click install
npx skills add https://github.com/robot-denny/ai-sketchlab --skill architecture-audit-robot-denny
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-audit
Source: https://github.com/robot-denny/ai-sketchlab/tree/main/.agents/skills/architecture-audit
Command: npx skills add https://github.com/robot-denny/ai-sketchlab --skill architecture-audit-robot-denny

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Evaluating the structural quality of an Umbraco/.NET codebase is subjective and time-consuming, especially when inheriting an unfamiliar project or deciding whether the architecture supports a future headless move. This Skill produces an evidence-cited written audit with scores, strengths, weaknesses, and prioritized P0/P1/P2 recommendations tailored to the codebase's lifecycle stage. ## Core Features & Use Cases - Seven-pillar assessment: Scores modern .NET hygiene, architectural separation, Umbraco-version-appropriate patterns, headless suitability, documentation and onboarding, resilience and operations, and scalability on a calibrated 1-5 rubric. - Lifecycle-aware recommendations: Detects whether the codebase is greenfield, growing, mature, or brownfield and gates recommendations accordingly, so greenfield projects get ambitious foundational advice while mature ones get small high-leverage fixes. - Head-to-head comparison: Optionally audits a second repository and merges both reports into a side-by-side comparison with per-pillar winners. - Use Case: You just inherited an Umbraco site from a departing developer. Run the audit to get a brownfield map of what lives where, risk-prioritized findings, and a report you can share with your team. ## Quick Start Ask the assistant to review the architecture of this codebase and produce a written audit with prioritized recommendations.

Frequently Asked Questions about architecture-audit

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

FAQPage Schema
How do I audit the architecture of an Umbraco codebase?

Run the architecture-audit skill against the repository root. It detects the Umbraco version and lifecycle stage, collects structural signals, scores seven pillars on a 1-5 rubric, and writes a markdown report with prioritized P0/P1/P2 recommendations to the _audits folder.

How do I compare two Umbraco repositories architecturally?

Pass a second repository path using the --compare argument. The skill audits both targets independently, then merges the results into a head-to-head section with side-by-side pillar scores and per-pillar pros and cons.

Does the architecture audit work on non-Umbraco .NET projects?

Yes, with reduced scope. If no Umbraco package is detected, the skill confirms intent with the user and falls back to generic .NET conventions for the Umbraco-specific pillar. It does not run on non-.NET codebases at all.

Can the audit tell if my site is ready to go headless?

Yes. Pillar 4 classifies the current orientation as traditional, hybrid, or headless, rates migration readiness, and estimates the effort for content access refactoring, business logic extraction, and frontend work.

When should I not use an architecture audit skill?

Skip it for line-level code review of a diff or pull request, for quick informal gut checks, and for non-.NET codebases. The skill produces a full written report, which is too heavy for casual questions.

Does the architecture audit modify my codebase?

No. The skill is strictly read-only against the target repository. Its only write operation is saving the generated markdown report into an _audits directory, and it never overwrites an existing report file.