GitHub
refactoring-diagnosis
Use when identifying bad code/design and selecting refactor targets - produces a diagnosis report with smells, risks, and refactor vs rewrite decision
☆ 65Voir le skill
withzombies AI Skills
GitHub ↗Explorez les skills IA publiés de withzombies et consultez leurs instructions source.
Statistiques de l’auteur
Skills indexés
23Étoiles des dépôts des skills indexés
1,315Forks du dépôt
176Moyenne des étoiles par skill indexé
57Les étoiles d’un dépôt peuvent se répéter entre ses skills.
Catégories populaires
Indexation récente
Explorer
GitHub
writing-plans
Use to expand bd tasks with detailed implementation steps - adds exact file paths, complete code, verification commands assuming zero context
☆ 65Voir le skill
GitHub
analyzing-test-effectiveness
Use to audit test quality with Google Fellow SRE scrutiny - identifies tautological tests, coverage gaming, weak assertions, missing corner cases. Creates bd epic with tasks for improvements, then runs SRE task...
☆ 65Voir le skill
GitHub
finishing-a-development-branch
Use when implementation complete and tests pass - closes bd epic, presents integration options (merge/PR/keep/discard), executes choice
☆ 56Voir le skill
GitHub
dispatching-parallel-agents
Use when facing 3+ independent failures that can be investigated without shared state or dependencies - dispatches multiple Claude agents to investigate and fix independent problems concurrently
☆ 56Voir le skill
GitHub
writing-plans
Use to expand bd tasks with detailed implementation steps - adds exact file paths, complete code, verification commands assuming zero context
☆ 56Voir le skill
GitHub
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work - applies TDD to documentation by testing with subagents before writing
☆ 56Voir le skill
GitHub
testing-anti-patterns
Use when writing or changing tests, adding mocks - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies
☆ 56Voir le skill
GitHub
building-hooks
Use when creating Claude Code hooks - covers hook patterns, composition, testing, progressive enhancement from simple to advanced
☆ 56Voir le skill
GitHub
verification-before-completion
Use before claiming work complete, fixed, or passing - requires running verification commands and confirming output; evidence before assertions always
☆ 56Voir le skill
GitHub
debugging-with-tools
Use when encountering bugs or test failures - systematic debugging using debuggers, internet research, and agents to find root cause before fixing
☆ 56Voir le skill
GitHub
sre-task-refinement
Use when you have to refine subtasks into actionable plans ensuring that all corner cases are handled and we understand all the requirements.
☆ 56Voir le skill
GitHub
skills-auto-activation
Use when skills aren't activating reliably - covers official solutions (better descriptions) and custom hook system for deterministic skill activation
☆ 56Voir le skill
GitHub
analyzing-test-effectiveness
Use to audit test quality with Google Fellow SRE scrutiny - identifies tautological tests, coverage gaming, weak assertions, missing corner cases. Creates bd epic with tasks for improvements, then runs SRE task...
☆ 56Voir le skill
GitHub
executing-plans
Use to execute bd tasks iteratively - executes one task, reviews learnings, creates/refines next task, then STOPS for user review before continuing
☆ 56Voir le skill
GitHub
fixing-bugs
Use when encountering a bug - complete workflow from discovery through debugging, bd issue, test-driven fix, verification, and closure
☆ 56Voir le skill
GitHub
root-cause-tracing
Use when errors occur deep in execution - traces bugs backward through call stack to find original trigger, not just symptom
☆ 56Voir le skill
GitHub
managing-bd-tasks
Use for advanced bd operations - splitting tasks mid-flight, merging duplicates, changing dependencies, archiving epics, querying metrics, cross-epic dependencies
☆ 56Voir le skill
GitHub
test-driven-development
Use when implementing features or fixing bugs - enforces RED-GREEN-REFACTOR cycle requiring tests to fail before writing code
☆ 56Voir le skill
GitHub
refactoring-safely
Use when refactoring code - test-preserving transformations in small steps, running tests between each change
☆ 56Voir le skill
GitHub
review-implementation
Use after hyperpowers:executing-plans completes all tasks - verifies implementation against bd spec, all success criteria met, anti-patterns avoided
☆ 56Voir le skill
GitHub
brainstorming
Use when creating or developing anything, before writing code - refines rough ideas into bd epics with immutable requirements
☆ 56Voir le skill
GitHub
using-hyper
Use when starting any conversation - establishes mandatory workflows for finding and using skills
☆ 56Voir 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é.