GitHub
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
brmatola AI Skills
GitHub ↗Explorez les skills IA publiés de brmatola et consultez leurs instructions source.
Statistiques de l’auteur
Skills indexés
20Étoiles des dépôts des skills indexés
0Forks du dépôt
0Moyenne des étoiles par skill indexé
0Les étoiles d’un dépôt peuvent se répéter entre ses skills.
Catégories populaires
Indexation récente
Explorer
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 - guides completion of development work by presenting structured options for merge, PR, or cleanup
GitHub
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
GitHub
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
GitHub
researching-on-the-internet
Use when planning features and need current API docs, library patterns, or external knowledge - gathers well-sourced, current information from the internet to inform technical decisions
GitHub
using-gremlins
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
GitHub
maintaining-project-context
Use when completing development phases or branches to identify and update CLAUDE.md files that may have become stale - analyzes what changed, determines affected contracts and documentation, and coordinates upd...
GitHub
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
GitHub
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
GitHub
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
GitHub
writing-claude-md-files
Use when creating or updating CLAUDE.md files for projects or subdirectories - covers top-level vs domain-level organization, capturing architectural intent and contracts, and mandatory freshness dates
GitHub
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
GitHub
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
GitHub
investigating-a-codebase
Use when planning or designing features and need to understand current codebase state, find existing patterns, or verify assumptions about what exists - prevents hallucination by grounding plans in reality
GitHub
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before as...
GitHub
plan-archive
Use when a plan is abandoned, obsolete, or superseded and should be archived
GitHub
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
GitHub
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement...
GitHub
plan-complete
Use when a plan's implementation is finished and all work has been merged or shipped
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é.