chore: 更新 ESLint 和 Prettier 配置，新增 lint-staged 配置文件，更新 .gitignore 文件以排除不必要的文件，增强 CI/CD 流程，添加 Husky 钩子以确保代码质量

Author: DeadWaveWave

.eslintrc.json

@@ -1,20 +1,19 @@
 {
   "parser": "@typescript-eslint/parser",
-  "extends": [
-    "eslint:recommended"
-  ],
+  "extends": ["eslint:recommended"],
   "plugins": ["@typescript-eslint"],
   "parserOptions": {
     "ecmaVersion": 2022,
     "sourceType": "module"
   },
   "rules": {
     "@typescript-eslint/no-unused-vars": "error",
-    "@typescript-eslint/no-explicit-any": "warn",
-    "prefer-const": "error"
+    "@typescript-eslint/no-explicit-any": "off",
+    "prefer-const": "error",
+    "no-control-regex": "off"
   },
   "env": {
     "node": true,
     "es2022": true
   }
-}
+}

.github/workflows/ci.yml

@@ -0,0 +1,58 @@
+name: CI
+
+on:
+  push:
+    branches: [main, develop]
+  pull_request:
+    branches: [main, develop]
+
+jobs:
+  test:
+    name: Test on Node.js ${{ matrix.node-version }}
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        node-version: [18.x, 20.x, 22.x]
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Setup pnpm
+        uses: pnpm/action-setup@v4
+        with:
+          version: 8
+
+      - name: Setup Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v4
+        with:
+          node-version: ${{ matrix.node-version }}
+          cache: 'pnpm'
+
+      - name: Install dependencies
+        run: pnpm install --frozen-lockfile
+
+      - name: Type check
+        run: pnpm run type-check
+
+      - name: Lint
+        run: pnpm run lint
+
+      - name: Format check
+        run: pnpm run format:check
+
+      - name: Test
+        run: pnpm run test:coverage
+
+      - name: Build
+        run: pnpm run build
+
+      - name: Upload coverage to Codecov
+        if: matrix.node-version == '20.x'
+        uses: codecov/codecov-action@v4
+        with:
+          file: ./coverage/lcov.info
+          flags: unittests
+          name: codecov-umbrella
+          fail_ci_if_error: false

.gitignore

@@ -44,6 +44,17 @@ temp/
 # WaveForge specific
 .wave/current-task.md
 
+# Husky
+.husky/_
+
+# Coverage reports
+coverage/
+*.lcov
+
+# Test results
+test-results/
+junit.xml
+
 # TypeScript cache
 *.tsbuildinfo
 

.husky/pre-commit

@@ -0,0 +1,11 @@
+#!/usr/bin/env sh
+. "$(dirname -- "$0")/_/husky.sh"
+
+# 运行 lint-staged 进行代码检查和格式化
+pnpm exec lint-staged
+
+# 运行类型检查
+pnpm run type-check
+
+# 运行所有测试
+pnpm test

.lintstagedrc.json

@@ -0,0 +1,5 @@
+{
+  "*.{ts,js,json,md}": ["prettier --write"],
+  "*.{ts,js}": ["eslint --fix"],
+  "src/**/*.ts": ["vitest related --run"]
+}

.prettierrc

@@ -5,4 +5,4 @@
   "printWidth": 80,
   "tabWidth": 2,
   "useTabs": false
-}
+}

CHANGLOG.md

@@ -17,11 +17,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Added
 
--   Initial project structure for the `WaveForge` methodology
--   Complete Chinese documentation (`.cursor-zh`) including roles, templates, rules, and examples.
--   Complete English translation (`.cursor-en`) of all methodology documents and examples.
+- Initial project structure for the `WaveForge` methodology
+- Complete Chinese documentation (`.cursor-zh`) including roles, templates, rules, and examples.
+- Complete English translation (`.cursor-en`) of all methodology documents and examples.
 
 ### Changed
 
