Audit TypeScript codebases for architecture and code-quality issues.
npx skills add https://github.com/maxbeaudoin/productflash --skill arch-review-maxbeaudoin
Please help me install this Agent Skill. Skill: arch-review Source: https://github.com/maxbeaudoin/productflash/tree/main/.claude/skills/arch-review Command: npx skills add https://github.com/maxbeaudoin/productflash --skill arch-review-maxbeaudoin
It helps you identify architecture and code-quality risks in a TypeScript web/SaaS codebase using evidence-based, read-only findings, so you can reduce change pain and onboarding cost without “magic” or code modifications.
file:line excerpts plus remediation guidance.Ask the AI to run an architecture audit on your repository and produce one ranked report with concrete file-and-line evidence and remediation steps.
High-intent search queries and answers about installing and using this skill.
An architecture audit identifies structural risks by checking module boundaries, coupling, and cohesion in TypeScript code. It outputs ranked findings with severity, file:line evidence, and remediation guidance to reduce change pain and onboarding cost.
The best way to check for SOLID, DRY, and KISS violations is an evidence-first code-quality audit. It evaluates your TypeScript project against these heuristics, providing ranked reports with specific file and line excerpts for concrete remediation.
You can audit client-server boundaries and type-safety hygiene by running a maintainability review on your TypeScript web codebase. This read-only process checks API consistency, isomorphism separation, and error-handling patterns, generating evidence-backed findings.
An architecture review does not modify your code; it is a strictly read-only audit. It analyzes your TypeScript files to identify quality risks and structural issues, outputting a ranked report with remediation steps without making any code changes.
Yes, you can validate project conventions during a code audit. The review re-checks stated rules found in repo docs like CLAUDE.md or ADRs, upgrading findings to Violations when explicit invariants are broken, alongside general code-quality smells.
A limitation of this read-only audit is that it focuses on static structure and maintainability, not runtime behavior. It explicitly notes when runtime verification is needed for error-handling patterns and API consistency, as it does not execute code.
cacackDetect documentation drift between project docs and repository code.
molacoAudit Rust module imports, exports, and re-exports for visibility discipline.
Junior-Frontend-devEnforce SOLID, DRY, and KISS principles with pre-commit lint and type checks.
yanochka11Review code changes for bugs, security issues, and maintainability risks.