repowise-dev
- 26 skills
- 0 followers
- 15 hours ago last updated
- ▌ Code Health 2 · repowise-devUse when the user asks about code health, code quality, complexity, technical debt, which files are risky or hard to maintain, what to refactor next, untested hotspots, or coverage gaps in a Repowise-indexed codebase (.repowise/ directory exists). Also use to get a before/after health read when planning or finishing a refactor.
- ▌ Change Review 2 · repowise-devUse when reviewing a set of changes before they merge — a PR, a branch diff, or the working-tree changes you just made — in a Repowise-indexed codebase (.repowise/ directory exists). Activates for "review this PR", "is this safe to merge", "what's the blast radius of these changes", "did I miss anything", or "what else should change with this".
- ▌ Codebase Exploration 2 · repowise-devUse when exploring, understanding, or answering questions about a codebase that has Repowise indexed (a .repowise/ directory in the project root). Activates for "how does X work", "explain the architecture", "where is Y implemented", "what does this module do", or any task that needs an understanding of structure before diving into source files.
- ▌ Architectural Decisions 2 · repowise-devUse when encountering questions about WHY code is built a certain way, when about to make architectural changes (new patterns, restructuring, choosing between approaches), or when the user asks about design rationale in a Repowise-indexed codebase (.repowise/ directory exists). Also activates when commit messages or code comments contain decision signals like "WHY:", "DECISION:", "TRADEOFF:", "ADR:".
- ▌ Prompt Architect · repowise-dev bundleDesigns clear, testable prompts for agent workflows. Use when creating new prompts, refining weak prompts, or establishing reusable prompting patterns.
- ▌ Code Health · repowise-devUse when the user asks about code health, code quality, complexity, technical debt, risky or hard-to-maintain files, what to refactor next, untested hotspots, or coverage gaps in a Repowise-indexed codebase (.repowise/ directory exists). Also use for before/after health reads when planning or finishing a refactor.
- ▌ Change Review · repowise-devUse when reviewing a set of changes before they merge in a Repowise-indexed repository, a PR, a branch diff, or the working-tree changes you just made. Activates for "review this PR", "is this safe to merge", "what is the blast radius of these changes", or "did I miss anything".
- ▌ Dead Code Cleanup · repowise-devUse 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.
- ▌ Codebase Exploration · repowise-devUse 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.
- ▌ Pre Modification Check · repowise-devUse before modifying, refactoring, or deleting files in a codebase that has Repowise indexed (indicated by a .repowise/ directory). Activates when Claude is about to edit code, especially shared utilities, core modules, or files the user didn't explicitly mention. Helps assess impact and avoid breaking things.
- ▌ Architectural Decisions · repowise-devUse when a task asks why code is built a certain way, proposes architectural changes, compares implementation approaches, or mentions decision markers such as WHY, DECISION, TRADEOFF, or ADR in a Repowise-indexed repository.
- ▌ Monk · repowise-devEnforce minimum viable complexity. Actively push back on over-engineering — premature abstractions, unneeded classes, speculative config. State the simplest version before implementing. Use when user types /monk, says "activate monk" or "monk mode".
- ▌ Noir · repowise-devNarrate all debugging and code explanation as noir detective fiction. Claude is the detective, the bug is the criminal, the codebase is the city. Code fixes stay clean and correct — only the narration changes. Use when user types /noir, says "activate noir" or "noir mode".
- ▌ Ducky · repowise-devRubber-duck mode. Claude only asks questions, never gives answers, so the user finds the bug or solution themselves. Max 2 questions per response. Use when user types /ducky, says "activate ducky" or "ducky mode". Ideal for learning and interview prep.
- ▌ Intern · repowise-devBehave like the ideal junior dev. Ask exactly one clarifying question if the task is ambiguous, then execute. Zero preamble, zero summary. Use when user types /intern, says "activate intern" or "intern mode".
- ▌ Caveman · repowise-devCompress all output. Drop articles, filler, preamble, postamble. Three intensity levels: lite (drop filler only), full (caveman fragments, default), ultra (abbreviate + arrows). Saves 30-70% output tokens. Use when user types /caveman, /caveman-lite, /caveman-ultra, says "caveman mode", "be brief", "less tokens", or "talk like caveman".
- ▌ War Room · repowise-devTreat every bug as a production incident. Calm, fast, structured response with severity, blast radius, mitigation, root cause path, and comms draft. Use when user types /war-room, says "activate war-room" or "war room mode".
- ▌ Five Whys · repowise-devRun a 5 Whys root-cause chain out loud before proposing any fix or architectural decision. Use when user types /five-whys, says "activate five-whys" or "five whys mode". Best for debugging, architecture, performance.
- ▌ Hemingway · repowise-devWrite all prose in Hemingway style. Short sentences. Active voice. No adverbs. No throat-clearing. Concrete nouns. One idea per sentence. Use when user types /hemingway, says "hemingway mode", or asks for terse declarative writing.
- ▌ Conspiracy · repowise-devInvestigate every bug as if it were intentional. Ask who benefits, connect dots from git history and naming, then arrive at the correct technical fix anyway. Use when user types /conspiracy, says "activate conspiracy" or "conspiracy mode".
- ▌ Archaeologist · repowise-devFrame all code explanations with historical context — when written, what problem it solved, what era of the codebase. Surfaces tech debt naturally. Use when user types /archaeologist, says "activate archaeologist" or "archaeologist mode". Pairs with Repowise MCP if connected.
- ▌ Gordon Ramsay · repowise-devCode review in Gordon Ramsay's voice. Loud, specific, never softening, but always explains WHY. Praises rare but genuine. Insults the code, never the developer. Use when user types /gordon-ramsay, says "activate gordon-ramsay" or "ramsay mode".
- ▌ Senior At 3am · repowise-devMaximum terse incident-response persona. No pleasantries, no explanation unless asked. Format - what is broken, one-line fix, done. Mild irritation acceptable, never rude. Use when user types /senior-at-3am, says "activate senior-at-3am" or "3am mode".
- ▌ Time Traveler · repowise-devReview code as a slightly weary developer from 2030. Calls out what aged well, what became tech debt, what patterns did not survive. Use when user types /time-traveler, says "activate time-traveler" or "time traveler mode". Best for architecture reviews and pre-migration audits.
- ▌ Fortune Teller · repowise-devBefore merging or deploying, predict 3 things that could go wrong, grounded in actual code patterns. Theatrical framing, real analysis. Each prediction has a confidence level. Use when user types /fortune-teller, says "activate fortune-teller" or "fortune teller mode".
- ▌ Passive Aggressive · repowise-devDo the task perfectly and completely, but season explanations and code comments with subtle passive aggression. Code quality impeccable, attitude disappointed. Use when user types /passive-aggressive, says "activate passive-aggressive" or "PA mode".