--   Overhauled the main `README.md` for a more professional and visually appealing layout, including a new logo, badges, and a Star History chart.
--   Clarified the project's vision and its deep integration with the Cursor editor in the `README.md`.
+- Overhauled the main `README.md` for a more professional and visually appealing layout, including a new logo, badges, and a Star History chart.
+- Clarified the project's vision and its deep integration with the Cursor editor in the `README.md`.

README.md

@@ -25,15 +25,15 @@ WaveForge is in active design and development. The core design for its MCP-based
 ## ✨ Feature Highlights
 
 - **Intelligent Task System**
-    - **Two-Level Task Model**: Easily manage complex tasks with a structure of "Overall Plans" and "Specific Steps." Get a high-level overview while focusing on the immediate task, unifying macro and micro perspectives.
-    - **Automation-Driven Workflow**: When the last step of a plan is completed, the system automatically completes the plan and prompts the AI to generate steps for the next one. This "relay race" style of automation makes task progression seamless.
+  - **Two-Level Task Model**: Easily manage complex tasks with a structure of "Overall Plans" and "Specific Steps." Get a high-level overview while focusing on the immediate task, unifying macro and micro perspectives.
+  - **Automation-Driven Workflow**: When the last step of a plan is completed, the system automatically completes the plan and prompts the AI to generate steps for the next one. This "relay race" style of automation makes task progression seamless.
 - **Seamless Multi-Agent & Cross-Tool Collaboration**
-    - **Unique Project Identifier**: A revolutionary project-binding mechanism eliminates dependency on the current working directory (CWD) or editor workspace. No matter which tool (Cursor, VSCode, Kiro) or terminal you're in, all agents are guaranteed to collaborate within the same project context.
-    - **Real-Time Sync Guarantee**: Ensures data consistency and avoids state conflicts during parallel operations by multiple agents through file locking and state versioning.
+  - **Unique Project Identifier**: A revolutionary project-binding mechanism eliminates dependency on the current working directory (CWD) or editor workspace. No matter which tool (Cursor, VSCode, Kiro) or terminal you're in, all agents are guaranteed to collaborate within the same project context.
+  - **Real-Time Sync Guarantee**: Ensures data consistency and avoids state conflicts during parallel operations by multiple agents through file locking and state versioning.
 - **Developer Experience First**
-    - **Zero-Config Start & Self-Healing**: On its first run, it automatically and idempotently creates the necessary directory structure, templates, and configuration files. Ready to use out-of-the-box with no tedious setup.
-    - **One-Click Devlog Generation**: Upon task completion, a single confirmation automatically generates two styles of development logs from a template: `timeline` (a faithful record of the execution trace) and `narrative` (story-like storytelling). The logs aggregate Git commits, file changes, test results, and key discussions, making documentation effortless.
-    - **Comprehensive Traceability (Provenance)**: Automatically collects and organizes all task-related information, including Git commit ranges, PR/Issue links, requirement document paths, and meeting notes, to build a complete traceable information view.
+  - **Zero-Config Start & Self-Healing**: On its first run, it automatically and idempotently creates the necessary directory structure, templates, and configuration files. Ready to use out-of-the-box with no tedious setup.
+  - **One-Click Devlog Generation**: Upon task completion, a single confirmation automatically generates two styles of development logs from a template: `timeline` (a faithful record of the execution trace) and `narrative` (story-like storytelling). The logs aggregate Git commits, file changes, test results, and key discussions, making documentation effortless.
+  - **Comprehensive Traceability (Provenance)**: Automatically collects and organizes all task-related information, including Git commit ranges, PR/Issue links, requirement document paths, and meeting notes, to build a complete traceable information view.
 
 ## 🚀 Getting Started
 
@@ -44,32 +44,35 @@ For detailed instructions on installation, configuration, and usage, please see
 We are actively working on implementing the following core features. Feel free to join the discussion or contribute!
 
 ### Core Framework
+
 - [ ] **Project Binding & Environment Self-Healing**
