GitHub
requesting-code-review
Dispatch code-reviewer subagent to review implementation against plan or requirements before proceeding
☆ 38Voir le skill
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
executing-plans
Execute detailed plans in batches with review checkpoints
☆ 38Voir le skill
GitHub
using-git-worktrees
Create isolated git worktrees with smart directory selection and safety verification
☆ 38Voir le skill
GitHub
finishing-a-development-branch
Complete feature development with structured options for merge, PR, or cleanup
☆ 38Voir le skill
GitHub
refactoring-safely
Refactor with tests first, one change at a time, never mix refactoring with bug fixes or new features
☆ 38Voir le skill
GitHub
creating-skills
TDD for process documentation - test with subagents before writing, iterate until bulletproof
☆ 38Voir le skill
GitHub
testing-anti-patterns
Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.
☆ 38Voir le skill
GitHub
defense-in-depth-validation
Validate at every layer data passes through to make bugs impossible
☆ 38Voir le skill
GitHub
condition-based-waiting
Replace arbitrary timeouts with condition polling for reliable async tests
☆ 38Voir le skill
GitHub
test-driven-development-tdd
Write the test first, watch it fail, write minimal code to pass
☆ 38Voir le skill
GitHub
code-review-reception
Receive and act on code review feedback with technical rigor, not performative agreement or blind implementation
☆ 38Voir le skill
GitHub
validating-inputs
Check all external inputs for validity - garbage in, nothing out, never garbage out
☆ 38Voir le skill
GitHub
gardening-skills-wiki
Maintain skills wiki health - check links, naming, cross-references, and coverage
☆ 38Voir le skill
GitHub
writing-evergreen-comments
Write comments explaining WHAT and WHY, never temporal context or history
☆ 38Voir le skill
GitHub
vue
Use when editing .vue files, creating Vue 3 components, writing composables, or testing Vue code - provides Composition API patterns, props/emits best practices, VueUse integration, and reactive destructuring g...
☆ 38Voir le skill
GitHub
vueuse
Use when working with VueUse composables - provides reactive utilities for state, browser APIs, sensors, network, animations. Check VueUse before writing custom composables - most patterns already implemented.
☆ 38Voir le skill
GitHub
tbd
Lightweight, git-native issue tracking (aka beads) for AI agents. Use for creating, planning, updating, and tracking issues with dependencies. Invoke when user mentions tbd, beads, to-do lists, planning, tracki...
☆ 38Voir le skill
GitHub
nuxthub
Use when building NuxtHub v0.10.4 applications - provides database (Drizzle ORM with sqlite/postgresql/mysql), KV storage, blob storage, and cache APIs. Covers configuration, schema definition, migrations, mult...
☆ 38Voir le skill
GitHub
clarification-expert
Clarify ambiguous requests by researching first, then asking only judgment calls; stop before implementation.
☆ 37Voir le skill
GitHub
commit
Create micro-commits (minimal incision) with at least one validation signal per commit.
☆ 37Voir le skill
GitHub
gen-plan
Generate iterative `plan-N.md` files in the repo root (max N=5). Use only when asked; clarify before `plan-1.md`; stop at `plan-5.md`.
☆ 37Voir le skill
GitHub
select
Preflight bead work: verify beads are in use, confirm explicit start/continue, identify active bead or select next `bd ready`, clarify done criteria, and scope audit before marking `in_progress`.
☆ 37Voir le skill
GitHub
beads
bd (beads) issue-tracking workflow; use when `.beads/` exists or when running `bd` commands.
☆ 37Voir le skill
GitHub
trace
TRACE (Type/Readability/Atomic/Cognitive/Essential) lens for explaining code and proposing improvements (no edits applied).
☆ 37Voir le skill
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é.