code-review-skill
Use when reviewing code, pull requests, architecture, security, performance, maintainability, or language/framework-specific defects.
Skills
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 11-16 00:04
Coding & development
41,205 results
codeburn
Local-first AI coding token/cost analytics via CodeBurn CLI (npx codeburn). Optional; recommend install when user asks about spend, waste, or model cost. Not a…
coding-discipline
Operating contract for changing code, scripts, configuration, or build files. Use before implementation work; do not use as a domain-specific Skyrim syntax…
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool…
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
one-shot-completion
Use when the user asks for a finished result, end-to-end fix, “do it all”, or a task with implied deliverables.
ponytail
Use when coding work risks over-engineering, unnecessary dependencies, excess abstraction, or a larger solution than the requirement needs.
ponytail-audit
Quality audit of a whole repo: bugs, security holes, what breaks under real load, risky code without tests, slow paths, and what to delete, merge or split.…
ponytail-debt
List every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail…
ponytail-help
Quick reference for ponytail levels, skills and commands. One-shot display. Use for /ponytail-help, "ponytail help", "how do I use ponytail".
ponytail-review
Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed.…
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical…
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
token-efficiency
Use when waiting for CI/builds, reducing repetitive reads, measuring token cost or caching, or choosing MCP/skill scope. Save round trips and irrelevant output…
unity-mod-frameworks
Unity game mods via BepInEx, Harmony, MonoMod, IL2CPP or Mono - RimWorld, Valheim, Subnautica, Lethal Company, Risk of Rain 2, Stardew Valley, Oxygen Not…
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via…
workspace-organization
Use when starting, placing, or scaffolding a project, or entering a workspace with no map — settle the root with the user, keep layout tidy, maintain…
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
relic-routing
Define routes with path parameters, wildcards, tail segments, and typed params in Relic. Use when adding endpoints, handling dynamic URLs, setting up URL…
shopware-change-scope
Scope Shopware bug fixes, cleanups, and behavioral changes. Use when fixing an issue, applying review feedback, deciding whether to broaden a cleanup, or…
autonomous-coding-agent
Build autonomous coding agents with CLI integration. Use when creating automated coding workflows, managing multi-session development, or building CI/CD code…