style: Fix Prettier formatting issues

Author: hisaho

src/orchestration/builtin-skills.js

@@ -454,7 +454,10 @@ const requirementsReviewerSkill = {
       }
 
       default:
-        return { success: false, error: 'Invalid action. Use: review, fagan, pbr, metrics, correct' };
+        return {
+          success: false,
+          error: 'Invalid action. Use: review, fagan, pbr, metrics, correct',
+        };
     }
   },
 };
@@ -499,7 +502,8 @@ const designReviewerSkill = {
     {
       name: 'focus',
       type: 'array',
-      description: 'Review focus areas: solid, patterns, coupling-cohesion, error-handling, security, all',
+      description:
+        'Review focus areas: solid, patterns, coupling-cohesion, error-handling, security, all',
       required: false,
     },
     { name: 'outputFormat', type: 'string', description: 'json, markdown', required: false },
@@ -685,7 +689,8 @@ const designReviewerSkill = {
       default:
         return {
           success: false,
-          error: 'Invalid action. Use: review, solid, patterns, coupling, security, c4, adr, correct',
+          error:
+            'Invalid action. Use: review, solid, patterns, coupling, security, c4, adr, correct',
         };
     }
   },

src/validators/design-reviewer.js

@@ -463,9 +463,7 @@ class DesignReviewer {
     }
 
     // DIP (Dependency Inversion Principle) チェック
-    if (
-      /directly\s+depend|concrete\s+class|tight\s+coupling|直接依存/gi.test(content)
-    ) {
+    if (/directly\s+depend|concrete\s+class|tight\s+coupling|直接依存/gi.test(content)) {
       issues.push(
         new DesignIssue({
           id: `DES-SOLID-${String(issueCounter++).padStart(3, '0')}`,
@@ -545,8 +543,7 @@ class DesignReviewer {
           severity: IssueSeverity.SUGGESTION,
           title: 'Consider Observer Pattern',
           description: 'Event handling mentioned. Observer pattern might be beneficial.',
-          recommendation:
-            'Consider Observer/Pub-Sub pattern for decoupled event notification.',
+          recommendation: 'Consider Observer/Pub-Sub pattern for decoupled event notification.',
         })
       );
     }
@@ -570,8 +567,7 @@ class DesignReviewer {
           severity: IssueSeverity.MAJOR,
           title: 'High Coupling Detected',
           description: 'Design mentions tight coupling between components',
-          recommendation:
-            'Reduce coupling through interfaces, events, or dependency injection.',
+          recommendation: 'Reduce coupling through interfaces, events, or dependency injection.',
         })
       );
     }
@@ -657,8 +653,7 @@ class DesignReviewer {
           severity: IssueSeverity.MINOR,
           title: 'Missing Retry Strategy',
           description: 'External service integration without retry strategy',
-          recommendation:
-            'Add retry with exponential backoff for external service calls.',
+          recommendation: 'Add retry with exponential backoff for external service calls.',
         })
       );
     }
@@ -675,8 +670,7 @@ class DesignReviewer {
           severity: IssueSeverity.MINOR,
           title: 'Consider Circuit Breaker',
           description: 'Distributed system without circuit breaker pattern',
-          recommendation:
-            'Implement circuit breaker pattern to prevent cascade failures.',
+          recommendation: 'Implement circuit breaker pattern to prevent cascade failures.',
         })
       );
     }
@@ -690,8 +684,7 @@ class DesignReviewer {
           severity: IssueSeverity.SUGGESTION,
           title: 'Consider Graceful Degradation',
           description: 'No graceful degradation strategy documented',
-          recommendation:
-            'Define fallback behaviors for when components fail.',
+          recommendation: 'Define fallback behaviors for when components fail.',
         })
       );
     }
@@ -844,8 +837,7 @@ class DesignReviewer {
           severity: IssueSeverity.MINOR,
           title: 'Missing Component Diagram',
           description: 'C4 Component diagram not found',
-          recommendation:
-            'Add Component diagram for key containers showing internal structure.',
+          recommendation: 'Add Component diagram for key containers showing internal structure.',
         })
       );
     }
@@ -875,8 +867,7 @@ class DesignReviewer {
           severity: IssueSeverity.MINOR,
           title: 'Missing ADR Status',
           description: 'ADR status not specified',
-          recommendation:
-            'Add status: proposed/accepted/deprecated/superseded.',
+          recommendation: 'Add status: proposed/accepted/deprecated/superseded.',
         })
       );
     }
@@ -889,8 +880,7 @@ class DesignReviewer {
           severity: IssueSeverity.MAJOR,
           title: 'Missing ADR Context',
           description: 'ADR context/background not documented',
-          recommendation:
-            'Add Context section explaining the problem/situation.',
+          recommendation: 'Add Context section explaining the problem/situation.',
         })
       );
     }
@@ -903,8 +893,7 @@ class DesignReviewer {
           severity: IssueSeverity.CRITICAL,
           title: 'Missing ADR Decision',
           description: 'ADR decision not clearly stated',
-          recommendation:
-            'Add Decision section clearly stating what was decided.',
+          recommendation: 'Add Decision section clearly stating what was decided.',
         })
       );
     }
@@ -917,8 +906,7 @@ class DesignReviewer {
           severity: IssueSeverity.MAJOR,
           title: 'Missing ADR Consequences',
           description: 'ADR consequences not documented',
-          recommendation:
-            'Add Consequences section with both positive and negative impacts.',
+          recommendation: 'Add Consequences section with both positive and negative impacts.',
         })
       );
     }
@@ -931,8 +919,7 @@ class DesignReviewer {
           severity: IssueSeverity.MINOR,
           title: 'Missing ADR Alternatives',
           description: 'ADR alternatives considered not documented',
-          recommendation:
-            'Add Alternatives section showing other options that were considered.',
+          recommendation: 'Add Alternatives section showing other options that were considered.',
         })
       );
     }

src/validators/requirements-reviewer.js

@@ -631,8 +631,7 @@ class RequirementsReviewer {
                 title: `Missing Boundary Values: ${req.id}`,
                 description: 'Requirement mentions ranges but boundary values are not specified.',
                 evidence: req.fullText,
-                recommendation:
-                  'Specify exact minimum and maximum values for boundary testing.',
+                recommendation: 'Specify exact minimum and maximum values for boundary testing.',
               })
             );
           }
@@ -668,8 +667,7 @@ class RequirementsReviewer {
             type: DefectType.MISSING,
             title: 'Missing Scalability Requirements',
             description: 'No requirements found for system scalability.',
-            recommendation:
-              'Define expected load, concurrent users, and scaling requirements.',
+            recommendation: 'Define expected load, concurrent users, and scaling requirements.',
           })
         );
       }
@@ -684,7 +682,8 @@ class RequirementsReviewer {
             type: DefectType.MISSING,
             title: 'Missing Availability Requirements',
             description: 'No availability/SLA requirements defined.',
-            recommendation: 'Specify target availability (e.g., 99.9% uptime) and recovery time objectives.',
+            recommendation:
+              'Specify target availability (e.g., 99.9% uptime) and recovery time objectives.',
           })
         );
       }
@@ -924,7 +923,8 @@ class RequirementsReviewer {
    * 修正レポートを生成
    */
   generateCorrectionReport(correctionResult) {
-    const { changesApplied, rejectedFindings, updatedQualityGate, filesModified } = correctionResult;
+    const { changesApplied, rejectedFindings, updatedQualityGate, filesModified } =
+      correctionResult;
 
     let report = `## 📝 Correction Report\n\n`;
     report += `**Correction Date**: ${new Date().toISOString().split('T')[0]}\n\n`;