Verified:GitHub

sdcorejs-review-architecture

Audit codebase architecture for layering violations and circular dependencies.

2|Updated Apr 18, 2026

Search Tags:#architecture review #module boundaries #code structure #circular dependency #layering #convention drift #abstraction leak

Ready to run

npx skills add https://github.com/sdcorejs/sdcorejs-agent --skill sdcorejs-review-architecture

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdcorejs-review-architecture
Source: https://github.com/sdcorejs/sdcorejs-agent/tree/main/plugin/skills/sdcorejs-review-architecture
Command: npx skills add https://github.com/sdcorejs/sdcorejs-agent --skill sdcorejs-review-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevent structural code quality problems that line-by-line review misses, such as layering violations, abstraction leaks, circular dependencies, boundary breaches, and architectural drift from SDCoreJS conventions.

Core Features & Use Cases

Cross-track architecture checklist: audits a feature/module for structural issues like wrong layering, circular dependencies, and missing module boundaries.
Convention and test placement review: checks drift against documented conventions and evaluates whether tests live at the right architectural layer.
Severity-based actionable reporting: produces Critical/Important/Minor findings with file:line citations and a fix path that routes Critical to repair-loop.

Quick Start

Run the architecture audit for a module by saying: "review kiến trúc for this feature before merge".

Frequently Asked Questions about sdcorejs-review-architecture

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

FAQPage Schema

How do I detect architecture drift and layering violations in a codebase?▼

Run a cross-track architecture review checklist to detect layering violations, boundary breaches, and convention drift. It outputs Critical, Important, and Minor findings with file:line citations to pinpoint structural issues missed by per-file review.

Why does per-file code review pass but the module architecture still seems wrong?▼

Per-file review misses structural problems like circular dependencies, abstraction leaks, and missing module boundaries. A cross-track architecture audit checks for these systemic issues to ensure overall code organization aligns with conventions.

What is the best way to audit code structure for circular dependencies before a major merge?▼

Use a cross-track architecture checklist to audit code structure for circular dependencies before major merges. It evaluates test placement and routes Critical findings with file:line citations toward an orchestration repair-loop for remediation.

How do I check for abstraction leaks and convention drift after a codebase refactor?▼

Apply an architecture review checklist after refactoring to check for abstraction leaks and convention drift. It evaluates the codebase against documented conventions and outputs actionable severity findings with specific file:line citations.

Can I use an architecture audit to review test placement and module boundaries?▼

Yes, an architecture audit can review test placement and module boundaries. The checklist evaluates whether tests live at the correct architectural layer and detects missing boundaries, reporting issues with severity levels and file:line citations.