---
name: review-service
description: Review a service definition (docs/services/<service-name>.md) using a structured 3-tier severity checklist.
argument-hint: "Relative path of the service document to review (e.g., docs/services/auth.md)"
---

Read and review the contents of a target service definition document in the workspace using a structured checklist with three severity levels (問題, 要確認, 提案).

## Review Checklist

### 1. 問題 (Issue/Problem - High Severity)

*Critical errors, logic flaws, or gaps that must be corrected.*

*   **構成要素の不足 (Missing Core Sections)**: Check if required sections are present: "サービス概要", "インターフェース定義", and "DTO定義".
*   **メソッド定義の整合性 (Interface Definition Mismatch)**: Signature, parameters, return values, or exception details that are inconsistent with the service role or DTO designs.
*   **アーキテクチャ定義との不整合 (Mismatch with ARCHITECTURE.md)**: Target application dependencies, namespace/package rules, or technology standards that violate the requirements of `docs/ARCHITECTURE.md`.
*   **参照・リンク切れ (Broken Links & References)**: References to DTOs or model tables (`docs/models/<table-name>.md`) that are invalid or broken.

### 2. 要確認 (Needs Confirmation/Clarification - Medium Severity)

*Items that require clarification or validation.*

*   **DTOバリデーションルールの妥当性 (DTO Validation Rules)**: Check if data types, mandatory constraints, or character limits configured in the DTO match the database schema constraints or logical application rules.
*   **エラー/例外処理方針 (Exception Handling Policy)**: Check if exception types and fallback logic for external APIs or DB operations are robust and well-documented.

### 3. 提案 (Suggestion/Recommendation - Low Severity)

*Constructive ideas to improve clarity, aesthetics, or user experience.*

*   **呼び出しフローの追加 (Sequence Flow)**: Suggest using Mermaid diagrams to illustrate interactions between components (e.g. `Controller -> Service -> Repository`).
*   **コードスニペット例の付記 (Code Snippet Examples)**: Provide quick mock implementations or class skeletons for implementation clarity.

---

## Execution Flow

1. **Locate Target File**:
   *   A file path argument is required. Prompt the user if not specified.
2. **Read Content**:
   *   Read the file content.
3. **Conduct Review**:
   *   Analyze the document line-by-line or section-by-section against the checklist.
4. **Save Report to File**:
   *   Save the formatted review report to `.review/[relative-path-to-target-document]` relative to the project root.
   *   Ensure the directories inside `.review/` are created automatically if they do not exist.
   *   If the report file already exists, overwrite it with the new review content.
5. **Output Report**:
   *   Present the structured review report in the chat and notify the user of the path to the saved file.

---

## Output Report Format

Output the review report using the following structure:

```markdown
# Document Review Report: [file basename]

Review of: `[relative/path/to/file]`

## Executive Summary

| Severity | Count | Key Focus |
| --- | --- | --- |
| 🔴 問題 (High) | 0 | Critical issues requiring immediate correction |
| 🟡 要確認 (Medium) | 0 | Items requiring user confirmation or alignment |
| 🟢 提案 (Low) | 0 | Suggestions for readability and quality |

---

## Detailed Findings

### 🔴 問題 (High Severity)
*List critical issues.*

- **[Short Summary of Issue]**
  - **Location**: Line X-Y / Section name
  - **Original Text**: `[original text]`
  - **Description**: [Why it is a problem]
  - **Recommended Action**: [Specific, actionable fix]

### 🟡 要確認 (Medium Severity)
*List items needing confirmation.*

- **[Short Summary]**
  - **Location**: Line X-Y / Section name
  - **Original Text**: `[original text]`
  - **Description**: [What needs confirmation and why]
  - **Recommended Action**: [Specific clarification questions or options]

### 🟢 提案 (Low Severity)
*List suggestions.*

- **[Short Summary]**
  - **Location**: Line X-Y / Section name
  - **Original Text**: `[original text]`
  - **Description**: [How it could be improved]
  - **Recommended Action**: [Concrete suggested text or structure]
```
