requesting-code-review
Use when completing tasks, implementing major features, or before merging
Découvrez les skills Recherche, comparez leurs dépôts et consultez leurs instructions.
Use when completing tasks, implementing major features, or before merging
Meta-audit skill for spellbook development. Spawns parallel subagents to factcheck docs, optimize instructions, find token savings, and identify MCP candidates. Produces actionable report.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans
Use when reading files or command output of unknown size to avoid blind truncation and context loss
Use when reviewing code changes, auditing new features, cleaning up PRs, or user says "find dead code", "find unused code", "check for unnecessary additions", "what can I remove".
Use when writing subagent prompts, skill instructions, or any high-stakes task requiring accuracy and truthfulness
Use before design phase to challenge assumptions and surface risks
Use when you have received code review feedback and need to process it. [DEPRECATED] Routes to code-review --feedback
Use when starting a session and wanting creative engagement, or when user says '/fun' or asks for a persona
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when mcp-language-server tools are available and you need semantic code intelligence for navigation, refactoring, or type analysis
Use when writing or modifying code. Enforces production-quality standards, prohibits common shortcuts, and ensures pre-existing issues are addressed. Invoked automatically by implementing-features and test-driv...
Use when session returns mode.type='tarot' - tarot archetypes collaborate via roundtable dialogue with instruction-engineering embedded
Use when building, creating, or adding functionality. Triggers: "implement X", "build Y", "add feature Z", "create X", "start a new project", "Would be great to...", "I want to...", "We need...", "Can we add......
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when reviewing large PRs to surface changes requiring human attention
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
Use when instruction files (skills, prompts, CLAUDE.md) are too long or need token reduction while preserving capability. Triggers: "optimize instructions", "reduce tokens", "compress skill", "make this shorter...
Use on first session in a project, or when user asks for codebase overview. Creates persistent glossary, architecture maps, and decision records to solve agent amnesia.
Use when you have a written implementation plan to execute
Use when you have a spec or requirements for a multi-step task, before touching code
Use when merging parallel worktrees back together after parallel implementation
Use when debugging bugs, test failures, or unexpected behavior
Use when git merge or rebase fails with conflicts, you see 'unmerged paths' or conflict markers (
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.