auto
01Command Claude Code
An automatic command selector that reads a described task and routes it to a matching development command.
One-click intelligence upgrade for Claude Code, including production-grade agents, skills, hooks, commands, rules, and MCP configuration
Command Claude Code
An automatic command selector that reads a described task and routes it to a matching development command.
Command Claude Code
A command that incrementally fixes TypeScript and build errors by running the project build, grouping and explaining errors, applying fixes, and checking the result again.
Command Claude Code
A review command that examines uncommitted code changes for security problems, code-quality issues, and common development mistakes.
Command Claude Code
A command that uses Playwright to create and run end-to-end tests, which check complete user journeys through an application.
Command Claude Code
A planning command that restates a development request, identifies risks, and creates a step-by-step implementation plan. It waits for the user's approval before code changes begin.
Command Claude Code
A dead-code cleanup command for finding code that is no longer used and preparing safe removals. Dead code means files, exports, or dependencies that the project does not use.
Command Claude Code
A command that uses test-driven development (TDD): define the code interface, write tests first, implement the smallest working solution, and then improve it. It also checks that at least 80% of the code is covered by tests.
Command Claude Code
A command that checks automated-test coverage and creates tests for code paths that are not tested. Test coverage measures which parts of a program are exercised by tests.
Command Claude Code
A command that scans a codebase and updates concise architecture documents describing its backend, frontend, data model, and overall structure.
Command Claude Code
A command that creates developer documentation from project settings and environment examples. It uses package.json, a file that defines project scripts, and .env.example, a template listing configuration variables.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: