michael-denyer/pstack-claude

这个仓库里有 54 个技能，GitHub 星标 ★ 435。

• architectSketch types, signatures, and module structure before code, then stay in the loo
• arenaSpawn N parallel candidates at the same task, pick a base, graft the strongest p
• automate-meUse for \"automate me\", \"create/update/refresh my -mode skill\", \"turn/captur
• babysitWatch an open PR — fix failing CI, handle the straightforward review comments, a
• blast-radiusFind what a change could break somewhere else before it ships, beyond the diff,
• broRestate the last message in plain human language, with no jargon. Use for /bro o
• create-verification-skillGenerate a project-local verification skill that drives your app the way a user
• deslopRemove AI-generated code slop and clean up code style
• figure-it-outDesign an auditable playbook when no narrower one fits: a large migration, an am
• fix-ciFind failing PR checks, inspect logs or external check links, and apply focused
• fix-merge-conflictsResolve merge conflicts non-interactively, validate build and tests, and finaliz
• get-pr-commentsFetch and summarize review comments from the active pull request
• howUse for \"how does X work\", code walkthroughs before changing something, and pl
• interrogateUse for \"interrogate\", \"adversarial review\", \"multi-model review\", \"chall
• maintain-verification-skillPeriodic pass that keeps a project's verification skill and feature map honest:
• make-pr-easy-to-reviewPrepare PRs for review by cleaning noisy history, improving PR descriptions, and
• no-commentsSpawn the comment-sicko subagent, fix accepted findings, and offer encodings for
• poteto-modepoteto's agent style for concise, detailed responses, deliberate subagents, unsl
• principle-attack-the-premiseApply when two or more fixes that share one premise have failed the same gate. T
• principle-boundary-disciplineApply when wiring validation, error handling, or framework adapters. Concentrate
• principle-build-the-leverApply to any non-trivial work, not just bulk work: edits, migrations, analyses,
• principle-encode-lessons-in-structureApply when you catch yourself writing the same instruction a second time, or not
• principle-exhaust-the-design-spaceApply when facing a novel UI interaction or architectural decision with no prece
• principle-experience-firstApply when product, UX, or feature-scope tradeoffs come up. Choose user delight
• principle-fix-root-causesApply when debugging. Trace each symptom to its root cause and fix it there; rep
• principle-foundational-thinkingApply before writing logic: choosing core types and data structures, sequencing
• principle-guard-the-context-windowApply when context is filling up: large outputs, long files, repeated reads, fan
• principle-laziness-protocolApply when refactoring, evaluating diff size, or tempted to add abstractions, la
• principle-make-operations-idempotentApply when designing commands, lifecycle steps, or processing loops that run ami
• principle-migrate-callers-then-delete-legacy-apisApply when introducing a new internal API while old callers still exist. Migrate
• principle-minimize-reader-loadApply when reviewing or shaping code that's hard to trace. Count layers between
• principle-model-the-domainApply when writing stateful logic, or when code branches a lot or repeats a shap
• principle-never-block-on-the-humanApply when tempted to ask 'should I do X?' on reversible work. Proceed, present
• principle-outcome-oriented-executionApply during planned rewrites and migrations with explicit phase boundaries. Con
• principle-prove-it-worksApply after completing a task, before declaring done. Verify against the real ar
• principle-redesign-from-first-principlesApply when integrating a new requirement into an existing design. Redesign as if
• principle-separate-before-serializing-shared-stateApply when concurrent actors might write to the same file, branch, key, or state
• principle-sequence-verifiable-unitsApply to multi-step work (sweeps, migrations, runs of similar edits) and to how
• principle-subtract-before-you-addApply when sequencing an addition, refactor, or rewrite. Remove dead code, redun
• principle-test-behavior-not-implementationApply when you write, change, or keep a test. Call the code the way its users do
• principle-type-system-disciplineApply when designing types, reviewing a function signature, or writing code in a
• recallReconstruct your recent working context from your own chat history, live state,
• reflectSpawn three parallel review subagents over the active transcript, surface learni
• setup-pstackConfigure which models pstack uses per role. Detects your available Claude model
• show-me-your-workKeep a reviewable decision trail for long-running or unattended work: a TSV log
• swarmFan out N parallel workers, drain them, and return one report. Use for /swarm, '
• tddUse only when the user explicitly asks for TDD, a failing test, or a regression
• teachExplain a body of work plainly so a person actually understands it. Runs the `ho
• technical-writingLayered technical-writing standard: Diátaxis structure, Google developer style s
• thermo-nuclear-code-quality-reviewRun an extremely strict maintainability review for abstraction quality, giant fi
• typescript-best-practicesTypeScript best practices. Use when reading or editing any .ts or .tsx file.
• unslopCut AI tells from any writing. Must always apply.
• what-did-i-get-doneSummarize authored commits over a user-specified time period into a concise upda
• whyUse for 'why does X work this way', 'why we picked Y', design rationale, regress