8cc99ab483
Major restructure of the compounding-engineering plugin: ## Agents (24 total, now categorized) - review/ (10): architecture-strategist, code-simplicity-reviewer, data-integrity-guardian, dhh-rails-reviewer, kieran-rails-reviewer, kieran-python-reviewer, kieran-typescript-reviewer, pattern-recognition-specialist, performance-oracle, security-sentinel - research/ (4): best-practices-researcher, framework-docs-researcher, git-history-analyzer, repo-research-analyst - design/ (3): design-implementation-reviewer, design-iterator, figma-design-sync - workflow/ (6): bug-reproduction-validator, every-style-editor, feedback-codifier, lint, pr-comment-resolver, spec-flow-analyzer - docs/ (1): ankane-readme-writer ## Commands (15 total) - Moved workflow commands to commands/workflows/ subdirectory - Added: changelog, create-agent-skill, heal-skill, plan_review, prime, reproduce-bug, resolve_parallel, resolve_pr_parallel ## Skills (11 total) - Added: andrew-kane-gem-writer, codify-docs, create-agent-skills, dhh-ruby-style, dspy-ruby, every-style-editor, file-todos, frontend-design, git-worktree, skill-creator - Kept: gemini-imagegen 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
35 lines
1.2 KiB
Markdown
35 lines
1.2 KiB
Markdown
---
|
||
name: resolve_parallel
|
||
description: Resolve all TODO comments using parallel processing
|
||
argument-hint: "[optional: specific TODO pattern or file]"
|
||
---
|
||
|
||
Resolve all TODO comments using parallel processing.
|
||
|
||
## Workflow
|
||
|
||
### 1. Analyze
|
||
|
||
Gather the things todo from above.
|
||
|
||
### 2. Plan
|
||
|
||
Create a TodoWrite list of all unresolved items grouped by type.Make sure to look at dependencies that might occur and prioritize the ones needed by others. For example, if you need to change a name, you must wait to do the others. Output a mermaid flow diagram showing how we can do this. Can we do everything in parallel? Do we need to do one first that leads to others in parallel? I'll put the to-dos in the mermaid diagram flow‑wise so the agent knows how to proceed in order.
|
||
|
||
### 3. Implement (PARALLEL)
|
||
|
||
Spawn a pr-comment-resolver agent for each unresolved item in parallel.
|
||
|
||
So if there are 3 comments, it will spawn 3 pr-comment-resolver agents in parallel. liek this
|
||
|
||
1. Task pr-comment-resolver(comment1)
|
||
2. Task pr-comment-resolver(comment2)
|
||
3. Task pr-comment-resolver(comment3)
|
||
|
||
Always run all in parallel subagents/Tasks for each Todo item.
|
||
|
||
### 4. Commit & Resolve
|
||
|
||
- Commit changes
|
||
- Push to remote
|