architecture-audit

Automate nightly TypeScript architecture audits that route discrete findings to PRs or issues.

515|64|Updated Oct 23, 2024

Search Tags:#typescript #architecture #refactor #code-quality #static-analysis #code-debt #nightly

Ready to run

npx skills add https://github.com/allenhutchison/obsidian-gemini --skill architecture-audit-allenhutchison

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-audit
Source: https://github.com/allenhutchison/obsidian-gemini/tree/main/.agents/skills/architecture-audit
Command: npx skills add https://github.com/allenhutchison/obsidian-gemini --skill architecture-audit-allenhutchison

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill performs a nightly architecture audit of a TypeScript codebase to surface architectural smells, like oversized files, DRY violations, dead code, missing tests, and weak typings, and to propose discrete units of work.

Core Features & Use Cases

Scans TypeScript source to detect structural issues and code smells.
Categorizes each finding into a single, actionable unit of work and routes it as a focused PR or an issue.
Generates human-reviewable artifacts (PRs and issues) with clear scope, risk, and rationale for each finding.

Quick Start

Run the architecture-audit nightly sweep to surface discrete architecture findings and open focused PRs or issues.

Frequently Asked Questions about architecture-audit

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

FAQPage Schema

How do I automate nightly tech debt audits for a TypeScript codebase?▼

Nightly tech debt audits are automated by scheduling a sweep of your TypeScript codebase to surface architectural smells and route discrete units of work as focused PRs or issues.

What architectural smells can static analysis detect in a large TypeScript repository?▼

Static analysis can detect architectural smells in a large TypeScript repository including oversized files, DRY violations, dead code, missing tests, and weak typings.

How do I route code quality findings into discrete pull requests or issues?▼

Code quality findings are routed into discrete pull requests or issues by categorizing each architectural smell into a single, actionable unit of work with bounded scope and clear justification.

Can I schedule nightly refactoring tasks for large TypeScript repositories?▼

Yes, nightly refactoring tasks are designed for large TypeScript repositories, running scheduled sweeps that ensure mechanically safe changes and per-finding routing.

What is the best way to track and resolve DRY violations and dead code in TypeScript?▼

The best way to track DRY violations and dead code is running a nightly architecture audit that generates human-reviewable artifacts with clear scope, risk, and rationale for each finding.