-    - [ ] `project_bind`: Implement unique binding between a project and the MCP service, eliminating CWD dependency.
-    - [ ] `project_info`: Get information about the currently bound project.
-    - [ ] **Initialization & Self-Healing**: Automatically create the `.wave` directory structure, templates, and config files on the first run.
+  - [ ] `project_bind`: Implement unique binding between a project and the MCP service, eliminating CWD dependency.
+  - [ ] `project_info`: Get information about the currently bound project.
+  - [ ] **Initialization & Self-Healing**: Automatically create the `.wave` directory structure, templates, and config files on the first run.
 
 ### Task Management (MCP Tools)
+
 - [ ] **Two-Level Task Model**
-    - [ ] `current_task_init`: Initialize a new task, defining its `goal` and `overall_plan`.
-    - [ ] `current_task_modify`: Dynamically adjust tasks, including the `plan`, `steps`, `goal`, or adding `hints` for the AI.
-    - [ ] `current_task_update`: Update the status of a `plan` or `step`.
+  - [ ] `current_task_init`: Initialize a new task, defining its `goal` and `overall_plan`.
+  - [ ] `current_task_modify`: Dynamically adjust tasks, including the `plan`, `steps`, `goal`, or adding `hints` for the AI.
+  - [ ] `current_task_update`: Update the status of a `plan` or `step`.
 - [ ] **Task Lifecycle**
-    - [ ] `current_task_read`: Read the full context of the current task to sync between clients.
-    - [ ] `current_task_complete`: Mark a task as complete and trigger Devlog generation.
-    - [ ] `task_list`: View a list of historical tasks.
-    - [ ] `task_switch`: Switch between different tasks.
+  - [ ] `current_task_read`: Read the full context of the current task to sync between clients.
+  - [ ] `current_task_complete`: Mark a task as complete and trigger Devlog generation.
+  - [ ] `task_list`: View a list of historical tasks.
+  - [ ] `task_switch`: Switch between different tasks.
 - [ ] **Process Logging & Traceability**
-    - [ ] `current_task_log`: Log key discussions, decisions, or exceptions during development.
-    - [ ] **Provenance**: Automatically associate Git commits, PR/Issue links, and other artifacts.
+  - [ ] `current_task_log`: Log key discussions, decisions, or exceptions during development.
+  - [ ] **Provenance**: Automatically associate Git commits, PR/Issue links, and other artifacts.
 
 ### Automation & Doc Generation
+
 - [ ] **Automated Workflow**
-    - [ ] Automatically mark a plan as completed when all its steps are done.
-    - [ ] Prompt the AI to generate steps when starting a new plan.
+  - [ ] Automatically mark a plan as completed when all its steps are done.
+  - [ ] Prompt the AI to generate steps when starting a new plan.
 - [ ] **Devlog Auto-Generation**
-    - [ ] `devlog_prepare_context`: Prepare the context needed for Devlog generation.
-    - [ ] `generate_devlog`: Populate `timeline` and `narrative` devlogs from templates using task snapshots, logs, and Git history.
+  - [ ] `devlog_prepare_context`: Prepare the context needed for Devlog generation.
+  - [ ] `generate_devlog`: Populate `timeline` and `narrative` devlogs from templates using task snapshots, logs, and Git history.
 
 ## Workflow: From Idea to Implementation
 

README.zh-CN.md

@@ -26,15 +26,15 @@ WaveForge 正处于活跃的设计与开发阶段，核心的 MCP 任务管理
 ## ✨ 亮点功能
 
 - **智能任务系统**
-    - **双层级任务模型**：通过“整体计划 (Plan)”和“具体步骤 (Step)”的结构，轻松驾驭复杂任务。既能总览全局，又能聚焦当下，实现宏观与微观的统一。
-    - **自动化流程驱动**：当计划的最后一步完成时，系统会自动完成该计划并提示 AI 为下一个计划生成步骤。这种“接力棒”式的自动化，让任务推进如丝般顺滑。
+  - **双层级任务模型**：通过“整体计划 (Plan)”和“具体步骤 (Step)”的结构，轻松驾驭复杂任务。既能总览全局，又能聚焦当下，实现宏观与微观的统一。
+  - **自动化流程驱动**：当计划的最后一步完成时，系统会自动完成该计划并提示 AI 为下一个计划生成步骤。这种“接力棒”式的自动化，让任务推进如丝般顺滑。
 - **无缝的多 Agent 与跨工具协作**
