refactoring-diagnosis
Use when identifying bad code/design and selecting refactor targets - produces a diagnosis report with smells, risks, and refactor vs rewrite decision
浏览 withzombies 维护的已发布 AI 技能,比较用途与说明,并通过来源仓库了解安装方式。
已收录技能
23收录技能的仓库 Stars 合计
1,315仓库 Forks
176平均每个技能的仓库 Stars
57同一仓库中的多个技能可能共享 Stars,合计包含重复仓库数据。
Use when identifying bad code/design and selecting refactor targets - produces a diagnosis report with smells, risks, and refactor vs rewrite decision
Use to expand bd tasks with detailed implementation steps - adds exact file paths, complete code, verification commands assuming zero context
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...
Use when implementation complete and tests pass - closes bd epic, presents integration options (merge/PR/keep/discard), executes choice
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
Use to expand bd tasks with detailed implementation steps - adds exact file paths, complete code, verification commands assuming zero context
Use when creating new skills, editing existing skills, or verifying skills work - applies TDD to documentation by testing with subagents before writing
Use when writing or changing tests, adding mocks - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies
Use when creating Claude Code hooks - covers hook patterns, composition, testing, progressive enhancement from simple to advanced
Use before claiming work complete, fixed, or passing - requires running verification commands and confirming output; evidence before assertions always
Use when encountering bugs or test failures - systematic debugging using debuggers, internet research, and agents to find root cause before fixing
Use when you have to refine subtasks into actionable plans ensuring that all corner cases are handled and we understand all the requirements.
Use when skills aren't activating reliably - covers official solutions (better descriptions) and custom hook system for deterministic skill activation
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...
Use to execute bd tasks iteratively - executes one task, reviews learnings, creates/refines next task, then STOPS for user review before continuing
Use when encountering a bug - complete workflow from discovery through debugging, bd issue, test-driven fix, verification, and closure
Use when errors occur deep in execution - traces bugs backward through call stack to find original trigger, not just symptom
Use for advanced bd operations - splitting tasks mid-flight, merging duplicates, changing dependencies, archiving epics, querying metrics, cross-epic dependencies
Use when implementing features or fixing bugs - enforces RED-GREEN-REFACTOR cycle requiring tests to fail before writing code
Use when refactoring code - test-preserving transformations in small steps, running tests between each change
Use after hyperpowers:executing-plans completes all tasks - verifies implementation against bd spec, all success criteria met, anti-patterns avoided
Use when creating or developing anything, before writing code - refines rough ideas into bd epics with immutable requirements
Use when starting any conversation - establishes mandatory workflows for finding and using skills
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。