codexspec 0.4.0__tar.gz → 0.4.2__tar.gz

{codexspec-0.4.0 → codexspec-0.4.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: codexspec
-Version: 0.4.0
+Version: 0.4.2
 Summary: CodexSpec - A Spec-Driven Development (SDD) toolkit for Claude Code
 Project-URL: Homepage, https://github.com/Zts0hg/codexspec
 Project-URL: Repository, https://github.com/Zts0hg/codexspec

{codexspec-0.4.0 → codexspec-0.4.2}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "codexspec"
-version = "0.4.0"
+version = "0.4.2"
 description = "CodexSpec - A Spec-Driven Development (SDD) toolkit for Claude Code"
 readme = "README.md"
 requires-python = ">=3.11"

{codexspec-0.4.0 → codexspec-0.4.2}/scripts/python/README.md

@@ -14,20 +14,26 @@
 ### 1. 安装依赖
 
 ```bash
-pip install watchdog
+pip install watchdog python-dotenv
+```
+
+或使用 uv:
+
+```bash
+uv sync
 ```
 
 ### 2. 启动监控
 
 ```bash
 # 监控最近活跃的项目
-python claude_monitor.py --json | python notify_telegram.py
+uv run python claude_monitor.py --json | uv run python notify_telegram.py
 
 # 监控指定项目
-python claude_monitor.py --json -p ~/.claude/projects/-your-project | python notify_telegram.py
+uv run python claude_monitor.py --json -p ~/.claude/projects/-your-project | uv run python notify_telegram.py
 
 # 列出所有可用项目
-python claude_monitor.py --list
+uv run python claude_monitor.py --list
 ```
 
 ### 3. 后台运行
@@ -48,6 +54,7 @@ pkill -f claude_monitor.py
 |------|------|------------|
 | `TASK_COMPLETE` | 任务执行完成 | ✅ |
 | `USER_QUESTION` | Claude 需要用户输入 | ❓ |
+| `PENDING_PERMISSION` | Claude 等待工具权限确认 | ⏳ |
 | `ERROR_STOP` | 执行出错停止 | ❌ |
 
 ## 配置
@@ -65,6 +72,7 @@ export TELEGRAM_PROXY="http://127.0.0.1:7890"  # 可选
 # 通知开关
 export NOTIFY_ON_COMPLETE="true"   # 任务完成时通知
 export NOTIFY_ON_USER_QUESTION="true"  # 需要输入时通知
+export NOTIFY_ON_PENDING_PERMISSION="true"  # 等待权限确认时通知
 export NOTIFY_ON_ERROR="true"      # 出错时通知
 ```
 

{codexspec-0.4.0 → codexspec-0.4.2}/scripts/python/claude_monitor.py

@@ -30,6 +30,7 @@ class SessionStatus(Enum):
 
     STREAMING = "STREAMING"  # 流式输出中
     TOOL_USE = "TOOL_USE"  # 工具调用中
+    PENDING_PERMISSION = "PENDING_PERMISSION"  # 等待权限确认
     USER_QUESTION = "USER_QUESTION"  # 等待用户回答
     ERROR_STOP = "ERROR_STOP"  # 出错停止
     TASK_COMPLETE = "TASK_COMPLETE"  # 任务完成
@@ -44,6 +45,16 @@ class QuestionOption:
     description: str
 
 
+@dataclass
+class ToolUseInfo:
+    """工具调用信息"""
+
+    tool_name: str
+    tool_id: str
+    tool_input: dict[str, Any]
+    description: Optional[str] = None
+
+
 @dataclass
 class QuestionInfo:
     """用户询问的详细信息"""
@@ -74,6 +85,7 @@ class SessionState:
     last_output: Optional[str] = None
     is_executing: bool = False
     questions: list[QuestionInfo] = field(default_factory=list)
+    pending_tools: list[ToolUseInfo] = field(default_factory=list)
     error_info: Optional[ErrorInfo] = None
 
 
@@ -91,7 +103,7 @@ class StateDetector:
     @staticmethod
     def detect(
         message: dict,
-    ) -> tuple[SessionStatus, Optional[QuestionInfo], Optional[ErrorInfo]]:
+    ) -> tuple[SessionStatus, Optional[QuestionInfo], list[ToolUseInfo], Optional[ErrorInfo]]:
         """
         检测消息状态
 
@@ -99,35 +111,76 @@ class StateDetector:
             message: Claude API 响应消息
 
         Returns:
-            tuple: (状态, 问题信息, 错误信息)
+            tuple: (状态, 问题信息, 工具调用列表, 错误信息)
         """
         stop_reason = message.get("stop_reason")
         content = message.get("content", [])
 
         # 1. 流式输出中 (stop_reason=null)
         if stop_reason is None:
-            return SessionStatus.STREAMING, None, None
+            return SessionStatus.STREAMING, None, [], None
 
-        # 2. 检查是否为用户询问
+        # 2. 检查是否为用户询问 (AskUserQuestion 工具)
         question_info = StateDetector._extract_question(content)
         if question_info:
-            return SessionStatus.USER_QUESTION, question_info, None
+            return SessionStatus.USER_QUESTION, question_info, [], None
 
-        # 3. 检查是否出错
+        # 3. 检查是否为工具调用等待权限确认
+        if stop_reason == "tool_use":
+            # 提取所有工具调用信息
+            tool_infos = StateDetector._extract_tool_uses(content)
+            if tool_infos:
+                return SessionStatus.PENDING_PERMISSION, None, tool_infos, None
+            return SessionStatus.TOOL_USE, None, [], None
+
+        # 4. 检查是否出错
         error_info = StateDetector._extract_error(message)
         if error_info and stop_reason not in StateDetector.STOP_REASONS_COMPLETE:
             # 有错误且不是正常完成
             if stop_reason in ("refusal", "error") or (
-                stop_reason not in StateDetector.STOP_REASONS_COMPLETE and stop_reason != "tool_use"
+                stop_reason not in StateDetector.STOP_REASONS_COMPLETE
             ):
-                return SessionStatus.ERROR_STOP, None, error_info
-
-        # 4. 工具调用（非 AskUserQuestion）
-        if stop_reason == "tool_use":
-            return SessionStatus.TOOL_USE, None, None
+                return SessionStatus.ERROR_STOP, None, [], error_info
 
         # 5. 任务完成
-        return SessionStatus.TASK_COMPLETE, None, None
+        return SessionStatus.TASK_COMPLETE, None, [], None
+
+    @staticmethod
+    def _extract_tool_uses(content: list) -> list[ToolUseInfo]:
+        """
+        从 content 中提取所有 tool_use 信息
+
+        Args:
+            content: 消息内容列表
+
+        Returns:
+            ToolUseInfo 列表
+        """
+        tool_infos = []
+        if not content:
+            return tool_infos
+
+        for item in content:
+            if item.get("type") != "tool_use":
+                continue
+
+            tool_name = item.get("name", "")
+            tool_id = item.get("id", "")
+            tool_input = item.get("input", {})
+
+            # 提取描述（如果存在）
+            description = tool_input.get("description") if isinstance(tool_input, dict) else None
+
+            tool_infos.append(
+                ToolUseInfo(
+                    tool_name=tool_name,
+                    tool_id=tool_id,
+                    tool_input=tool_input,
+                    description=description,
+                )
+            )
+
+        return tool_infos
 
     @staticmethod
     def _extract_question(content: list) -> Optional[QuestionInfo]:
@@ -237,6 +290,42 @@ class OutputFormatter:
 
     SEPARATOR = "=" * 60
 
+    @staticmethod
+    def format_pending_permission(session_id: str, tools: list[ToolUseInfo]) -> str:
+        """
+        格式化等待权限确认的输出
+
+        Args:
+            session_id: Session ID
+            tools: 工具调用列表
+
+        Returns:
+            格式化的输出字符串
+        """
+        lines = [
+            "",
+            OutputFormatter.SEPARATOR,
+            f"[Session: {session_id[:8]}] Status: PENDING_PERMISSION",
+            OutputFormatter.SEPARATOR,
+            "Tools waiting for permission:",
+        ]
+
+        for i, tool in enumerate(tools, 1):
+            lines.append(f"  [{i}] {tool.tool_name}")
+            if tool.description:
+                lines.append(f"      Description: {tool.description}")
+            # 显示工具输入参数
+            if tool.tool_input:
+                lines.append("      Input:")
+                for key, value in tool.tool_input.items():
+                    value_str = str(value)
+                    if len(value_str) > 200:
+                        value_str = value_str[:200] + "..."
+                    lines.append(f"        {key}: {value_str}")
+
+        lines.append(OutputFormatter.SEPARATOR)
+        return "\n".join(lines)
+
     @staticmethod
     def format_user_question(session_id: str, questions: list[QuestionInfo]) -> str:
         """
@@ -351,12 +440,14 @@ class ClaudeSessionMonitor(FileSystemEventHandler):
         on_complete: Optional[callable] = None,
         on_user_question: Optional[callable] = None,
         on_error_stop: Optional[callable] = None,
+        on_pending_permission: Optional[callable] = None,
     ):
         self.project_dir = project_dir or self._detect_current_project()
         self.quiet = quiet
         self.on_complete = on_complete
         self.on_user_question = on_user_question
         self.on_error_stop = on_error_stop
+        self.on_pending_permission = on_pending_permission
         self.sessions: dict[str, SessionState] = {}
         self._file_positions: dict[str, int] = {}  # 记录每个文件的读取位置
         self._observer: Optional[Observer] = None
@@ -473,7 +564,7 @@ class ClaudeSessionMonitor(FileSystemEventHandler):
         text_content = self._extract_text(content)
 
         # 使用 StateDetector 检测状态
-        detected_status, question_info, error_info = StateDetector.detect(message)
+        detected_status, question_info, tool_infos, error_info = StateDetector.detect(message)
 
         # 更新 session 状态
         if session_id not in self.sessions:
@@ -487,12 +578,13 @@ class ClaudeSessionMonitor(FileSystemEventHandler):
         state.last_output = text_content
         state.status = detected_status
 
-        # 根据检测结果更新问题/错误信息
+        # 根据检测结果更新问题/错误/工具信息
         if question_info:
             state.questions = [question_info]
         else:
             state.questions = []
 
+        state.pending_tools = tool_infos
         state.error_info = error_info
 
         # 判断是否正在执行
@@ -509,8 +601,12 @@ class ClaudeSessionMonitor(FileSystemEventHandler):
 
         # 触发状态变化回调
         if not silent:
+            # 检测等待权限确认状态
+            if detected_status == SessionStatus.PENDING_PERMISSION:
+                self._on_pending_permission(session_id, state.pending_tools)
+
             # 检测用户询问状态
-            if detected_status == SessionStatus.USER_QUESTION:
+            elif detected_status == SessionStatus.USER_QUESTION:
                 self._on_user_question(session_id, state.questions)
 
             # 检测错误停止状态
@@ -595,6 +691,21 @@ class ClaudeSessionMonitor(FileSystemEventHandler):
         output = OutputFormatter.format_error_stop(session_id, error_info)
         print(output)
 
+    def _on_pending_permission(self, session_id: str, tools: list[ToolUseInfo]):
+        """等待权限确认时的回调"""
+        # 调用自定义回调（即使在 quiet 模式下也调用）
+        if self.on_pending_permission:
+            self.on_pending_permission(session_id, tools)
+            return
+
+        # quiet 模式下不输出默认格式
+        if self.quiet:
+            return
+
+        # 默认输出格式
+        output = OutputFormatter.format_pending_permission(session_id, tools)
+        print(output)
+
     def _print_completion(self, session_id: str, state: SessionState):
         """打印完成信息"""
         print(f"\n{'=' * 60}")
@@ -786,6 +897,7 @@ Examples:
     on_complete = None
     on_user_question = None
     on_error_stop = None
+    on_pending_permission = None
 
     if args.json:
 
@@ -830,9 +942,27 @@ Examples:
             }
             print(json.dumps(output, ensure_ascii=False), flush=True)
 
+        def json_pending_permission_callback(session_id: str, tools: list[ToolUseInfo]):
+            output = {
+                "session_id": session_id,
+                "status": SessionStatus.PENDING_PERMISSION.value,
+                "timestamp": time.time(),
+                "tools": [
+                    {
+                        "name": t.tool_name,
+                        "id": t.tool_id,
+                        "input": t.tool_input,
+                        "description": t.description,
+                    }
+                    for t in tools
+                ],
+            }
+            print(json.dumps(output, ensure_ascii=False), flush=True)
+
         on_complete = json_complete_callback
         on_user_question = json_user_question_callback
         on_error_stop = json_error_stop_callback
+        on_pending_permission = json_pending_permission_callback
 
     try:
         monitor = ClaudeSessionMonitor(
@@ -841,6 +971,7 @@ Examples:
             on_complete=on_complete,
             on_user_question=on_user_question,
             on_error_stop=on_error_stop,
+            on_pending_permission=on_pending_permission,
         )
         monitor.start(json_mode=args.json)
     except FileNotFoundError as e:

{codexspec-0.4.0 → codexspec-0.4.2}/scripts/python/notify_telegram.py

@@ -14,6 +14,11 @@ import urllib.error
 import urllib.request
 from typing import Optional
 
+from dotenv import load_dotenv
+
+# 从 .env 文件加载环境变量
+load_dotenv()
+
 # ============================================================================
 # 配置 (可从环境变量覆盖)
 # ============================================================================
@@ -26,6 +31,7 @@ PROXY = os.environ.get("TELEGRAM_PROXY", "http://127.0.0.1:7890")
 NOTIFY_ON_COMPLETE = os.environ.get("NOTIFY_ON_COMPLETE", "true").lower() == "true"
 NOTIFY_ON_USER_QUESTION = os.environ.get("NOTIFY_ON_USER_QUESTION", "true").lower() == "true"
 NOTIFY_ON_ERROR = os.environ.get("NOTIFY_ON_ERROR", "true").lower() == "true"
+NOTIFY_ON_PENDING_PERMISSION = os.environ.get("NOTIFY_ON_PENDING_PERMISSION", "true").lower() == "true"
 
 
 # ============================================================================
@@ -173,6 +179,39 @@ def format_error(data: dict) -> str:
     return "\n".join(lines)
 
 
+def format_pending_permission(data: dict) -> str:
+    """格式化工具权限询问通知"""
+    session_id = data.get("session_id", "unknown")[:8]
+    tools = data.get("tools", [])
+
+    lines = [
+        "⏳ <b>Claude Code 等待权限确认</b>",
+        "",
+        f"📌 Session: <code>{session_id}</code>",
+    ]
+
+    for i, tool in enumerate(tools, 1):
+        name = tool.get("name", "unknown")
+        description = tool.get("description", "")
+        tool_input = tool.get("input", {})
+
+        lines.append("")
+        lines.append(f"🔧 <b>工具 {i}:</b> {escape_html(name)}")
+
+        if description:
+            lines.append(f"📝 {escape_html(description)}")
+
+        if tool_input:
+            lines.append("<b>参数:</b>")
+            for key, value in tool_input.items():
+                value_str = str(value)
+                if len(value_str) > 100:
+                    value_str = value_str[:100] + "..."
+                lines.append(f"  • {key}: {escape_html(value_str)}")
+
+    return "\n".join(lines)
+
+
 # ============================================================================
 # 主循环
 # ============================================================================
@@ -201,12 +240,26 @@ def process_event(line: str) -> Optional[str]:
         return format_user_question(data)
     elif status == "ERROR_STOP" and NOTIFY_ON_ERROR:
         return format_error(data)
+    elif status == "PENDING_PERMISSION" and NOTIFY_ON_PENDING_PERMISSION:
+        return format_pending_permission(data)
 
     return None
 
 
 def main():
     """主循环 - 从 stdin 读取 JSON 行并发送通知"""
+    # 检查必需的凭证
+    missing = []
+    if not BOT_TOKEN:
+        missing.append("TELEGRAM_BOT_TOKEN")
+    if not CHAT_ID:
+        missing.append("TELEGRAM_CHAT_ID")
+
+    if missing:
+        print(f"[ERROR] Missing required environment variables: {', '.join(missing)}", file=sys.stderr)
+        print("[ERROR] Please set these in your .env file or environment", file=sys.stderr)
+        sys.exit(1)
+
     print("[INFO] Telegram Notifier started", file=sys.stderr)
     print(f"[INFO] Chat ID: {CHAT_ID}", file=sys.stderr)
     print(f"[INFO] Proxy: {PROXY}", file=sys.stderr)

{codexspec-0.4.0 → codexspec-0.4.2}/src/codexspec/__init__.py

@@ -35,7 +35,7 @@ from .i18n import (
 )
 
 # Version info
-__version__ = "0.2.2"
+__version__ = "0.4.1"
 __author__ = "CodexSpec Team"
 
 # Constitution file path constants

{codexspec-0.4.0 → codexspec-0.4.2}/src/codexspec/translator.py

@@ -21,12 +21,20 @@ def get_translations_dir() -> Path:
     Returns:
         Path to templates/translations directory
     """
-    # When installed via uv/pip
-    package_dir = Path(__file__).parent.parent.parent / "templates" / "translations"
-    if package_dir.exists():
-        return package_dir
-    # Development fallback
-    return Path(__file__).parent.parent.parent / "templates" / "translations"
+    # Path 1: Wheel install - templates packaged inside codexspec package
+    # __file__ = site-packages/codexspec/translator.py
+    # parent / "templates" / "translations" = site-packages/codexspec/templates/translations
+    installed_translations = Path(__file__).parent / "templates" / "translations"
+    if installed_translations.exists():
+        return installed_translations
+
+    # Path 2: Development/editable install - templates in project root
+    dev_translations = Path(__file__).parent.parent.parent / "templates" / "translations"
+    if dev_translations.exists():
+        return dev_translations
+
+    # Path 3: Fallback - return the installed path (for error messages)
+    return installed_translations
 
 
 def get_translation_cache_path(language: str) -> Path:

{codexspec-0.4.0 → codexspec-0.4.2}/templates/translations/de.json

@@ -1,13 +1,15 @@
 {
   "constitution": {
     "description": "Projektverfassung aus interaktiven oder bereitgestellten Prinzipien erstellen oder aktualisieren und sicherstellen, dass alle abhängigen Vorlagen synchronisiert bleiben.",
-    "argument-hint": "[quick|deep | Projektprinzipien] (optional)\n\nDieser Befehl erstellt/aktualisiert die Projektverfassung unter .codexspec/memory/constitution.md.\n\nDrei Verwendungsmöglichkeiten:\n1. Ohne Argumente → Interaktiver Modus: Explorationstiefe wählen (quick/deep)\n2. quick → Leichte Exploration: Konfigurationsdateien + README + Haupteinstiegspunkte (~5-10 Dateien)\n3. deep → Vollständige Exploration: alles oben + Quellcode-Analyse + Architektur-Patterns\n4. <Beschreibung> → Exploration überspringen, Prinzipien direkt verwenden"
+    "argument-hint": "[quick|deep | Projektprinzipien] (optional)\n\nDieser Befehl erstellt/aktualisiert die Projektverfassung unter .codexspec/memory/constitution.md.\n\nDrei Verwendungsmöglichkeiten:\n1. Ohne Argumente → Interaktiver Modus: Explorationstiefe wählen (quick/deep)\n2. quick → Leichte Exploration: Konfigurationsdateien + README + Haupteinstiegspunkte (~5-10 Dateien)\n3. deep → Vollständige Exploration: alles oben + Quellcode-Analyse + Architektur-Patterns\n4. <Beschreibung> → Exploration überspringen, Prinzipien direkt verwenden\n\nBeispiele:\n  /codexspec.constitution\n  /codexspec.constitution quick\n  /codexspec.constitution deep\n  /codexspec.constitution Python FastAPI Backend mit pytest, Fokus auf Typsicherheit"
   },
   "specify": {
-    "description": "Anforderungen durch interaktives Q&A klären und erste Ideen erkunden und verfeinern"
+    "description": "Anforderungen durch interaktives Q&A klären und erste Ideen erkunden und verfeinern",
+    "argument-hint": "Beschreiben Sie Ihre ursprüngliche Idee oder Anforderung"
   },
   "clarify": {
-    "description": "Unklare Bereiche in der Funktionsspezifikation durch gezielte Fragen vor der technischen Planung identifizieren"
+    "description": "Unklare Bereiche in der Funktionsspezifikation durch gezielte Fragen vor der technischen Planung identifizieren",
+    "argument-hint": "[pfad_zu_spec.md] (optional, standardmäßig .codexspec/specs/{feature-id}/)"
   },
   "analyze": {
     "description": "Nicht-destruktive Konsistenz- und Qualitätsanalyse zwischen Artefakten spec.md, plan.md und tasks.md durchführen"
@@ -19,39 +21,49 @@
     "description": "spec.md-Dokument generieren nachdem Anforderungen geklärt sind"
   },
   "spec-to-plan": {
-    "description": "Funktionsspezifikation in technischen Implementierungsplan umwandeln"
+    "description": "Funktionsspezifikation in technischen Implementierungsplan umwandeln",
+    "argument-hint": ".codexspec/specs/{feature-id}/spec.md"
   },
   "plan-to-tasks": {
-    "description": "Technischen Implementierungsplan in ausführbare Aufgaben zerlegen"
+    "description": "Technischen Implementierungsplan in ausführbare Aufgaben zerlegen",
+    "argument-hint": "[spec.md_pfad plan.md_pfad] (optional, standardmäßig .codexspec/specs/{feature-id}/)"
   },
   "review-spec": {
-    "description": "Vollständigkeit, Klarheit und Qualität der Funktionsspezifikation überprüfen und validieren"
+    "description": "Vollständigkeit, Klarheit und Qualität der Funktionsspezifikation überprüfen und validieren",
+    "argument-hint": "[spec.md_pfad] (optional, standardmäßig .codexspec/specs/{feature-id}/)"
   },
   "review-plan": {
-    "description": "Machbarkeit und Konsistenz des technischen Implementierungsplans überprüfen und validieren"
+    "description": "Machbarkeit und Konsistenz des technischen Implementierungsplans überprüfen und validieren",
+    "argument-hint": "[plan.md_pfad] (optional, standardmäßig .codexspec/specs/{feature-id}/)"
   },
   "review-tasks": {
-    "description": "Vollständigkeit, Reihenfolge und TDD-Konformität der Aufgabenaufschlüsselung überprüfen und validieren"
+    "description": "Vollständigkeit, Reihenfolge und TDD-Konformität der Aufgabenaufschlüsselung überprüfen und validieren",
+    "argument-hint": "[tasks.md_pfad] (optional, standardmäßig .codexspec/specs/{feature-id}/)"
   },
   "implement-tasks": {
-    "description": "Implementierungsaufgaben mit bedingtem TDD-Workflow ausführen (TDD für Code, direkte Implementierung für Docs/Config)"
+    "description": "Implementierungsaufgaben mit bedingtem TDD-Workflow ausführen (TDD für Code, direkte Implementierung für Docs/Config)",
+    "argument-hint": "[tasks_pfad] | [spec_pfad plan_pfad tasks_pfad]"
   },
   "tasks-to-issues": {
     "description": "Bestehende Aufgaben in umsetzbare GitHub Issues für diese Funktionalität umwandeln"
   },
   "commit": {
-    "description": "Conventional Commits konforme Commit-Nachrichten basierend auf Git-Status und Sitzungskontext generieren und ausführen"
+    "description": "Conventional Commits konforme Commit-Nachrichten basierend auf Git-Status und Sitzungskontext generieren und ausführen",
+    "argument-hint": "[-p] -p verwenden um nur die Nachricht ohne Commit voranzuzeigen"
   },
   "commit-staged": {
-    "description": "Gestagte Git-Änderungen analysieren und Conventional Commits konforme Commit-Nachricht generieren"
+    "description": "Gestagte Git-Änderungen analysieren und Conventional Commits konforme Commit-Nachricht generieren",
+    "argument-hint": "[-p] -p verwenden um nur die Nachricht ohne Commit voranzuzeigen"
   },
   "pr": {
     "description": "Strukturierte Pull Request (GitHub) oder Merge Request (GitLab) Beschreibung basierend auf git diff und optionaler spec.md-Integration generieren"
   },
   "check-i18n-semantics": {
-    "description": "Semantische Konsistenz und Qualität mehrsprachiger Dokumentation prüfen"
+    "description": "Semantische Konsistenz und Qualität mehrsprachiger Dokumentation prüfen",
+    "argument-hint": "[quelldatei] [--lang <sprache>] [--strict]"
   },
   "translate-docs": {
-    "description": "Projektdokumentation in die angegebene Sprache übersetzen"
+    "description": "Projektdokumentation in die angegebene Sprache übersetzen",
+    "argument-hint": "--lang <sprachcodes> (z.B. 'zh,ja,ko') oder 'all' für alle Sprachen"
   }
 }

{codexspec-0.4.0 → codexspec-0.4.2}/templates/translations/es.json

@@ -1,13 +1,15 @@
 {
   "constitution": {
     "description": "Crear o actualizar la constitución del proyecto a partir de entradas interactivas o principios proporcionados, asegurando que todas las plantillas dependientes permanezcan sincronizadas.",
-    "argument-hint": "[quick|deep | principios del proyecto] (opcional)\n\nEste comando crea/actualiza la constitución del proyecto en .codexspec/memory/constitution.md.\n\nTres formas de uso:\n1. Sin argumentos → Modo interactivo: elegir profundidad de exploración (quick/deep)\n2. quick → Exploración ligera: archivos de configuración + README + puntos de entrada principales (~5-10 archivos)\n3. deep → Exploración completa: todo lo anterior + análisis de código fuente + patrones de arquitectura\n4. <descripción> → Omitir exploración, usar tus principios directamente"
+    "argument-hint": "[quick|deep | principios del proyecto] (opcional)\n\nEste comando crea/actualiza la constitución del proyecto en .codexspec/memory/constitution.md.\n\nTres formas de uso:\n1. Sin argumentos → Modo interactivo: elegir profundidad de exploración (quick/deep)\n2. quick → Exploración ligera: archivos de configuración + README + puntos de entrada principales (~5-10 archivos)\n3. deep → Exploración completa: todo lo anterior + análisis de código fuente + patrones de arquitectura\n4. <descripción> → Omitir exploración, usar tus principios directamente\n\nEjemplos:\n  /codexspec.constitution\n  /codexspec.constitution quick\n  /codexspec.constitution deep\n  /codexspec.constitution Python FastAPI backend con pytest, enfocado en seguridad de tipos"
   },
   "specify": {
-    "description": "Aclarar requisitos mediante Q&A interactivo para explorar y refinar ideas iniciales"
+    "description": "Aclarar requisitos mediante Q&A interactivo para explorar y refinar ideas iniciales",
+    "argument-hint": "Describe tu idea inicial o requisito"
   },
   "clarify": {
-    "description": "Identificar áreas poco claras en la especificación funcional mediante preguntas dirigidas antes de la planificación técnica"
+    "description": "Identificar áreas poco claras en la especificación funcional mediante preguntas dirigidas antes de la planificación técnica",
+    "argument-hint": "[ruta_a_spec.md] (opcional, por defecto .codexspec/specs/{feature-id}/)"
   },
   "analyze": {
     "description": "Realizar análisis no destructivo de consistencia y calidad entre artefactos spec.md, plan.md y tasks.md"
@@ -19,39 +21,49 @@
     "description": "Generar documento spec.md después de que los requisitos estén claros"
   },
   "spec-to-plan": {
-    "description": "Convertir especificación funcional en plan de implementación técnica"
+    "description": "Convertir especificación funcional en plan de implementación técnica",
+    "argument-hint": ".codexspec/specs/{feature-id}/spec.md"
   },
   "plan-to-tasks": {
-    "description": "Descomponer plan de implementación técnica en tareas ejecutables"
+    "description": "Descomponer plan de implementación técnica en tareas ejecutables",
+    "argument-hint": "[ruta_a_spec.md ruta_a_plan.md] (opcional, por defecto .codexspec/specs/{feature-id}/)"
   },
   "review-spec": {
-    "description": "Revisar y validar completitud, claridad y calidad de la especificación funcional"
+    "description": "Revisar y validar completitud, claridad y calidad de la especificación funcional",
+    "argument-hint": "[ruta_a_spec.md] (opcional, por defecto .codexspec/specs/{feature-id}/)"
   },
   "review-plan": {
-    "description": "Revisar y validar viabilidad y consistencia del plan de implementación técnica"
+    "description": "Revisar y validar viabilidad y consistencia del plan de implementación técnica",
+    "argument-hint": "[ruta_a_plan.md] (opcional, por defecto .codexspec/specs/{feature-id}/)"
   },
   "review-tasks": {
-    "description": "Revisar y validar completitud, orden y cumplimiento TDD de la descomposición de tareas"
+    "description": "Revisar y validar completitud, orden y cumplimiento TDD de la descomposición de tareas",
+    "argument-hint": "[ruta_a_tasks.md] (opcional, por defecto .codexspec/specs/{feature-id}/)"
   },
   "implement-tasks": {
-    "description": "Ejecutar tareas de implementación con flujo de trabajo TDD condicional (TDD para código, implementación directa para docs/config)"
+    "description": "Ejecutar tareas de implementación con flujo de trabajo TDD condicional (TDD para código, implementación directa para docs/config)",
+    "argument-hint": "[ruta_tasks] | [ruta_spec ruta_plan ruta_tasks]"
   },
   "tasks-to-issues": {
     "description": "Convertir tareas existentes en GitHub Issues accionables para esta funcionalidad"
   },
   "commit": {
-    "description": "Generar y ejecutar mensajes de commit conformes a Conventional Commits basados en estado git y contexto de sesión"
+    "description": "Generar y ejecutar mensajes de commit conformes a Conventional Commits basados en estado git y contexto de sesión",
+    "argument-hint": "[-p] Usa -p para solo previsualizar el mensaje sin hacer commit"
   },
   "commit-staged": {
-    "description": "Analizar cambios git preparados y generar mensaje de commit conforme a Conventional Commits"
+    "description": "Analizar cambios git preparados y generar mensaje de commit conforme a Conventional Commits",
+    "argument-hint": "[-p] Usa -p para solo previsualizar el mensaje sin hacer commit"
   },
   "pr": {
     "description": "Generar descripción estructurada de Pull Request (GitHub) o Merge Request (GitLab) basada en git diff e integración opcional de spec.md"
   },
   "check-i18n-semantics": {
-    "description": "Verificar consistencia semántica y calidad de documentación multilingüe"
+    "description": "Verificar consistencia semántica y calidad de documentación multilingüe",
+    "argument-hint": "[archivo_fuente] [--lang <idioma>] [--strict]"
   },
   "translate-docs": {
-    "description": "Traducir documentación del proyecto al idioma especificado"
+    "description": "Traducir documentación del proyecto al idioma especificado",
+    "argument-hint": "--lang <códigos_idioma> (ej: 'zh,ja,ko') o 'all' para todos los idiomas"
   }
 }

{codexspec-0.4.0 → codexspec-0.4.2}/templates/translations/fr.json

@@ -1,13 +1,15 @@
 {
   "constitution": {
     "description": "Créer ou mettre à jour la constitution du projet à partir d'entrées interactives ou de principes fournis, en garantissant la synchronisation de tous les modèles dépendants.",
-    "argument-hint": "[quick|deep | principes du projet] (optionnel)\n\nCette commande crée/met à jour la constitution du projet dans .codexspec/memory/constitution.md.\n\nTrois modes d'utilisation :\n1. Sans arguments → Mode interactif : choisir la profondeur d'exploration (quick/deep)\n2. quick → Exploration légère : fichiers de configuration + README + points d'entrée principaux (~5-10 fichiers)\n3. deep → Exploration complète : tout ce qui précède + analyse du code source + patterns d'architecture\n4. <description> → Ignorer l'exploration, utiliser vos principes directement"
+    "argument-hint": "[quick|deep | principes du projet] (optionnel)\n\nCette commande crée/met à jour la constitution du projet dans .codexspec/memory/constitution.md.\n\nTrois modes d'utilisation :\n1. Sans arguments → Mode interactif : choisir la profondeur d'exploration (quick/deep)\n2. quick → Exploration légère : fichiers de configuration + README + points d'entrée principaux (~5-10 fichiers)\n3. deep → Exploration complète : tout ce qui précède + analyse du code source + patterns d'architecture\n4. <description> → Ignorer l'exploration, utiliser vos principes directement\n\nExemples :\n  /codexspec.constitution\n  /codexspec.constitution quick\n  /codexspec.constitution deep\n  /codexspec.constitution Python FastAPI backend avec pytest, axé sur la sécurité des types"
   },
   "specify": {
-    "description": "Clarifier les exigences via Q&R interactif pour explorer et affiner les idées initiales"
+    "description": "Clarifier les exigences via Q&R interactif pour explorer et affiner les idées initiales",
+    "argument-hint": "Décrivez votre idée initiale ou vos exigences"
   },
   "clarify": {
-    "description": "Identifier les zones floues dans la spécification fonctionnelle via des questions ciblées avant la planification technique"
+    "description": "Identifier les zones floues dans la spécification fonctionnelle via des questions ciblées avant la planification technique",
+    "argument-hint": "[chemin_vers_spec.md] (optionnel, par défaut .codexspec/specs/{feature-id}/)"
   },
   "analyze": {
     "description": "Effectuer une analyse non destructive de cohérence et qualité entre artefacts spec.md, plan.md et tasks.md"
@@ -19,39 +21,49 @@
     "description": "Générer le document spec.md une fois les exigences clarifiées"
   },
   "spec-to-plan": {
-    "description": "Convertir la spécification fonctionnelle en plan d'implémentation technique"
+    "description": "Convertir la spécification fonctionnelle en plan d'implémentation technique",
+    "argument-hint": ".codexspec/specs/{feature-id}/spec.md"
   },
   "plan-to-tasks": {
-    "description": "Décomposer le plan d'implémentation technique en tâches exécutables"
+    "description": "Décomposer le plan d'implémentation technique en tâches exécutables",
+    "argument-hint": "[chemin_spec.md chemin_plan.md] (optionnel, par défaut .codexspec/specs/{feature-id}/)"
   },
   "review-spec": {
-    "description": "Réviser et valider complétude, clarté et qualité de la spécification fonctionnelle"
+    "description": "Réviser et valider complétude, clarté et qualité de la spécification fonctionnelle",
+    "argument-hint": "[chemin_spec.md] (optionnel, par défaut .codexspec/specs/{feature-id}/)"
   },
   "review-plan": {
-    "description": "Réviser et valider faisabilité et cohérence du plan d'implémentation technique"
+    "description": "Réviser et valider faisabilité et cohérence du plan d'implémentation technique",
+    "argument-hint": "[chemin_plan.md] (optionnel, par défaut .codexspec/specs/{feature-id}/)"
   },
   "review-tasks": {
-    "description": "Réviser et valider complétude, ordonnancement et conformité TDD de la décomposition des tâches"
+    "description": "Réviser et valider complétude, ordonnancement et conformité TDD de la décomposition des tâches",
+    "argument-hint": "[chemin_tasks.md] (optionnel, par défaut .codexspec/specs/{feature-id}/)"
   },
   "implement-tasks": {
-    "description": "Exécuter les tâches d'implémentation avec workflow TDD conditionnel (TDD pour code, implémentation directe pour docs/config)"
+    "description": "Exécuter les tâches d'implémentation avec workflow TDD conditionnel (TDD pour code, implémentation directe pour docs/config)",
+    "argument-hint": "[chemin_tasks] | [chemin_spec chemin_plan chemin_tasks]"
   },
   "tasks-to-issues": {
     "description": "Convertir les tâches existantes en GitHub Issues actionnables pour cette fonctionnalité"
   },
   "commit": {
-    "description": "Générer et exécuter des messages de commit conformes à Conventional Commits basés sur l'état git et le contexte de session"
+    "description": "Générer et exécuter des messages de commit conformes à Conventional Commits basés sur l'état git et le contexte de session",
+    "argument-hint": "[-p] Utilisez -p pour seulement prévisualiser le message sans commettre"
   },
   "commit-staged": {
-    "description": "Analyser les changements git stagés et générer un message de commit conforme à Conventional Commits"
+    "description": "Analyser les changements git stagés et générer un message de commit conforme à Conventional Commits",
+    "argument-hint": "[-p] Utilisez -p pour seulement prévisualiser le message sans commettre"
   },
   "pr": {
     "description": "Générer une description structurée de Pull Request (GitHub) ou Merge Request (GitLab) basée sur git diff et intégration optionnelle de spec.md"
   },
   "check-i18n-semantics": {
-    "description": "Vérifier la cohérence sémantique et la qualité de la documentation multilingue"
+    "description": "Vérifier la cohérence sémantique et la qualité de la documentation multilingue",
+    "argument-hint": "[fichier_source] [--lang <langue>] [--strict]"
   },
   "translate-docs": {
-    "description": "Traduire la documentation du projet dans la langue spécifiée"
+    "description": "Traduire la documentation du projet dans la langue spécifiée",
+    "argument-hint": "--lang <codes_langue> (ex: 'zh,ja,ko') ou 'all' pour toutes les langues"
   }
 }

{codexspec-0.4.0 → codexspec-0.4.2}/templates/translations/ja.json

@@ -1,13 +1,15 @@
 {
   "constitution": {
     "description": "対話型または提供された原則入力からプロジェクト憲法を作成または更新し、依存テンプレートの同期を保ちます。",
-    "argument-hint": "[quick|deep | プロジェクト原則] (オプション)\n\nこのコマンドは .codexspec/memory/constitution.md にプロジェクト憲法を作成/更新します。\n\n3つの使用方法：\n1. 引数なし → 対話モード：探索深度を選択 (quick/deep)\n2. quick → 軽量探索：設定ファイル + README + コアエントリーポイント (~5-10ファイル)\n3. deep → 完全探索：上記 + ソースコード分析 + アーキテクチャパターン\n4. <説明> → 探索をスキップし、あなたの原則を直接使用"
+    "argument-hint": "[quick|deep | プロジェクト原則] (オプション)\n\nこのコマンドは .codexspec/memory/constitution.md にプロジェクト憲法を作成/更新します。\n\n3つの使用方法：\n1. 引数なし → 対話モード：探索深度を選択 (quick/deep)\n2. quick → 軽量探索：設定ファイル + README + コアエントリーポイント (~5-10ファイル)\n3. deep → 完全探索：上記 + ソースコード分析 + アーキテクチャパターン\n4. <説明> → 探索をスキップし、あなたの原則を直接使用\n\n例：\n  /codexspec.constitution\n  /codexspec.constitution quick\n  /codexspec.constitution deep\n  /codexspec.constitution Python FastAPI バックエンドで pytest 使用、型安全性重視"
   },
   "specify": {
-    "description": "対話型Q&Aを通じて要件を明確化し、初期アイデアを探索・洗練"
+    "description": "対話型Q&Aを通じて要件を明確化し、初期アイデアを探索・洗練",
+    "argument-hint": "初期アイデアや要件を記述してください"
   },
   "clarify": {
-    "description": "技術計画前にターゲットを絞った質問で機能仕様の不明確な領域を特定"
+    "description": "技術計画前にターゲットを絞った質問で機能仕様の不明確な領域を特定",
+    "argument-hint": "[spec.md へのパス] (オプション、デフォルトは .codexspec/specs/{feature-id}/)"
   },
   "analyze": {
     "description": "spec.md、plan.md、tasks.md間の整合性と品質を非破壊的に分析"
@@ -19,39 +21,49 @@
     "description": "要件が明確になった後にspec.mdドキュメントを生成"
   },
   "spec-to-plan": {
-    "description": "機能仕様を技術実装計画に変換"
+    "description": "機能仕様を技術実装計画に変換",
+    "argument-hint": ".codexspec/specs/{feature-id}/spec.md"
   },
   "plan-to-tasks": {
-    "description": "技術実装計画を実行可能なタスクに分解"
+    "description": "技術実装計画を実行可能なタスクに分解",
+    "argument-hint": "[spec.md へのパス plan.md へのパス] (オプション、デフォルトは .codexspec/specs/{feature-id}/)"
   },
   "review-spec": {
-    "description": "機能仕様の完全性、明確性、品質をレビュー・検証"
+    "description": "機能仕様の完全性、明確性、品質をレビュー・検証",
+    "argument-hint": "[spec.md へのパス] (オプション、デフォルトは .codexspec/specs/{feature-id}/)"
   },
   "review-plan": {
-    "description": "技術実装計画の実現可能性と整合性をレビュー・検証"
+    "description": "技術実装計画の実現可能性と整合性をレビュー・検証",
+    "argument-hint": "[plan.md へのパス] (オプション、デフォルトは .codexspec/specs/{feature-id}/)"
   },
   "review-tasks": {
-    "description": "タスク分解の完全性、順序、TDD準拠をレビュー・検証"
+    "description": "タスク分解の完全性、順序、TDD準拠をレビュー・検証",
+    "argument-hint": "[tasks.md へのパス] (オプション、デフォルトは .codexspec/specs/{feature-id}/)"
   },
   "implement-tasks": {
-    "description": "条件付きTDDワークフローで実装タスクを実行（コードはTDD、ドキュメント/設定は直接実装）"
+    "description": "条件付きTDDワークフローで実装タスクを実行（コードはTDD、ドキュメント/設定は直接実装）",
+    "argument-hint": "[tasks へのパス] | [spec へのパス plan へのパス tasks へのパス]"
   },
   "tasks-to-issues": {
     "description": "既存のタスクをこの機能の実行可能なGitHub Issuesに変換"
   },
   "commit": {
-    "description": "gitステータスとセッションコンテキストに基づいてConventional Commits準拠のコミットメッセージを生成・実行"
+    "description": "gitステータスとセッションコンテキストに基づいてConventional Commits準拠のコミットメッセージを生成・実行",
+    "argument-hint": "[-p] -p を使用するとコミットせずにメッセージをプレビューのみ"
   },
   "commit-staged": {
-    "description": "ステージングされたgit変更を分析し、Conventional Commits準拠のコミットメッセージを生成"
+    "description": "ステージングされたgit変更を分析し、Conventional Commits準拠のコミットメッセージを生成",
+    "argument-hint": "[-p] -p を使用するとコミットせずにメッセージをプレビューのみ"
   },
   "pr": {
     "description": "git diffとオプションのspec.md統合に基づいて構造化されたPull Request (GitHub) またはMerge Request (GitLab) 説明を生成"
   },
   "check-i18n-semantics": {
-    "description": "多言語ドキュメントの意味的一貫性と品質をチェック"
+    "description": "多言語ドキュメントの意味的一貫性と品質をチェック",
+    "argument-hint": "[ソースファイル] [--lang <言語>] [--strict]"
   },
   "translate-docs": {
-    "description": "プロジェクトドキュメントを指定言語に翻訳"
+    "description": "プロジェクトドキュメントを指定言語に翻訳",
+    "argument-hint": "--lang <言語コード> (例: 'zh,ja,ko') または 'all' ですべての言語"
   }
 }

{codexspec-0.4.0 → codexspec-0.4.2}/templates/translations/ko.json

@@ -1,13 +1,15 @@
 {
   "constitution": {
     "description": "대화형 또는 제공된 원칙 입력에서 프로젝트 헌법을 생성하거나 업데이트하며, 모든 종속 템플릿의 동기화를 유지합니다.",
-    "argument-hint": "[quick|deep | 프로젝트 원칙] (선택사항)\n\n이 명령은 .codexspec/memory/constitution.md에 프로젝트 헌법을 생성/업데이트합니다.\n\n세 가지 사용 방법:\n1. 인수 없음 → 대화형 모드: 탐색 깊이 선택 (quick/deep)\n2. quick → 가벼운 탐색: 설정 파일 + README + 핵심 진입점 (~5-10개 파일)\n3. deep → 전체 탐색: 위 내용 + 소스 코드 분석 + 아키텍처 패턴\n4. <설명> → 탐색 건너뛰기, 원칙 직접 사용"
+    "argument-hint": "[quick|deep | 프로젝트 원칙] (선택사항)\n\n이 명령은 .codexspec/memory/constitution.md에 프로젝트 헌법을 생성/업데이트합니다.\n\n세 가지 사용 방법:\n1. 인수 없음 → 대화형 모드: 탐색 깊이 선택 (quick/deep)\n2. quick → 가벼운 탐색: 설정 파일 + README + 핵심 진입점 (~5-10개 파일)\n3. deep → 전체 탐색: 위 내용 + 소스 코드 분석 + 아키텍처 패턴\n4. <설명> → 탐색 건너뛰기, 원칙 직접 사용\n\n예시:\n  /codexspec.constitution\n  /codexspec.constitution quick\n  /codexspec.constitution deep\n  /codexspec.constitution Python FastAPI 백엔드에서 pytest 사용, 타입 안전성 중시"
   },
   "specify": {
-    "description": "대화형 Q&A를 통해 요구사항을 명확히 하고 초기 아이디어를 탐색 및 정제"
+    "description": "대화형 Q&A를 통해 요구사항을 명확히 하고 초기 아이디어를 탐색 및 정제",
+    "argument-hint": "초기 아이디어나 요구사항을 설명해 주세요"
   },
   "clarify": {
-    "description": "기술 계획 전에 대상화된 질문으로 기능 사양의 불명확한 영역 식별"
+    "description": "기술 계획 전에 대상화된 질문으로 기능 사양의 불명확한 영역 식별",
+    "argument-hint": "[spec.md 경로] (선택사항, 기본값 .codexspec/specs/{feature-id}/)"
   },
   "analyze": {
     "description": "spec.md, plan.md, tasks.md 간의 일관성과 품질을 비파괴적으로 분석"
@@ -19,39 +21,49 @@
     "description": "요구사항이 명확해진 후 spec.md 문서 생성"
   },
   "spec-to-plan": {
-    "description": "기능 사양을 기술 구현 계획으로 변환"
+    "description": "기능 사양을 기술 구현 계획으로 변환",
+    "argument-hint": ".codexspec/specs/{feature-id}/spec.md"
   },
   "plan-to-tasks": {
-    "description": "기술 구현 계획을 실행 가능한 작업으로 분해"
+    "description": "기술 구현 계획을 실행 가능한 작업으로 분해",
+    "argument-hint": "[spec.md 경로 plan.md 경로] (선택사항, 기본값 .codexspec/specs/{feature-id}/)"
   },
   "review-spec": {
-    "description": "기능 사양의 완전성, 명확성, 품질 검토 및 검증"
+    "description": "기능 사양의 완전성, 명확성, 품질 검토 및 검증",
+    "argument-hint": "[spec.md 경로] (선택사항, 기본값 .codexspec/specs/{feature-id}/)"
   },
   "review-plan": {
-    "description": "기술 구현 계획의 실현 가능성과 일관성 검토 및 검증"
+    "description": "기술 구현 계획의 실현 가능성과 일관성 검토 및 검증",
+    "argument-hint": "[plan.md 경로] (선택사항, 기본값 .codexspec/specs/{feature-id}/)"
   },
   "review-tasks": {
-    "description": "작업 분해의 완전성, 순서, TDD 준수 검토 및 검증"
+    "description": "작업 분해의 완전성, 순서, TDD 준수 검토 및 검증",
+    "argument-hint": "[tasks.md 경로] (선택사항, 기본값 .codexspec/specs/{feature-id}/)"
   },
   "implement-tasks": {
-    "description": "조건부 TDD 워크플로로 구현 작업 실행 (코드는 TDD, 문서/구성은 직접 구현)"
+    "description": "조건부 TDD 워크플로로 구현 작업 실행 (코드는 TDD, 문서/구성은 직접 구현)",
+    "argument-hint": "[tasks 경로] | [spec 경로 plan 경로 tasks 경로]"
   },
   "tasks-to-issues": {
     "description": "기존 작업을 이 기능에 대한 실행 가능한 GitHub Issues로 변환"
   },
   "commit": {
-    "description": "git 상태와 세션 컨텍스트를 기반으로 Conventional Commits 준수 커밋 메시지 생성 및 실행"
+    "description": "git 상태와 세션 컨텍스트를 기반으로 Conventional Commits 준수 커밋 메시지 생성 및 실행",
+    "argument-hint": "[-p] -p를 사용하면 커밋하지 않고 메시지만 미리보기"
   },
   "commit-staged": {
-    "description": "스테이징된 git 변경 사항을 분석하고 Conventional Commits 준수 커밋 메시지 생성"
+    "description": "스테이징된 git 변경 사항을 분석하고 Conventional Commits 준수 커밋 메시지 생성",
+    "argument-hint": "[-p] -p를 사용하면 커밋하지 않고 메시지만 미리보기"
   },
   "pr": {
     "description": "git diff와 선택적 spec.md 통합을 기반으로 구조화된 Pull Request (GitHub) 또는 Merge Request (GitLab) 설명 생성"
   },
   "check-i18n-semantics": {
-    "description": "다국어 문서의 의미적 일관성과 품질 검사"
+    "description": "다국어 문서의 의미적 일관성과 품질 검사",
+    "argument-hint": "[소스_파일] [--lang <언어>] [--strict]"
   },
   "translate-docs": {
-    "description": "프로젝트 문서를 지정된 언어로 번역"
+    "description": "프로젝트 문서를 지정된 언어로 번역",
+    "argument-hint": "--lang <언어_코드> (예: 'zh,ja,ko') 또는 'all'로 모든 언어"
   }
 }

{codexspec-0.4.0 → codexspec-0.4.2}/templates/translations/pt-BR.json

@@ -1,13 +1,15 @@
 {
   "constitution": {
     "description": "Criar ou atualizar a constituição do projeto a partir de entradas interativas ou princípios fornecidos, garantindo que todos os modelos dependentes permaneçam sincronizados.",
-    "argument-hint": "[quick|deep | princípios do projeto] (opcional)\n\nEste comando cria/atualiza a constituição do projeto em .codexspec/memory/constitution.md.\n\nTrês formas de uso:\n1. Sem argumentos → Modo interativo: escolher profundidade de exploração (quick/deep)\n2. quick → Exploração leve: arquivos de configuração + README + pontos de entrada principais (~5-10 arquivos)\n3. deep → Exploração completa: tudo acima + análise de código fonte + padrões de arquitetura\n4. <descrição> → Pular exploração, usar seus princípios diretamente"
+    "argument-hint": "[quick|deep | princípios do projeto] (opcional)\n\nEste comando cria/atualiza a constituição do projeto em .codexspec/memory/constitution.md.\n\nTrês formas de uso:\n1. Sem argumentos → Modo interativo: escolher profundidade de exploração (quick/deep)\n2. quick → Exploração leve: arquivos de configuração + README + pontos de entrada principais (~5-10 arquivos)\n3. deep → Exploração completa: tudo acima + análise de código fonte + padrões de arquitetura\n4. <descrição> → Pular exploração, usar seus princípios diretamente\n\nExemplos:\n  /codexspec.constitution\n  /codexspec.constitution quick\n  /codexspec.constitution deep\n  /codexspec.constitution Python FastAPI backend com pytest, focado em segurança de tipos"
   },
   "specify": {
-    "description": "Esclarecer requisitos através de Q&A interativo para explorar e refinar ideias iniciais"
+    "description": "Esclarecer requisitos através de Q&A interativo para explorar e refinar ideias iniciais",
+    "argument-hint": "Descreva sua ideia inicial ou requisito"
   },
   "clarify": {
-    "description": "Identificar áreas pouco claras na especificação funcional através de perguntas direcionadas antes do planejamento técnico"
+    "description": "Identificar áreas pouco claras na especificação funcional através de perguntas direcionadas antes do planejamento técnico",
+    "argument-hint": "[caminho_para_spec.md] (opcional, padrão .codexspec/specs/{feature-id}/)"
   },
   "analyze": {
     "description": "Realizar análise não destrutiva de consistência e qualidade entre artefatos spec.md, plan.md e tasks.md"
@@ -19,39 +21,49 @@
     "description": "Gerar documento spec.md após os requisitos estarem claros"
   },
   "spec-to-plan": {
-    "description": "Converter especificação funcional em plano de implementação técnica"
+    "description": "Converter especificação funcional em plano de implementação técnica",
+    "argument-hint": ".codexspec/specs/{feature-id}/spec.md"
   },
   "plan-to-tasks": {
-    "description": "Decompor plano de implementação técnica em tarefas executáveis"
+    "description": "Decompor plano de implementação técnica em tarefas executáveis",
+    "argument-hint": "[caminho_spec.md caminho_plan.md] (opcional, padrão .codexspec/specs/{feature-id}/)"
   },
   "review-spec": {
-    "description": "Revisar e validar completude, clareza e qualidade da especificação funcional"
+    "description": "Revisar e validar completude, clareza e qualidade da especificação funcional",
+    "argument-hint": "[caminho_spec.md] (opcional, padrão .codexspec/specs/{feature-id}/)"
   },
   "review-plan": {
-    "description": "Revisar e validar viabilidade e consistência do plano de implementação técnica"
+    "description": "Revisar e validar viabilidade e consistência do plano de implementação técnica",
+    "argument-hint": "[caminho_plan.md] (opcional, padrão .codexspec/specs/{feature-id}/)"
   },
   "review-tasks": {
-    "description": "Revisar e validar completude, ordenação e conformidade TDD da decomposição de tarefas"
+    "description": "Revisar e validar completude, ordenação e conformidade TDD da decomposição de tarefas",
+    "argument-hint": "[caminho_tasks.md] (opcional, padrão .codexspec/specs/{feature-id}/)"
   },
   "implement-tasks": {
-    "description": "Executar tarefas de implementação com workflow TDD condicional (TDD para código, implementação direta para docs/config)"
+    "description": "Executar tarefas de implementação com workflow TDD condicional (TDD para código, implementação direta para docs/config)",
+    "argument-hint": "[caminho_tasks] | [caminho_spec caminho_plan caminho_tasks]"
   },
   "tasks-to-issues": {
     "description": "Converter tarefas existentes em GitHub Issues acionáveis para esta funcionalidade"
   },
   "commit": {
-    "description": "Gerar e executar mensagens de commit em conformidade com Conventional Commits baseadas no estado git e contexto de sessão"
+    "description": "Gerar e executar mensagens de commit em conformidade com Conventional Commits baseadas no estado git e contexto de sessão",
+    "argument-hint": "[-p] Use -p para apenas visualizar a mensagem sem fazer commit"
   },
   "commit-staged": {
-    "description": "Analisar mudanças git preparadas e gerar mensagem de commit em conformidade com Conventional Commits"
+    "description": "Analisar mudanças git preparadas e gerar mensagem de commit em conformidade com Conventional Commits",
+    "argument-hint": "[-p] Use -p para apenas visualizar a mensagem sem fazer commit"
   },
   "pr": {
     "description": "Gerar descrição estruturada de Pull Request (GitHub) ou Merge Request (GitLab) baseada em git diff e integração opcional de spec.md"
   },
   "check-i18n-semantics": {
-    "description": "Verificar consistência semântica e qualidade de documentação multilíngue"
+    "description": "Verificar consistência semântica e qualidade de documentação multilíngue",
+    "argument-hint": "[arquivo_origem] [--lang <idioma>] [--strict]"
   },
   "translate-docs": {
-    "description": "Traduzir documentação do projeto para o idioma especificado"
+    "description": "Traduzir documentação do projeto para o idioma especificado",
+    "argument-hint": "--lang <códigos_idioma> (ex: 'zh,ja,ko') ou 'all' para todos os idiomas"
   }
 }

{codexspec-0.4.0 → codexspec-0.4.2}/templates/translations/zh-CN.json

@@ -4,10 +4,12 @@
     "argument-hint": "[quick|deep | 项目原则] (可选)\n\n此命令创建/更新位于 .codexspec/memory/constitution.md 的项目宪法。\n\n三种使用方式：\n1. 无参数 → 交互模式：选择探索深度 (quick/deep)\n2. quick → 轻量探索：配置文件 + README + 核心入口点 (~5-10 个文件)\n3. deep → 完整探索：以上内容 + 源代码分析 + 架构模式\n4. <描述> → 跳过探索，直接使用你的原则\n\n示例：\n  /codexspec.constitution\n  /codexspec.constitution quick\n  /codexspec.constitution deep\n  /codexspec.constitution Python FastAPI 后端使用 pytest，注重类型安全"
   },
   "specify": {
-    "description": "通过交互式问答澄清需求，探索和完善初始想法"
+    "description": "通过交互式问答澄清需求，探索和完善初始想法",
+    "argument-hint": "描述你的初始想法或需求"
   },
   "clarify": {
-    "description": "在技术规划前通过定向澄清问题识别功能规格中的不明确区域"
+    "description": "在技术规划前通过定向澄清问题识别功能规格中的不明确区域",
+    "argument-hint": "[spec.md 路径] (可选，默认为 .codexspec/specs/{feature-id}/)"
   },
   "analyze": {
     "description": "对 spec.md、plan.md 和 tasks.md 执行非破坏性的跨工件一致性和质量分析"
@@ -19,39 +21,49 @@
     "description": "需求明确后生成 spec.md 文档"
   },
   "spec-to-plan": {
-    "description": "将功能规格转换为技术实现计划"
+    "description": "将功能规格转换为技术实现计划",
+    "argument-hint": ".codexspec/specs/{feature-id}/spec.md"
   },
   "plan-to-tasks": {
-    "description": "将技术实现计划分解为可执行的任务"
+    "description": "将技术实现计划分解为可执行的任务",
+    "argument-hint": "[spec.md 路径 plan.md 路径] (可选，默认为 .codexspec/specs/{feature-id}/)"
   },
   "review-spec": {
-    "description": "审查和验证功能规格的完整性、清晰度和质量"
+    "description": "审查和验证功能规格的完整性、清晰度和质量",
+    "argument-hint": "[spec.md 路径] (可选，默认为 .codexspec/specs/{feature-id}/)"
   },
   "review-plan": {
-    "description": "审查和验证技术实现计划的可行性和一致性"
+    "description": "审查和验证技术实现计划的可行性和一致性",
+    "argument-hint": "[plan.md 路径] (可选，默认为 .codexspec/specs/{feature-id}/)"
   },
   "review-tasks": {
-    "description": "审查和验证任务分解的完整性、排序和 TDD 合规性"
+    "description": "审查和验证任务分解的完整性、排序和 TDD 合规性",
+    "argument-hint": "[tasks.md 路径] (可选，默认为 .codexspec/specs/{feature-id}/)"
   },
   "implement-tasks": {
-    "description": "执行实现任务，支持条件 TDD 工作流（代码使用 TDD，文档/配置直接实现）"
+    "description": "执行实现任务，支持条件 TDD 工作流（代码使用 TDD，文档/配置直接实现）",
+    "argument-hint": "[tasks 路径] | [spec 路径 plan 路径 tasks 路径]"
   },
   "tasks-to-issues": {
     "description": "将现有任务转换为该功能的可操作 GitHub Issues"
   },
   "commit": {
-    "description": "基于 git 状态和会话上下文生成并执行符合 Conventional Commits 规范的提交信息"
+    "description": "基于 git 状态和会话上下文生成并执行符合 Conventional Commits 规范的提交信息",
+    "argument-hint": "[-p] 使用 -p 仅预览提交信息而不执行提交"
   },
   "commit-staged": {
-    "description": "分析暂存的 git 更改并生成符合 Conventional Commits 规范的提交信息"
+    "description": "分析暂存的 git 更改并生成符合 Conventional Commits 规范的提交信息",
+    "argument-hint": "[-p] 使用 -p 仅预览提交信息而不执行提交"
   },
   "pr": {
     "description": "基于 git diff 和可选的 spec.md 集成生成结构化的 Pull Request (GitHub) 或 Merge Request (GitLab) 描述"
   },
   "check-i18n-semantics": {
-    "description": "检查多语言文档的语义一致性和质量"
+    "description": "检查多语言文档的语义一致性和质量",
+    "argument-hint": "[源文件] [--lang <语言>] [--strict]"
   },
   "translate-docs": {
-    "description": "翻译项目文档到指定语言"
+    "description": "翻译项目文档到指定语言",
+    "argument-hint": "--lang <语言代码> (如 'zh,ja,ko') 或 'all' 翻译所有语言"
   }
 }