-    - **项目唯一标识**：革命性的项目绑定机制，彻底摆脱对当前工作目录 (CWD) 或编辑器工作区的依赖。无论你在哪个工具（Cursor, VSCode, Kiro）或终端中，都能确保所有 Agent 在同一个项目上下文中协作，不再有“找不着北”的烦恼。
-    - **实时同步保障**：通过文件锁和状态版本控制，确保多个 Agent 并行操作时的数据一致性，避免状态冲突。
+  - **项目唯一标识**：革命性的项目绑定机制，彻底摆脱对当前工作目录 (CWD) 或编辑器工作区的依赖。无论你在哪个工具（Cursor, VSCode, Kiro）或终端中，都能确保所有 Agent 在同一个项目上下文中协作，不再有“找不着北”的烦恼。
+  - **实时同步保障**：通过文件锁和状态版本控制，确保多个 Agent 并行操作时的数据一致性，避免状态冲突。
 - **开发者体验至上**
-    - **零配置启动与自愈**：首次运行自动创建所需目录结构、模板和配置文件，并具备幂等性。开箱即用，无需繁琐配置。
-    - **一键生成 Devlog**：任务完成后，只需一步确认，即可基于模板自动生成两种风格的开发日志：`timeline`（忠实记录执行轨迹）和 `narrative`（故事化叙事）。日志内容自动聚合 Git 提交、文件变更、测试结果和关键讨论，将繁琐的文档工作化为无形。
-    - **全面的可追溯性 (Provenance)**：自动采集和整理与任务相关的一切信息，包括 Git 提交范围、PR/Issue 链接、需求文档路径、会议纪要等，构建完整的可溯源信息视图。
+  - **零配置启动与自愈**：首次运行自动创建所需目录结构、模板和配置文件，并具备幂等性。开箱即用，无需繁琐配置。
+  - **一键生成 Devlog**：任务完成后，只需一步确认，即可基于模板自动生成两种风格的开发日志：`timeline`（忠实记录执行轨迹）和 `narrative`（故事化叙事）。日志内容自动聚合 Git 提交、文件变更、测试结果和关键讨论，将繁琐的文档工作化为无形。
+  - **全面的可追溯性 (Provenance)**：自动采集和整理与任务相关的一切信息，包括 Git 提交范围、PR/Issue 链接、需求文档路径、会议纪要等，构建完整的可溯源信息视图。
 
 ## 🚀 快速上手
 
@@ -45,36 +45,39 @@ WaveForge 正处于活跃的设计与开发阶段，核心的 MCP 任务管理
 我们正在积极推进以下核心功能的实现，欢迎你加入讨论或贡献代码！
 
 ### 核心框架
+
 - [ ] **项目绑定与环境自愈**
-    - [ ] `project_bind`: 实现项目与 MCP 服务的唯一绑定，摆脱对 CWD 的依赖。
-    - [ ] `project_info`: 获取当前绑定的项目信息。
-    - [ ] **初始化与自愈**：首次运行时自动创建 `.wave` 目录结构、模板及配置文件。
+  - [ ] `project_bind`: 实现项目与 MCP 服务的唯一绑定，摆脱对 CWD 的依赖。
+  - [ ] `project_info`: 获取当前绑定的项目信息。
+  - [ ] **初始化与自愈**：首次运行时自动创建 `.wave` 目录结构、模板及配置文件。
 
 ### 任务管理工具 (MCP Tools)
+
 - [ ] **双层级任务模型**
