← ClaudeAtlas

codebase-improvementlisted

Audit, diagnose, plan, and improve software codebases through repository reconnaissance, evidence-backed findings, competing-hypothesis investigation, leverage-based prioritization, executable plans, backlog reconciliation, and proportionate simplification. Use when asked why a defect or surprising behavior occurs, for a read-only root-cause report, to audit a repository, decide what to improve next, simplify code, create or review an implementation plan, reconcile stale work, or implement selected improvements. Do not use for PR-only review, dependency-update-only work, focused test, test-runner, or test-framework diagnosis, architecture-only decisions, or frontend-only diagnosis when a narrower skill applies.
sebastian-software/skills.sebastian-software.com · ★ 0 · AI & Automation · score 70
Install: claude install-skill sebastian-software/skills.sebastian-software.com
# Codebase Improvement Understand the repository before judging it. Produce fewer, better-supported findings and make the next action executable without inventing a private project management system. ## Choose the Operating Mode Match actions to the user's authority: - **Audit or report:** inspect read-only and return vetted findings. Do not edit source, publish issues, or create plan files unless asked. - **Focused audit:** inspect only the named category, package, flow, or branch delta plus the directly affected callers and contracts. - **Investigate or diagnose:** reproduce or trace one symptom, test competing explanations, and return the best-supported cause or uncertainty plus exactly one next action. This mode is read-only: do not implement a fix, add a test, edit configuration, publish an issue, or change project state without a separate user authorization. - **Plan:** investigate enough to make one requested change executable. Return the plan in the response unless the user asks to save it. - **Review plan:** test an existing plan against current code, repository conventions, decision records, scope, and verification reality. - **Reconcile:** verify whether recorded work is done, stale, blocked, superseded, duplicated, or no longer valuable. - **Improve or implement:** when the user explicitly asks for changes, select and implement the agreed scope, then verify it. Planning is a means, not a reason to refuse authorized implementation. ## Wor