all publishers

michael-denyer

@michael-denyer source repo

21 published skills

  1. ▌
    Setup · michael-denyer
    Prepare all shared tools for the agent-formal-verify plugin: Java, Python, TLC, elan, Lean, Rust and Kani. Use for initial installation, missing prerequisites, or /agent-formal-verify:setup.
    4.3k repo stars
  2. ▌
    Formal Verify · michael-denyer bundle
    Model-check thread protocols with TLA+ and TLC, prove sequential invariants with Lean 4, and check bounded Rust functions with Kani. Map counter-examples to source locations, reproductions and fixes, and keep the models in CI. Bring existing models back in line after the code changes. Use for /agent-formal-verify:formal-verify, formal verification, model checking, Lean proofs, Kani, bounded Rust verification, rechecking models after code changes, or concurrency bugs that runtime tests cannot reproduce.
    4.3k repo stars
  3. ▌
    Bro · michael-denyer
    Restate the last message in plain human language, with no jargon. Use for /bro or when asked to say it plainly.
    4.3k repo stars
  4. ▌
    Fix CI · michael-denyer
    Find failing PR checks, inspect logs or external check links, and apply focused fixes
    4.3k repo stars
  5. ▌
    Memory MCP · michael-denyer
    Persistent memory for Claude Code with two-tier architecture: hot cache for instant recall (0ms) and semantic search for everything else (~50ms). Automatically learns what you use and promotes it.
    4.3k repo stars
  6. ▌
    Test Memory · michael-denyer
    Comprehensive interactive testing of all Memory MCP features
    4.3k repo stars
  7. ▌
    How · michael-denyer bundle
    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.
    4.3k repo stars
  8. ▌
    Tdd · michael-denyer
    Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.
    4.3k repo stars
  9. ▌
    Why · michael-denyer bundle
    Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
    4.3k repo stars
  10. ▌
    Swarm · michael-denyer
    Fan out N parallel workers, drain them, and return one report. Use for /swarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.
    4.3k repo stars
  11. ▌
    Teach · michael-denyer
    Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
    4.3k repo stars
  12. ▌
    Recall · michael-denyer
    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.
    4.3k repo stars
  13. ▌
    Unslop · michael-denyer
    Cut AI tells from any writing. Must always apply.
    4.3k repo stars
  14. ▌
    Babysit · michael-denyer
    Watch an open PR — fix failing CI, handle the straightforward review comments, and drive it to a mergeable state. Claude Code analog of Cursor's built-in /babysit. Use after opening a PR when the user wants the agent to shepherd it without re-prompting.
    4.3k repo stars
  15. ▌
    Reflect · michael-denyer bundle
    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.
    4.3k repo stars
  16. ▌
    Architect · michael-denyer bundle
    Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.
    4.3k repo stars
  17. ▌
    Automate Me · michael-denyer
    Use for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill", or wanting agents to follow how the user works. Drafts or revises a personal -mode skill via plugin-dev:skill-development + unslop, optionally pulling fresh evidence from recent transcripts.
    4.3k repo stars
  18. ▌
    Interrogate · michael-denyer bundle
    Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart". Multiple LLM reviewers challenge changes from independent angles.
    4.3k repo stars
  19. ▌
    No Comments · michael-denyer
    Spawn the comment-sicko subagent, fix accepted findings, and offer encodings for claimed constraints.
    4.3k repo stars
  20. ▌
    Blast Radius · michael-denyer
    Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', reviewing a small diff you don't trust, or a brief that asserts something about existing code ('make X public', 'X already handles Y') before you design against that assertion.
    4.3k repo stars
  21. ▌
    Technical Writing · michael-denyer
    Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
    4.3k repo stars