lens-architecture

Review codebase architecture and uncommitted changes for architectural soundness.

Updated Aug 26, 2025
One-click install
npx skills add https://github.com/ThonkTank/Salt-Marcher --skill lens-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lens-architecture
Source: https://github.com/ThonkTank/Salt-Marcher/tree/main/tools/quality/skills/lens-architecture
Command: npx skills add https://github.com/ThonkTank/Salt-Marcher --skill lens-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the review of codebase architecture and uncommitted changes for architectural soundness, focusing on separation of concerns, dependency direction, quality attributes, data architecture, and structural risks.

Core Features & Use Cases

  • Automated Architecture Review: Reviews codebase architecture or uncommitted changes for architectural soundness.
  • Specialist Lens Contract: Adds specialist criteria, labels, verdicts, and report sections for architectural review.
  • Code Evaluation: Evaluates code for long-term impact on system evolvability, maintainability, and operational reliability.
  • Review Modes: Offers Fit Review and Architecture Question Review modes to assess architectural impact.
  • Triage: Identifies high, low, or drift-relevant architectural significance of changes.
  • Structural State Ownership Matrix: Provides a matrix to classify architecture findings by their significance and impact.
  • Quality Attributes: Focuses on resilience, scalability, performance, observability, deployability, security, and testability.
  • Distributed Patterns: Evaluates asynchronous and distributed patterns in the codebase.
  • Architectural Risk Assessment: Assesses risks associated with architectural decisions.

Quick Start

Run the lens-architecture skill on your codebase to automate architectural code reviews and ensure the long-term health of your system.

Frequently Asked Questions about lens-architecture

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

FAQPage Schema
How do I automate an architectural code review for my codebase?

An architectural code review evaluates your codebase or uncommitted changes for separation of concerns, dependency direction, and structural risks. It assesses system evolvability, maintainability, and operational reliability to ensure long-term health.

What is architectural triage and how does it classify code changes?

Architectural triage identifies the architectural significance of code changes by classifying them as high, low, or drift-relevant. This classification helps determine the impact of modifications on the overall system structure and guides review focus.

Can I assess distributed patterns and quality attributes during a code review?

Yes, you can assess distributed patterns and quality attributes during a code review. This involves evaluating asynchronous patterns for resilience, scalability, performance, observability, deployability, security, and testability within the codebase architecture.

Do I need prior architectural knowledge to review code for system evolvability?

Yes, reviewing code for system evolvability requires prior architectural knowledge and an understanding of codebases. This expertise is necessary to effectively evaluate separation of concerns, data architecture, and structural risks.

What is the best way to evaluate architectural risk in uncommitted changes?

The best way to evaluate architectural risk in uncommitted changes is to use review modes like Fit Review and Architecture Question Review. These modes assess the long-term impact of modifications on system maintainability and operational reliability.

How does a structural state ownership matrix help with code maintainability?

A structural state ownership matrix helps with code maintainability by classifying architecture findings according to their significance and impact. This classification identifies high, low, or drift-relevant architectural issues that affect system evolvability.