mirror of https://github.com/catlog22/Claude-Code-Workflow.git synced 2026-02-05 01:50:27 +08:00

Files

catlog22 89f6ac6804 feat: Implement multi-phase project analysis workflow with Mermaid diagram generation and CPCC compliance documentation

- Phase 3: Added Mermaid diagram generation for system architecture, function modules, algorithms, class diagrams, sequence diagrams, and error flows.
- Phase 4: Assembled analysis and diagrams into a structured CPCC-compliant document with section templates and figure numbering.
- Phase 5: Developed compliance review process with iterative refinement based on analysis findings and user feedback.
- Added CPCC compliance requirements and quality standards for project analysis reports.
- Established a comprehensive project analysis skill with detailed execution flow and report types.
- Enhanced error handling and recovery mechanisms throughout the analysis phases.

2025-12-26 11:44:29 +08:00

2.3 KiB

Raw Blame History

Phase 1: Requirements Discovery

Collect user requirements before analysis begins.

Execution

Step 1: Report Type Selection

AskUserQuestion({
  questions: [{
    question: "What type of project analysis report would you like?",
    header: "Report Type",
    multiSelect: false,
    options: [
      {label: "Architecture (Recommended)", description: "System structure, module relationships, layer analysis, dependency graph"},
      {label: "Design", description: "Design patterns, class relationships, component interactions, abstraction analysis"},
      {label: "Methods", description: "Key algorithms, critical code paths, core function explanations with examples"},
      {label: "Comprehensive", description: "All above combined into a complete project analysis"}
    ]
  }]
})

Step 2: Depth Level Selection

AskUserQuestion({
  questions: [{
    question: "What depth level do you need?",
    header: "Depth",
    multiSelect: false,
    options: [
      {label: "Overview", description: "High-level understanding, suitable for onboarding"},
      {label: "Detailed", description: "In-depth analysis with code examples"},
      {label: "Deep-Dive", description: "Exhaustive analysis with implementation details"}
    ]
  }]
})

Step 3: Scope Definition

AskUserQuestion({
  questions: [{
    question: "What scope should the analysis cover?",
    header: "Scope",
    multiSelect: false,
    options: [
      {label: "Full Project", description: "Analyze entire codebase"},
      {label: "Specific Module", description: "Focus on a specific module or directory"},
      {label: "Custom Path", description: "Specify custom path pattern"}
    ]
  }]
})

Focus Areas Mapping

Report Type	Focus Areas
Architecture	Layer Structure, Module Dependencies, Entry Points, Data Flow
Design	Design Patterns, Class Relationships, Interface Contracts, State Management
Methods	Core Algorithms, Critical Paths, Public APIs, Complex Logic
Comprehensive	All above combined

Output

Save configuration to analysis-config.json:

{
  "type": "architecture|design|methods|comprehensive",
  "depth": "overview|detailed|deep-dive",
  "scope": "**/*|src/**/*|custom",
  "focus_areas": ["..."]
}

2.3 KiB Raw Blame History