-    - [ ] `current_task_init`: 初始化新任务，定义目标 (`goal`) 和宏观计划 (`overall_plan`)。
-    - [ ] `current_task_modify`: 动态调整任务，支持：
-      - `plan`: 整体调整计划。
-      - `steps`: 为当前计划生成或修改具体步骤。
-      - `goal`: 微调验收标准。
-      - `hints`: 为 AI 添加上下文提示。
-    - [ ] `current_task_update`: 更新计划 (`plan`) 或步骤 (`step`) 的状态。
+  - [ ] `current_task_init`: 初始化新任务，定义目标 (`goal`) 和宏观计划 (`overall_plan`)。
+  - [ ] `current_task_modify`: 动态调整任务，支持：
+    - `plan`: 整体调整计划。
+    - `steps`: 为当前计划生成或修改具体步骤。
+    - `goal`: 微调验收标准。
+    - `hints`: 为 AI 添加上下文提示。
+  - [ ] `current_task_update`: 更新计划 (`plan`) 或步骤 (`step`) 的状态。
 - [ ] **任务生命周期**
-    - [ ] `current_task_read`: 读取当前任务的完整上下文，便于在不同客户端间同步。
-    - [ ] `current_task_complete`: 标记任务完成，并触发开发日志 (Devlog) 生成。
-    - [ ] `task_list`: 查看历史任务列表。
-    - [ ] `task_switch`: 在不同任务间切换。
+  - [ ] `current_task_read`: 读取当前任务的完整上下文，便于在不同客户端间同步。
+  - [ ] `current_task_complete`: 标记任务完成，并触发开发日志 (Devlog) 生成。
+  - [ ] `task_list`: 查看历史任务列表。
+  - [ ] `task_switch`: 在不同任务间切换。
 - [ ] **过程记录与追溯**
-    - [ ] `current_task_log`: 记录开发过程中的关键讨论、决策或异常。
-    - [ ] **可追溯性 (Provenance)**: 自动关联 Git 提交、PR/Issue 链接等信息。
+  - [ ] `current_task_log`: 记录开发过程中的关键讨论、决策或异常。
+  - [ ] **可追溯性 (Provenance)**: 自动关联 Git 提交、PR/Issue 链接等信息。
 
 ### 自动化与文档生成
+
 - [ ] **自动化流程**
-    - [ ] 当计划的所有步骤完成后，自动将计划标记为完成。
-    - [ ] 当进入新计划时，提示 AI 生成具体步骤。
+  - [ ] 当计划的所有步骤完成后，自动将计划标记为完成。
+  - [ ] 当进入新计划时，提示 AI 生成具体步骤。
 - [ ] **Devlog 自动生成**
-    - [ ] `devlog_prepare_context`: 准备生成 Devlog 所需的上下文。
-    - [ ] `generate_devlog`: 基于模板，将任务快照、日志、Git 历史等信息填充为 `timeline` 和 `narrative` 两种风格的开发日志。
+  - [ ] `devlog_prepare_context`: 准备生成 Devlog 所需的上下文。
+  - [ ] `generate_devlog`: 基于模板，将任务快照、日志、Git 历史等信息填充为 `timeline` 和 `narrative` 两种风格的开发日志。
 
 ## 协作流程：从灵感到实现
 

USAGE.md

@@ -50,6 +50,7 @@ pnpm start
 Checks the server's health status, returning uptime, memory usage, etc.
 
 **Schema:**
+
 ```json
 {
   "name": "health",
@@ -67,6 +68,7 @@ Checks the server's health status, returning uptime, memory usage, etc.
 Tests the server connection and can optionally echo a message.
 
 **Schema:**
+
 ```json
 {
   "name": "ping",
@@ -96,7 +98,6 @@ Tests the server connection and can optionally echo a message.
 | `WF_DEVLOG_TEMPLATE` | Path to the Devlog template                     | `.wave/templates/devlog-template.md` |
 | `WF_DEBUG`           | Debug mode (`true` or `false`)                  | `false`                              |
 
-
 ### MCP Client Configuration
 
 Add the following to your MCP client configuration:
@@ -113,4 +114,4 @@ Add the following to your MCP client configuration:
     }
   }
 }
-```
+```