Refactor
Propose better object-oriented architecture for complex, procedural codeFrom its SKILL.md
npx -y skills add broneq/bdk --skill refactorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.6 KB, 312 tokens by cl100k_base, as published. Nobody here has run it
Refactor
Relies on BDK foundation (STARTUP_INSTRUCTIONS.md) for project context and MCP tool preference.
For each <!-- INJECT: <name> --> marker below, run python3 ${CLAUDE_PLUGIN_ROOT}/scripts/inject-rules.py <name> and substitute its stdout in place of the marker before acting on it.
Complex refactor needed. Code messy, needs clean class separation.
Workflow:
- Architecture survey:
!python3 ${CLAUDE_PLUGIN_ROOT}/scripts/inject.py --chain ${CLAUDE_PLUGIN_ROOT}/fragments/tool-tiers/explore.chain.json
Using the exploration tools above: understand current community structure, identify tightly-coupled communities, detect cross-cutting concerns, and identify dead code with refactor_tool(mode="dead_code") if graph is available.
2. Launch explorer subagent with architecture findings as context (not blind). For follow-up questions on the same exploration, prefer SendMessage(to: "<agentId>", ...) over re-spawning. See STARTUP "Continuing a Spawned Agent".
3. Propose OO architecture with well-separated classes — reference community boundaries, address surprising connections
4. Identify applicable design patterns and explain fit — see rules below
5. Create docs in .bdk/refactor/:
- Architecture overview
- Applicable patterns with rationale
- Implementation plan
Problem description:
$ARGUMENTS
<!-- INJECT: design-patterns -->What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.