architectural-decisions
The architectural-decisions Claude Code skill queries a Repowise-indexed repository to retrieve documented rationale behind code design choices, implementation approaches, and structural decisions. Use this skill when addressing questions about why code exists in its current form, evaluating proposed architectural changes, comparing different implementation strategies, or when code contains decision markers like WHY, DECISION, TRADEOFF, or ADR that require explanation.
git clone --depth 1 https://github.com/repowise-dev/repowise /tmp/architectural-decisions && cp -r /tmp/architectural-decisions/plugins/codex/skills/architectural-decisions ~/.claude/skills/architectural-decisionsSKILL.md
# Architectural Decisions With Repowise Repowise captures architectural decisions: the rationale behind how code is built. ## When The User Asks Why Something Exists Call `get_why(query="specific area or decision")` to search captured decisions. This covers inline decision markers, git-derived rationale, and decisions mined from documentation. ## Before Architectural Changes 1. Call `get_why(query="the area being changed")` before introducing new patterns, restructuring modules, replacing infrastructure, or choosing between approaches. 2. If decisions are found, summarize the relevant rationale and tradeoffs before editing. 3. If no decision is found, state that no recorded decision governs the area and continue with normal source inspection. ## When No Specific Query Exists Call `get_why()` to inspect decision health: stale decisions, conflicts, and ungoverned hotspots. ## When Decision Markers Appear In Code If a file contains `WHY:`, `DECISION:`, `TRADEOFF:`, or `ADR:`, call `get_context(targets=["path/to/file"])` to retrieve the full file context and related decisions. ## Recording New Decisions When the user makes a new architectural decision, suggest recording it with a `DECISION:` comment in the relevant code or with `repowise decision add`.
>
>
Use when exploring, understanding, or answering questions about a Repowise-indexed codebase, including architecture, where code is implemented, how a module works, or which files are relevant before reading source.
Use when the user asks about unused code, cleanup, deleting files or exports, refactoring old areas, reducing bundle size, code hygiene, technical debt, or maintenance in a Repowise-indexed repository.
Use before modifying, refactoring, moving, or deleting files in a Repowise-indexed repository, especially shared utilities, core modules, public APIs, or files the user did not explicitly identify.