michael-deny
56 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
michael-denyerfix-ci
Find failing PR checks, inspect logs or external check links, and apply focused fixes
- installs
- 2
- GitHub stars
- 3.2K
- Updated
- Oct 21
michael-denyerfix-merge-conflicts
Resolve merge conflicts non-interactively, validate build and tests, and finalize conflict resolution
- installs
- 2
- GitHub stars
- 3.2K
- Updated
- Oct 21
michael-denyerhow
Use for \"how does X work\", code walkthroughs before changing something, and placement / ownership / layering questions (\"where should this live\", \"which package owns this\", \"is this the right layer\"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.
- installs
- 2
- GitHub stars
- 3.2K
- Updated
- Oct 21
michael-denyerketchup
Catch the user up on what changed in this chat since their last message, in plain words and small visuals. List every item waiting on them with what they need to decide it from the reply alone. Use for /ketchup.
- installs
- 2
- GitHub stars
- 3.1K
- Updated
- Oct 20
michael-denyermaintain-formal-verification-skill
Bring a project's formal verification back in line with the code after the code changes: find the commits that touched verified code, update the model, harness, or properties to describe the code as it is now, rerun, and say whether each failure is drift in the verification or a bug in the code. Use for /maintain-formal-verification-skill, \"is the model still true to the code\", or after merges and refactors that touched verified code without rechecking it.
- installs
- 2
- GitHub stars
- 3.1K
- Updated
- Oct 20
michael-denyermaintain-verification-skill
Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or \"audit the verify skill\".
- installs
- 2
- GitHub stars
- 3.1K
- Updated
- Oct 20
michael-denyermake-pr-easy-to-review
Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior. Use for "make this easy to review", "tidy this PR", "clean up commits", or "annotate the diff".
- installs
- 2
- GitHub stars
- 3.1K
- Updated
- Oct 20
michael-denyerpoteto-help
Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.
- installs
- 2
- GitHub stars
- 3.2K
- Updated
- Oct 21
michael-denyerprinciple-boundary-discipline
Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.
- installs
- 2
- GitHub stars
- 3.2K
- Updated
- Oct 21
michael-denyerprinciple-experience-first
Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.
- installs
- 2
- GitHub stars
- 3.2K
- Updated
- Oct 21
michael-denyerprinciple-explain-the-number
Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.
- installs
- 2
- GitHub stars
- 3.1K
- Updated
- Oct 20
michael-denyerprinciple-fix-root-causes
Apply when debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a fix only when the state it handles is legitimate.
- installs
- 2
- GitHub stars
- 3.2K
- Updated
- Oct 21
michael-denyerprinciple-foundational-thinking
Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.
- installs
- 2
- GitHub stars
- 3.1K
- Updated
- Oct 20
michael-denyerprinciple-minimize-reader-load
Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.
- installs
- 2
- GitHub stars
- 3.1K
- Updated
- Oct 20
michael-denyerprinciple-model-the-domain
Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files.
- installs
- 2
- GitHub stars
- 3.1K
- Updated
- Oct 20
michael-denyerprinciple-never-block-on-the-human
Apply when tempted to ask 'should I do X?' on reversible work.
- installs
- 2
- GitHub stars
- 3.1K
- Updated
- Oct 20
michael-denyerprinciple-outcome-oriented-execution
Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.
- installs
- 2
- GitHub stars
- 3.1K
- Updated
- Oct 20
michael-denyerprinciple-redesign-from-first-principles
Apply when integrating a new requirement into an existing design.
- installs
- 2
- GitHub stars
- 3.1K
- Updated
- Oct 20
michael-denyerprinciple-separate-before-serializing-shared-state
Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.
- installs
- 2
- GitHub stars
- 3.2K
- Updated
- Oct 21
michael-denyerprinciple-sequence-verifiable-units
Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.
- installs
- 2
- GitHub stars
- 3.2K
- Updated
- Oct 21
michael-denyerprinciple-subtract-before-you-add
Apply when sequencing an addition, refactor, or rewrite. Remove dead code, redundant validators, and stub references first, then build on the simpler base.
- installs
- 2
- GitHub stars
- 3.2K
- Updated
- Oct 21
michael-denyerprinciple-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
- installs
- 2
- GitHub stars
- 3.2K
- Updated
- Oct 21
michael-denyerrecall
Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming work, and before telling the user that something was never recorded.
- installs
- 2
- GitHub stars
- 3.2K
- Updated
- Oct 21
michael-denyerreflect
Spawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.
- installs
- 2
- GitHub stars
- 3.2K
- Updated
- Oct 21