Creates or updates repository specs, acceptance criteria, durable decisions, and documentation for new work. Use when adding a feature or defining an ambiguous slice, when making architectural decisions or changing contracts (game state, leaderboard, audio, settings), or when recording durable context (decisions, glossary, conventions) for future engineers and agents.

2026-06-301

dead-code-audit

satyrlord/mb

Audits the MEMORYBLOX codebase for dead TypeScript code, orphan files, and unused symbols, triages findings into live dead code or false positives, and optionally removes provably dead code with focused validation. Use when the user asks for a dead-code scan, unused-code audit, orphan-file scan, unused-symbol triage, or cleanup from analyzer findings.

2026-06-301

deslop

satyrlord/mb

Remove AI-generated code slop from the current branch diff. Use when the user asks to deslop, clean up AI slop, remove unnecessary comments, strip defensive cruft, or flatten needless nesting.

2026-06-301

diagnose

satyrlord/mb

Runs a disciplined diagnosis loop for hard bugs and performance regressions. Reproduce, minimise, hypothesise, instrument, fix, and regression-test. Use when the user says "diagnose this", the bug is flaky or not yet reproducible, root cause is unknown after triage, or a performance regression needs measurement before fixing.

2026-06-301

full-code-review

satyrlord/mb

Extremely strict maintainability review hunting code-judo restructurings — abstraction quality, the 1k-line rule, and spaghetti growth. Use when asked to review code, do a code review, audit changes, check for issues, or review uncommitted/staged changes. Covers diff-first review of pending changes and broader codebase audit.

2026-06-301

name	handoff
description	Transfer session state to a fresh agent as a minimal, lossless state-transfer document.
argument-hint	What will the next session be used for?
disable-model-invocation	true

Handoff

Produce a state-transfer document — the minimum payload a fresh agent needs to resume this session without re-litigating decisions already made. Save to the temporary directory of the user's OS, not the current workspace.

Completion Criterion

The handoff is done when a fresh agent, given only this document and the repo, can state the current task, the last concrete action taken, and the exact next step — without asking a single clarifying question.

Required Sections

Current task — one sentence. What we are building or fixing.
State snapshot — the last concrete action taken, and the immediate next step. Be specific: file paths, line numbers, command to run.
Decisions made — what was ruled in, what was ruled out, and why. This is the highest-value section; it prevents re-litigation.
Open questions — only the ones that block the next step. Skip resolved questions and future-phase unknowns.
Files touched — paths, not contents. Reference diffs or commits when available.
Suggested skills — the repo skills the next agent should invoke, in order.

What to Exclude

Content already captured in artifacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL.
Conversation history, dead ends, or discarded approaches — unless the reason for discarding is a durable decision.
Sensitive information: API keys, passwords, PII.

Format

Plain Markdown. No boilerplate headers beyond the sections above. Prefer bullet lists over prose paragraphs.

Tailoring

If the user passed arguments, treat them as a description of the next session's focus. Weight the state snapshot and suggested skills toward that focus.