GitHub
finding-dead-code
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".
Skills IA Contenu et médias
Découvrez les skills Contenu et médias, comparez leurs dépôts et consultez leurs instructions.
Catégories: Contenu et médias
Contenu et médias Effacer les filtres
Explorer
GitHub
emotional-stakes
Use when writing subagent prompts, skill instructions, or any high-stakes task requiring accuracy and truthfulness
GitHub
devils-advocate
Use before design phase to challenge assumptions and surface risks
GitHub
receiving-code-review
Use when you have received code review feedback and need to process it. [DEPRECATED] Routes to code-review --feedback
GitHub
fun-mode
Use when starting a session and wanting creative engagement, or when user says '/fun' or asks for a persona
GitHub
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
GitHub
using-lsp-tools
Use when mcp-language-server tools are available and you need semantic code intelligence for navigation, refactoring, or type analysis
GitHub
tarot-mode
Use when session returns mode.type='tarot' - tarot archetypes collaborate via roundtable dialogue with instruction-engineering embedded
GitHub
implementing-features
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......
GitHub
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
GitHub
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
GitHub
instruction-optimizer
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...
GitHub
project-encyclopedia
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.
GitHub
executing-plans
Use when you have a written implementation plan to execute
GitHub
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
GitHub
worktree-merge
Use when merging parallel worktrees back together after parallel implementation
GitHub
debugging
Use when debugging bugs, test failures, or unexpected behavior
GitHub
merge-conflict-resolution
Use when git merge or rebase fails with conflicts, you see 'unmerged paths' or conflict markers (
GitHub
using-skills
Use when starting any conversation
GitHub
instruction-engineering
Use when: (1) constructing prompts for subagents, (2) invoking the Task tool, or (3) writing/improving skill instructions or any LLM prompts
GitHub
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
GitHub
documentation-updates
Use after modifying library skills, library commands, or agents to ensure CHANGELOG, README, and docs are updated
GitHub
fixing-tests
Use when tests are failing, test quality issues were identified, or user wants to fix/improve specific tests
GitHub
fact-checking
Use when reviewing code changes, auditing documentation accuracy, validating technical claims before merge, or user says "verify claims", "factcheck", "audit documentation", "validate comments", "are these clai...
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é.