code-complexity-audit

Audit repository design quality across 13 dimensions and output a Design Health Report.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nkootstra/skills --skill code-complexity-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-complexity-audit
Source: https://github.com/nkootstra/skills/tree/main/skills/code-complexity-audit
Command: npx skills add https://github.com/nkootstra/skills --skill code-complexity-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams identify design quality issues and surface hotspots in a codebase, enabling targeted improvements to architecture and maintainability.

Core Features & Use Cases

  • Deep, multi-dimension analysis aligned with John Ousterhout's design principles, producing a Design Health Report with severity-classified findings.
  • Git-attribution of findings to identify authors and ownership, with a clear path for remediation.
  • Adaptive auditing that scales from small projects to large codebases, prioritizing core modules and high-risk areas.

Quick Start

Run the audit on your repository to generate a Design Health Report.

Frequently Asked Questions about code-complexity-audit

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

FAQPage Schema
How do I audit code design quality and identify architectural hotspots?

To audit code design quality, you run an analysis across your repository to surface architectural hotspots and debt. This process evaluates 13 dimensions across core design, structural, and surface areas to produce a Design Health Report.

What is git-informed sampling when running a code health check?

Git-informed sampling is a mechanism that uses repository history to select files for a code health check. It prioritizes core modules and high-risk areas to ensure the architecture assessment scales efficiently across large codebases.

Can I perform an architecture assessment across different programming languages?

Yes, you can perform an architecture assessment across various languages and project sizes. The audit applies to code reviews and health checks universally, evaluating design quality dimensions without being limited to a specific platform.

How do I attribute technical debt findings to specific authors in a repository?

You can attribute technical debt findings to specific authors using git attribution during the design quality audit. This feature identifies file ownership and provides a clear path for remediation of the severity-labeled findings.

What is the best way to evaluate core design principles during a code review?

The best way to evaluate core design principles is to apply a multi-dimension analysis aligned with John Ousterhout's design principles. This method classifies findings by severity to help teams target improvements to architecture and maintainability.