skills.rest
loonghao
loonghaoCOMMUNITY
Explore all skills by this author →
GitHub

architecture-diagnosis

Generate architecture diagnosis reports with subsystem boundaries and refactor roadmaps.

44|6|Updated Oct 27, 2025
Search Tags:#architecture#code review#refactoring#design patterns#diagnosis#risk assessment
One-click install
npx skills add https://github.com/loonghao/auroraview --skill architecture-diagnosis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-diagnosis
Source: https://github.com/loonghao/auroraview/tree/main/.codebuddy/skills/architecture-diagnosis
Command: npx skills add https://github.com/loonghao/auroraview --skill architecture-diagnosis

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill provides a comprehensive architecture diagnosis report for a codebase, identifying design flaws, assessing risks, and proposing actionable refactoring roadmaps.

Core Features & Use Cases

  • Architecture Assessment: Maps subsystem boundaries and identifies design flaws with concrete evidence.
  • Risk Analysis: Assesses risks associated with identified flaws and proposes phased refactoring plans.
  • Use Case: When a team needs a clear "diagnosis report" to make informed decisions about refactoring, understand system risks, or plan for future extensions, this skill provides the necessary insights.

Quick Start

Generate an architecture diagnosis report for the current repository, focusing on potential threading and event loop issues.

Frequently Asked Questions about architecture-diagnosis

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

FAQPage Schema
How do I diagnose architectural flaws and design smells in my codebase?▼

Architecture diagnosis identifies design flaws by mapping subsystem boundaries and detecting architectural smells with concrete evidence. It produces an actionable report assessing structural risks and code maintainability issues.

How do I create a refactoring roadmap for a complex software architecture?▼

Creating a refactoring roadmap involves assessing risks of identified architectural flaws and proposing a phased refactor plan. This breaks down complex codebase improvements into manageable, prioritized stages for structural maintenance.

Can I assess code structure risks before planning a major refactoring?▼

Yes, you can assess code structure risks before refactoring by scanning the repository to map subsystem boundaries and evaluate design flaws. This risk analysis highlights critical areas to inform maintenance decisions.

What is the best way to identify subsystem boundaries in a software repository?▼

The best way to identify subsystem boundaries is through an architecture diagnosis that scans the repository and maps structural divisions. This process exposes design flaws and provides concrete evidence for structural improvements.

Do I need any external dependencies to run an architecture diagnosis on my repository?▼

No external dependencies are required to run an architecture diagnosis on your repository. The skill operates independently using internal scripts and references to scan the codebase and produce actionable reports.

Related Skills

Explore More Software Engineering Skills→
Andreicr1Andreicr1

repo-research-analyst

Analyze repository structure, documentation, conventions, and implementation patterns.

Community
Advanced
zm2231zm2231

code-refactoring

Refactor code to improve quality, readability, and maintainability.

Community
Advanced
MadAppGangMadAppGang
7

audit

Audit codebases for security vulnerabilities, code smells, and compliance issues.

Official
Advanced
actionbookactionbook
1.4k

m15-anti-pattern

Identify and remediate Rust anti-patterns in code reviews.

Official
Basic