leftovers
End-of-branch cleanup. Finds what this branch added that the finished work doesn't use (abandoned first attempts, helpers that duplicate existing ones, unused…
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 11-17 00:07
41,434 results
End-of-branch cleanup. Finds what this branch added that the finished work doesn't use (abandoned first attempts, helpers that duplicate existing ones, unused…
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a…
Remove AI-generated code slop and clean up code style
Implement a piece of work based on a spec or set of tickets.
Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior. Use for "make this…
Create a fresh branch, complete work, and open a pull request
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a…
Use when you need to resolve an in-progress git merge/rebase conflict.
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality…
Write, fix, and run single-file, self-contained Python scripts using uv's PEP 723 inline metadata. When adding dependencies, always include `[tool.uv] exclude-newer` to preserve reproducibility. "Write a script in Python", "script with uv", "one-off Python...
Produce a weekly synthesis of authored commits with highlights by bugfix, tech debt, and net-new work
Summarize authored commits over a user-specified time period into a concise update
Contract-first design, Hyrum's Law, One-Version Rule, error semantics, boundary validation. Use when designing APIs, module boundaries, or public interfaces.
Trunk-based development, atomic commits, change sizing (~100 lines), commit-as-save-point pattern. Use when making any code change.
Ground every framework decision in official documentation. Use when you want authoritative, source-cited code for any framework or library.
Write a structured specification before code: objectives, structure, code style, testing strategy, boundaries. Use when starting a new project or feature.
TypeScript best practices. Use when reading or editing any .ts or .tsx file.
Explore the solution space when the path isn't obvious — invent options, stress-test them, pick one. Use for architecture decisions, design tradeoffs,…
Commander.js CLI framework patterns including Command class, options, arguments, nested subcommands, and Option class usage. Use when building Node.js CLIs,…
Modern type-safe Typer CLI patterns with type hints, Enums, and sub-apps. Use when building CLI applications, creating Typer commands, implementing type-safe…
Designs tool and slash-command runtimes for coding-agent CLIs: registries, deferred loading, tool search, dispatch, forks. Use when modeling tool pools. Not…
Designs session and task state for coding-agent runtimes: resume, checkpoints, compaction, cancellation, background and scheduled runs. Use when persisting…
Designs user-facing surfaces of coding-agent runtimes: remote and bridge sessions, transports, reconnect, terminal REPL, input history. Use when building agent…
Run Spectral to lint OpenAPI and AsyncAPI specs for security issues. Validates API design for authentication, authorization, rate limiting, and input…