Skip to content

MVPavan/via / .claude/skills/improve-codebase-architecture

improve-codebase-architecture

Unverified

Find evidence-backed architecture improvements within a named area or requested codebase survey.

Improve Codebase Architecture

Find architectural friction supported by current code, then recommend bounded improvements. A review authorizes inspection and reporting, not refactoring or glossary changes.

Use the named module or pain point. For a broad survey, use recent change history and actual maintenance/test friction to choose areas; expand when evidence warrants. Read relevant domain terms and ADRs. The codebase-design vocabulary helps evaluate interfaces without banning the repository's normal terminology.

For each worthwhile candidate, identify affected files, the concrete friction, a proposed direction, expected benefit, compatibility/migration cost and evidence. Apply the deletion test carefully: does complexity disappear or merely move into callers? Distinguish a supported recommendation from an untested hypothesis.

Present a concise comparison and strongest recommendation. Use an inline visual when it clarifies structure. HTML is optional; HTML-REPORT.md points to the shared artifact guidance. Do not create a report format merely to fill its components.

When an ADR conflicts, explain the new evidence that might justify revisiting it. An interview, alternative-interface exercise or domain-document update happens only when requested or already authorized, using the corresponding shared skill. Do not automatically enter a grilling loop after delivering the review.

receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 318kUpdated Claude CodeCodexUnverifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 318kUpdated Claude CodeCodexUnverifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 318kUpdated Claude CodeCodexUnverifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 318kUpdated Claude CodeCodexUnverifiedInstall