Skip to content

BumpyClock/agent-templates / skills/pstack/how

Explain codebase behavior, ownership, or architecture from source evidence.

How

Answer the codebase question at the level needed for a useful mental model. An explanation or design recommendation is read-only unless the user also requests changes.

Direct answer

Inspect the relevant entry points, contracts, callers, and documented decisions. Trace the path needed to answer the question. Distinguish observed behavior, documented intent, and inferred rationale. State unresolved uncertainty rather than invent a reason.

Return the supported answer and useful source locations. For a decision, give a recommendation and its tradeoffs. A narrow question needs neither a repository map nor a full architecture report.

Complex questions

Use Complex investigation when several independent paths or substantial source context need synthesis. Use Architecture critique for a requested critique or an unresolved design tradeoff. These routes do not require delegation or a separate explanation artifact.

Do not create a prototype, edit source, commit, or open a pull request unless the task authorizes that action.

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