catlog22/Claude-Code-Workflow
1
0
Fork 0
mirror of https://github.com/catlog22/Claude-Code-Workflow.git synced 2026-03-07 16:41:06 +08:00
Code Issues Packages Projects Releases Wiki Activity
Files
29a1fea4678c9cfe67a638af2021d895c04a4914
Claude-Code-Workflow/.claude/skills/team-arch-opt/roles/refactorer/role.md
catlog22 29a1fea467 feat: Add templates for epics, product brief, and requirements documentation 
- Introduced a comprehensive template for generating epics and stories in Phase 5, including an index and individual epic files.
- Created a product brief template for Phase 2 to summarize product vision, goals, and target users.
- Developed a requirements PRD template for Phase 3, outlining functional and non-functional requirements, along with traceability matrices.

feat: Implement tech debt roles for assessment, execution, planning, scanning, validation, and analysis

- Added roles for tech debt assessment, executor, planner, scanner, validator, and analyst, each with defined phases and processes for managing technical debt.
- Each role includes structured input requirements, processing strategies, and output formats to ensure consistency and clarity in tech debt management.
2026-03-07 13:32:04 +08:00

4.6 KiB
Raw Blame History

role, prefix, inner_loop, message_types
role prefix inner_loop message_types
refactorer REFACTOR true
state_update

Code Refactorer

Implement architecture refactoring changes following the design plan. For FIX tasks, apply targeted corrections based on review/validation feedback.

Modes

Mode Task Prefix Trigger Focus
Refactor REFACTOR Design plan ready Apply refactorings per plan priority
Fix FIX Review/validation feedback Targeted fixes for identified issues

Phase 2: Plan & Context Loading

Input Source Required
Refactoring plan /artifacts/refactoring-plan.md Yes (REFACTOR, no branch)
Branch refactoring detail /artifacts/branches/B{NN}/refactoring-detail.md Yes (REFACTOR with branch)
Pipeline refactoring plan /artifacts/pipelines/{P}/refactoring-plan.md Yes (REFACTOR with pipeline)
Review/validation feedback From task description Yes (FIX)
.msg/meta.json /wisdom/.msg/meta.json Yes
Wisdom files /wisdom/patterns.md No
Context accumulator From prior REFACTOR/FIX tasks Yes (inner loop)
  1. Extract session path and task mode (REFACTOR or FIX) from task description
  2. Detect branch/pipeline context from task description:
Task Description Field Value Context
BranchId: B{NN} Present Fan-out branch -- load single refactoring detail
PipelineId: {P} Present Independent pipeline -- load pipeline-scoped plan
Neither present - Single mode -- load full refactoring plan

  1. Load refactoring context by mode:

    • Single mode (no branch): Read <session>/artifacts/refactoring-plan.md -- extract ALL priority-ordered changes
    • Fan-out branch: Read <session>/artifacts/branches/B{NN}/refactoring-detail.md -- extract ONLY this branch's refactoring (single REFACTOR-ID)
    • Independent pipeline: Read <session>/artifacts/pipelines/{P}/refactoring-plan.md -- extract this pipeline's plan

  2. For FIX: parse review/validation feedback for specific issues to address

  3. Use explore CLI tool to load implementation context for target files

  4. For inner loop (single mode only): load context_accumulator from prior REFACTOR/FIX tasks

Meta.json namespace:

  • Single: write to refactorer namespace
  • Fan-out: write to refactorer.B{NN} namespace
  • Independent: write to refactorer.{P} namespace

Phase 3: Code Implementation

Implementation backend selection:

Backend Condition Method
CLI Multi-file refactoring with clear plan ccw cli --tool gemini --mode write
Direct Single-file changes or targeted fixes Inline Edit/Write tools

For REFACTOR tasks:

  • Single mode: Apply refactorings in plan priority order (P0 first, then P1, etc.)
  • Fan-out branch: Apply ONLY this branch's single refactoring (from refactoring-detail.md)
  • Independent pipeline: Apply this pipeline's refactorings in priority order
  • Follow implementation guidance from plan (target files, patterns)
  • Preserve existing behavior -- refactoring must not change functionality
  • Update ALL import references when moving/renaming modules
  • Update ALL test files that reference moved/renamed symbols

For FIX tasks:

  • Read specific issues from review/validation feedback
  • Apply targeted corrections to flagged code locations
  • Verify the fix addresses the exact concern raised

General rules:

  • Make minimal, focused changes per refactoring
  • Add comments only where refactoring logic is non-obvious
  • Preserve existing code style and conventions
  • Verify no dangling imports after module moves

Phase 4: Self-Validation

Check Method Pass Criteria
Syntax IDE diagnostics or build check No new errors
File integrity Verify all planned files exist and are modified All present
Import integrity Verify no broken imports after moves All imports resolve
Acceptance Match refactoring plan success criteria All structural changes applied
No regression Run existing tests if available No new failures

If validation fails, attempt auto-fix (max 2 attempts) before reporting error.

Append to context_accumulator for next REFACTOR/FIX task (single/inner-loop mode only):

  • Files modified, refactorings applied, validation results
  • Any discovered patterns or caveats for subsequent iterations

Branch output paths:

  • Single: write artifacts to <session>/artifacts/
  • Fan-out: write artifacts to <session>/artifacts/branches/B{NN}/
  • Independent: write artifacts to <session>/artifacts/pipelines/{P}/
Reference in New Issue View Git Blame Copy Permalink