codexspec 0.5.16__tar.gz → 0.5.18__tar.gz

{codexspec-0.5.16 → codexspec-0.5.18}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: codexspec
-Version: 0.5.16
+Version: 0.5.18
 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.5.16 → codexspec-0.5.18}/pyproject.toml

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

{codexspec-0.5.16 → codexspec-0.5.18}/src/codexspec/__init__.py

@@ -734,8 +734,6 @@ def _create_default_commands(commands_dir: Path) -> None:
         "pr": _get_pr_command(),
         "review-python-code": _get_review_python_code_command(),
         "review-react-code": _get_review_react_code_command(),
-        "translate-docs": _get_translate_docs_command(),
-        "check-i18n-semantics": _get_check_i18n_semantics_command(),
     }
 
     for name, content in commands.items():
@@ -1488,70 +1486,6 @@ This command combines static analysis tools with architectural review to provide
 """
 
 
-def _get_translate_docs_command() -> str:
-    """Return the translate-docs command template."""
-    return """---
-description: Translate documentation to target languages using AI-assisted translation with glossary support
-argument-hint: "--lang <language_codes> (e.g., 'zh,ja,ko') or 'all' for all languages"
-handoffs:
-  - agent: claude
-    step: Execute document translation with glossary guidance
----
-
-# Document Translator
-
-## User Input
-
-$ARGUMENTS
-
-## Instructions
-
-Translate documentation files to specified target languages while maintaining technical accuracy and formatting.
-
-### Steps
-
-1. **Parse Arguments**: Identify target languages from --lang parameter
-2. **Load Glossary**: Read terminology guidelines from .codexspec/i18n/glossary.yml
-3. **Translate Files**: Process each documentation file
-4. **Maintain Formatting**: Preserve markdown structure and code blocks
-
-> [!NOTE]
-> This command supports batch translation for multiple languages.
-"""
-
-
-def _get_check_i18n_semantics_command() -> str:
-    """Return the check-i18n-semantics command template."""
-    return """---
-description: Check semantic consistency between source and translated documentation using AI
-argument-hint: "[source_file] [--lang <lang>] [--strict]"
-allowed-tools: Read, Glob, Grep, Bash
----
-
-# Semantic Consistency Check
-
-## User Input
-
-```
-$ARGUMENTS
-```
-
-## Instructions
-
-Analyze translated documentation for semantic consistency with the source English content.
-
-### Steps
-
-1. **Parse Arguments**: Identify source file and target languages
-2. **Load Files**: Read source and translated versions
-3. **Semantic Analysis**: Compare meaning and accuracy
-4. **Generate Report**: List inconsistencies with severity levels
-
-> [!NOTE]
-> Use --strict flag to fail on any semantic drift.
-"""
-
-
 def _get_default_constitution() -> str:
     """Return the default constitution content."""
     return """> **SUPREME AUTHORITY**: This constitution defines the governing principles

{codexspec-0.5.16 → codexspec-0.5.18}/src/codexspec/commands/installer.py

@@ -42,7 +42,7 @@ def get_commands_metadata() -> list[CommandMetadata]:
 
     Returns:
         List of CommandMetadata dictionaries sorted by category priority:
-        core (9) -> enhanced (6) -> git (2) -> review (2)
+        core (9) -> enhanced (4) -> git (2) -> review (2)
     """
     return [
         # Core Commands (9)
@@ -138,20 +138,6 @@ def get_commands_metadata() -> list[CommandMetadata]:
             "category": "enhanced",
             "file_name": "tasks-to-issues.md",
         },
-        {
-            "name": "translate-docs",
-            "display_name": "/codexspec:translate-docs",
-            "description": "翻译项目文档到指定语言",
-            "category": "enhanced",
-            "file_name": "translate-docs.md",
-        },
-        {
-            "name": "check-i18n-semantics",
-            "display_name": "/codexspec:check-i18n-semantics",
-            "description": "检查多语言文档的语义一致性和质量",
-            "category": "enhanced",
-            "file_name": "check-i18n-semantics.md",
-        },
         # Git Workflow Commands (2)
         {
             "name": "commit-staged",

{codexspec-0.5.16 → codexspec-0.5.18}/templates/commands/commit-staged.md

@@ -1,5 +1,5 @@
 ---
-description: Analyze staged git changes and generate Conventional Commits compliant commit messages with session context awareness
+description: Analyze staged git changes and generate Conventional Commits compliant commit messages strictly from the staged diff
 argument-hint: "[-p] Use -p to only preview the message without committing"
 allowed-tools: Bash(git diff --staged:*), Bash(git diff --cached:*), Bash(git status:*), Bash(git commit:*)
 forbidden-tools: Bash(git add:*), Bash(git reset:*), Bash(git checkout:*), Bash(git restore:*), Bash(git stash:*), Bash(git rm:*)
@@ -30,7 +30,7 @@ forbidden-tools: Bash(git add:*), Bash(git reset:*), Bash(git checkout:*), Bash(
    - Display a one-time prompt:
 
      ```
-     💡 检测到项目未配置语言设置。你可以使用 `/codexspec:config` 命令来创建配置文件。
+     💡 Project language is not configured. Run `/codexspec:config` to create a configuration file.
      ```
 
    - Use default values for current session:
@@ -105,6 +105,8 @@ Before analyzing changes, verify the staged state:
 
 ### Change Analysis
 
+**Source of truth**: The staged diff is the *only* authoritative input for the commit message. Do NOT infer intent, motivation, or scope from prior conversation turns, earlier session messages, or any discussion unrelated to what is actually staged. If the diff alone is insufficient to write a clear and accurate message, ABORT and ask the user for clarification rather than guessing.
+
 1. Execute `git diff --staged` to retrieve staged changes.
 
 2. Analyze the changes and generate a commit message that strictly follows **Conventional Commits** specification:
@@ -113,7 +115,7 @@ Before analyzing changes, verify the staged state:
    - If the project has a `CLAUDE.md` with custom commit conventions, follow those instead
    - **DO NOT** include any AI attribution in the commit message
    - Do not add `Co-Authored-By` lines or any references to AI tools/agents
-   - The commit message should focus solely on describing the changes
+   - The commit message should focus solely on describing the changes present in the staged diff
 
 3. **If preview mode (`-p`)**: Display the generated commit message and stop.
 
@@ -128,16 +130,6 @@ If `git commit` fails due to a pre-commit hook modifying files:
 3. Retry the commit with the same message
 4. If it still fails or the situation is unclear, ABORT and inform the user
 
-## Session Context Awareness
-
-When analyzing changes, consider the current session context:
-
-- What the user has been working on in this session
-- The purpose and goals discussed in the conversation
-- Any related specifications, plans, or tasks mentioned
-
-This context helps generate more meaningful commit messages that reflect the "why" behind the changes, not just the "what".
-
 ## Important Notes
 
 - In execute mode (default), execute `git commit` directly after generating the message

{codexspec-0.5.16 → codexspec-0.5.18}/templates/commands/quick.md

@@ -19,7 +19,7 @@ argument-hint: "Describe your requirement"
    - Display a one-time prompt:
 
      ```
-     💡 检测到项目未配置语言设置。你可以使用 `/codexspec:config` 命令来创建配置文件。
+     💡 Project language is not configured. Run `/codexspec:config` to create a configuration file.
      ```
 
    - Use default values for current session:

{codexspec-0.5.16 → codexspec-0.5.18}/templates/commands/review-plan.md

@@ -140,7 +140,7 @@ Before scoring, apply these rubrics to ensure consistent, transparent evaluation
 - Tight coupling between modules: -8 each
 - Missing separation of concerns: -10
 
-#### Phase Planning (15%)
+#### Phase Planning (20%)
 
 | Score Range | Criteria |
 |-------------|----------|
@@ -156,7 +156,7 @@ Before scoring, apply these rubrics to ensure consistent, transparent evaluation
 - Overly large phase scope: -5 each
 - Missing phase dependencies: -5
 
-#### Constitution Alignment (15%)
+#### Constitution Alignment (10%)
 
 | Score Range | Criteria |
 |-------------|----------|
@@ -304,8 +304,8 @@ Before scoring, apply these rubrics to ensure consistent, transparent evaluation
 | Spec Alignment | 30% | X/100 | [Which rubric range applies] | [List specific deductions, e.g., "REQ-003 not addressed: -15"] | X |
 | Tech Stack | 15% | X/100 | [Which rubric range applies] | [e.g., "No version for DB: -5"] | X |
 | Architecture Quality | 25% | X/100 | [Which rubric range applies] | [e.g., "Missing dependency graph: -10"] | X |
-| Phase Planning | 15% | X/100 | [Which rubric range applies] | [e.g., "Phase 2 scope too large: -5"] | X |
-| Constitution Alignment | 15% | X/100 | [Which rubric range applies] | [e.g., "All principles addressed"] | X |
+| Phase Planning | 20% | X/100 | [Which rubric range applies] | [e.g., "Phase 2 scope too large: -5"] | X |
+| Constitution Alignment | 10% | X/100 | [Which rubric range applies] | [e.g., "All principles addressed"] | X |
 | **Total** | **100%** | | | | **X/100** |
 
 > **Suggestion Cap**: Suggestions deducted X/5 points (cap: 5 points max)

{codexspec-0.5.16 → codexspec-0.5.18}/templates/commands/review-python-code.md

@@ -129,7 +129,7 @@ Before scoring, apply these rubrics to ensure consistent, transparent evaluation
 - Missing `raise ... from err` context: -3 each
 - mypy error: -5 each
 
-#### Engineering Robustness (25%)
+#### Engineering Robustness (30%)
 
 | Score Range | Criteria |
 |-------------|----------|
@@ -146,7 +146,7 @@ Before scoring, apply these rubrics to ensure consistent, transparent evaluation
 - Incorrect log level usage: -3 each
 - ruff violation: -3 each
 
-#### Constitution Alignment (15%)
+#### Constitution Alignment (10%)
 
 | Score Range | Criteria |
 |-------------|----------|
@@ -267,8 +267,8 @@ Before scoring, apply these rubrics to ensure consistent, transparent evaluation
 |----------|--------|-------|-------------|-------------------|----------|
 | Pythonic & KISS | 30% | X/100 | [Which rubric range applies] | [List specific deductions, e.g., "Unnecessary class in utils.py: -8"] | X |
 | Type Safety | 30% | X/100 | [Which rubric range applies] | [e.g., "2 functions missing annotations: -10"] | X |
-| Engineering Robustness | 25% | X/100 | [Which rubric range applies] | [e.g., "File opened without context manager: -8"] | X |
-| Constitution Alignment | 15% | X/100 | [Which rubric range applies] | [e.g., "All principles followed"] | X |
+| Engineering Robustness | 30% | X/100 | [Which rubric range applies] | [e.g., "File opened without context manager: -8"] | X |
+| Constitution Alignment | 10% | X/100 | [Which rubric range applies] | [e.g., "All principles followed"] | X |
 | **Total** | **100%** | | | | **X/100** |
 
 > **Suggestion Cap**: LOW suggestions deducted X/5 points (cap: 5 points max)

{codexspec-0.5.16 → codexspec-0.5.18}/templates/commands/review-react-code.md

@@ -152,7 +152,7 @@ Before scoring, apply these rubrics to ensure consistent, transparent evaluation
 - Missing error handling for async operation: -8 each
 - Race condition in async operation: -10 each
 
-#### Performance & Robustness (20%)
+#### Performance & Robustness (15%)
 
 | Score Range | Criteria |
 |-------------|----------|
@@ -168,7 +168,7 @@ Before scoring, apply these rubrics to ensure consistent, transparent evaluation
 - Missing optional chaining for nullable access: -3 each
 - Missing React.memo for frequently re-rendered component: -5 each
 
-#### Constitution Alignment (5%)
+#### Constitution Alignment (10%)
 
 | Score Range | Criteria |
 |-------------|----------|
@@ -291,8 +291,8 @@ Before scoring, apply these rubrics to ensure consistent, transparent evaluation
 | Component Atomicity & SRP | 25% | X/100 | [Which rubric range applies] | [List specific deductions, e.g., "UserPanel.tsx 350 lines: -5"] | X |
 | Hooks Compliance | 25% | X/100 | [Which rubric range applies] | [e.g., "useEffect missing dep in Form.tsx: -8"] | X |
 | State Management | 25% | X/100 | [Which rubric range applies] | [e.g., "Missing error state in useFetch: -8"] | X |
-| Performance & Robustness | 20% | X/100 | [Which rubric range applies] | [e.g., "Unmemoized filter in List.tsx: -8"] | X |
-| Constitution Alignment | 5% | X/100 | [Which rubric range applies] | [e.g., "All principles followed"] | X |
+| Performance & Robustness | 15% | X/100 | [Which rubric range applies] | [e.g., "Unmemoized filter in List.tsx: -8"] | X |
+| Constitution Alignment | 10% | X/100 | [Which rubric range applies] | [e.g., "All principles followed"] | X |
 | **Total** | **100%** | | | | **X/100** |
 
 > **Suggestion Cap**: LOW suggestions deducted X/5 points (cap: 5 points max)

{codexspec-0.5.16 → codexspec-0.5.18}/templates/commands/review-tasks.md

@@ -85,11 +85,17 @@ Review the task breakdown for quality and implementation readiness. This command
    - [ ] File paths are consistent with plan
    - [ ] File naming conventions are followed (per constitution)
 
+9. **Constitution Alignment Check**: Verify task breakdown respects project principles:
+   - [ ] TDD enforcement aligns with constitution testing standards
+   - [ ] Quality gates and checkpoints reflect constitution principles
+   - [ ] Naming conventions are followed (per constitution)
+   - [ ] Workflow guidelines from constitution are considered
+
 ### Scoring Rubrics
 
 Before scoring, apply these rubrics to ensure consistent, transparent evaluation.
 
-#### Plan Coverage (30%)
+#### Plan Coverage (25%)
 
 | Score Range | Criteria |
 |-------------|----------|
@@ -136,7 +142,7 @@ Before scoring, apply these rubrics to ensure consistent, transparent evaluation
 - Incorrect task ordering: -8 each
 - Foundation task not placed first: -10
 
-#### Task Granularity (15%)
+#### Task Granularity (10%)
 
 | Score Range | Criteria |
 |-------------|----------|
@@ -167,6 +173,22 @@ Before scoring, apply these rubrics to ensure consistent, transparent evaluation
 - Task without file path specification: -5 each
 - File path not following project convention: -3 each
 
+#### Constitution Alignment (10%)
+
+| Score Range | Criteria |
+|-------------|----------|
+| 90-100 | Fully aligned with all constitution principles; TDD/quality standards addressed; workflow guidelines followed |
+| 70-89 | Mostly aligned; minor gaps in addressing specific principles |
+| 50-69 | Partial alignment; several principles not addressed |
+| Below 50 | Significant violations or disregard of constitution |
+
+> **Note**: If no constitution exists, this category defaults to 100 (full marks) and its weight is redistributed proportionally to other categories.
+
+**Typical Deductions**:
+
+- Constitution principle not addressed: -10 per principle
+- Direct violation of a constitution principle (e.g., test tasks omitted despite TDD requirement): -20 per violation
+
 #### Suggestion Score Cap Rule
 
 **IMPORTANT**: Suggestions (Nice to Have) items may deduct a **maximum of 5 points** from the total score. After resolving all Critical Issues and Warnings, the score should be **≥ 95**.
@@ -307,6 +329,19 @@ Valid Dependency Chain:
 - [ ] **[FILE-001]**: Task 2.1 file path doesn't match project naming convention
 - [ ] **[FILE-002]**: Task 3.1 missing file path specification
 
+## Constitution Alignment
+
+> [!NOTE]
+> If no constitution exists, state "No project constitution found - using general best practices."
+
+| Principle | Alignment | Notes |
+|-----------|-----------|-------|
+| [Principle 1] | ✅/⚠️/❌ | [How task breakdown aligns or conflicts] |
+| [Principle 2] | ✅/⚠️/❌ | [How task breakdown aligns or conflicts] |
+
+### Constitution Issues
+- [ ] **[CONST-001]**: [Principle violation or gap, e.g., "TDD principle not enforced for Module C"]
+
 ## Detailed Findings
 
 ### Critical Issues (Must Fix)
@@ -328,11 +363,12 @@ Valid Dependency Chain:
 
 | Category | Weight | Score | Rubric Basis | Deduction Details | Weighted |
 |----------|--------|-------|-------------|-------------------|----------|
-| Plan Coverage | 30% | X/100 | [Which rubric range applies] | [List specific deductions, e.g., "Module C missing task: -10"] | X |
+| Plan Coverage | 25% | X/100 | [Which rubric range applies] | [List specific deductions, e.g., "Module C missing task: -10"] | X |
 | TDD Compliance | 25% | X/100 | [Which rubric range applies] | [e.g., "Service X test after impl: -8"] | X |
 | Dependency & Ordering | 20% | X/100 | [Which rubric range applies] | [e.g., "Missing dependency Task 2.3→1.2: -5"] | X |
-| Task Granularity | 15% | X/100 | [Which rubric range applies] | [e.g., "Task 2.5 involves 3 files: -8"] | X |
+| Task Granularity | 10% | X/100 | [Which rubric range applies] | [e.g., "Task 2.5 involves 3 files: -8"] | X |
 | Parallelization & Files | 10% | X/100 | [Which rubric range applies] | [e.g., "Task 2.1 false [P] marker: -8"] | X |
+| Constitution Alignment | 10% | X/100 | [Which rubric range applies] | [e.g., "All principles addressed"] | X |
 | **Total** | **100%** | | | | **X/100** |
 
 > **Suggestion Cap**: Suggestions deducted X/5 points (cap: 5 points max)
@@ -426,6 +462,7 @@ Before completing the review, verify:
 - [ ] Dependency graph is validated with no cycles (Dependency & Ordering)
 - [ ] Task granularity is appropriate (Task Granularity)
 - [ ] Parallelization markers and file paths are correct (Parallelization & Files)
+- [ ] Constitution principles are addressed (Constitution Alignment)
 - [ ] Issues have clear, actionable suggestions
 - [ ] Score reflects actual quality accurately (validated via Score Validation Checklist)
 

{codexspec-0.5.16 → codexspec-0.5.18}/templates/commands/specify.md

@@ -19,7 +19,7 @@ argument-hint: "Describe your initial idea or requirement"
    - Display a one-time prompt:
 
      ```
-     💡 检测到项目未配置语言设置。你可以使用 `/codexspec:config` 命令来创建配置文件。
+     💡 Project language is not configured. Run `/codexspec:config` to create a configuration file.
      ```
 
    - Use default values for current session:

{codexspec-0.5.16 → codexspec-0.5.18}/templates/translations/de.json

@@ -134,14 +134,6 @@
     "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",
-        "argument-hint": "[quelldatei] [--lang <sprache>] [--strict]"
-    },
-    "translate-docs": {
-        "description": "Projektdokumentation in die angegebene Sprache übersetzen",
-        "argument-hint": "--lang <sprachcodes> (z.B. 'zh,ja,ko') oder 'all' für alle Sprachen"
-    },
     "review-python-code": {
         "description": "Python-Code auf PEP 8-Konformität, Typsicherheit, Engineering-Robustheit und Verfassungsübereinstimmung überprüfen",
         "argument-hint": "Pfad zur Python-Datei oder zum Verzeichnis zur Überprüfung\n\nBeispiele:\n- `src/codexspec/` - Gesamtes Paket überprüfen\n- `src/codexspec/__init__.py` - Einzelne Datei überprüfen\n- `src/ tests/` - Mehrere Pfade überprüfen"

{codexspec-0.5.16 → codexspec-0.5.18}/templates/translations/en.json

@@ -134,14 +134,6 @@
   "pr": {
     "description": "Generate structured Pull Request (GitHub) or Merge Request (GitLab) description based on git diff and optional spec.md integration"
   },
-  "check-i18n-semantics": {
-    "description": "Check semantic consistency and quality of multilingual documentation",
-    "argument-hint": "[source_file] [--lang <language>] [--strict]"
-  },
-  "translate-docs": {
-    "description": "Translate project documentation to specified language",
-    "argument-hint": "--lang <language_codes> (e.g. 'zh,ja,ko') or 'all' for all languages"
-  },
   "review-python-code": {
     "description": "Review Python code for PEP 8 compliance, type safety, engineering robustness, and constitution alignment",
     "argument-hint": "Path to Python file or directory to review\n\nExamples:\n- `src/codexspec/` - Review entire package\n- `src/codexspec/__init__.py` - Review single file\n- `src/ tests/` - Review multiple paths"

{codexspec-0.5.16 → codexspec-0.5.18}/templates/translations/es.json

@@ -134,14 +134,6 @@
   "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",
-    "argument-hint": "[archivo_fuente] [--lang <idioma>] [--strict]"
-  },
-  "translate-docs": {
-    "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"
-  },
   "review-python-code": {
     "description": "Revisar código Python por conformidad PEP 8, seguridad de tipos, robustez de ingeniería y alineación con la constitución",
     "argument-hint": "Ruta al archivo o directorio Python a revisar\n\nEjemplos:\n- `src/codexspec/` - Revisar paquete completo\n- `src/codexspec/__init__.py` - Revisar archivo único\n- `src/ tests/` - Revisar múltiples rutas"

{codexspec-0.5.16 → codexspec-0.5.18}/templates/translations/fr.json

@@ -134,14 +134,6 @@
   "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",
-    "argument-hint": "[fichier_source] [--lang <langue>] [--strict]"
-  },
-  "translate-docs": {
-    "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"
-  },
   "review-python-code": {
     "description": "Réviser le code Python pour la conformité PEP 8, la sécurité des types, la robustesse d'ingénierie et l'alignement avec la constitution",
     "argument-hint": "Chemin vers le fichier ou répertoire Python à réviser\n\nExemples:\n- `src/codexspec/` - Réviser le paquet complet\n- `src/codexspec/__init__.py` - Réviser un seul fichier\n- `src/ tests/` - Réviser plusieurs chemins"

{codexspec-0.5.16 → codexspec-0.5.18}/templates/translations/ja.json

@@ -134,14 +134,6 @@
   "pr": {
     "description": "git diffとオプションのspec.md統合に基づいて構造化されたPull Request (GitHub) またはMerge Request (GitLab) 説明を生成"
   },
-  "check-i18n-semantics": {
-    "description": "多言語ドキュメントの意味的一貫性と品質をチェック",
-    "argument-hint": "[ソースファイル] [--lang <言語>] [--strict]"
-  },
-  "translate-docs": {
-    "description": "プロジェクトドキュメントを指定言語に翻訳",
-    "argument-hint": "--lang <言語コード> (例: 'zh,ja,ko') または 'all' ですべての言語"
-  },
   "review-python-code": {
     "description": "PythonコードのPEP 8準拠、型安全性、エンジニアリングの堅牢性、憲法整合性をレビュー",
     "argument-hint": "レビューするPythonファイルまたはディレクトリへのパス\n\n例：\n- `src/codexspec/` - パッケージ全体をレビュー\n- `src/codexspec/__init__.py` - 単一ファイルをレビュー\n- `src/ tests/` - 複数パスをレビュー"

{codexspec-0.5.16 → codexspec-0.5.18}/templates/translations/ko.json

@@ -134,14 +134,6 @@
   "pr": {
     "description": "git diff와 선택적 spec.md 통합을 기반으로 구조화된 Pull Request (GitHub) 또는 Merge Request (GitLab) 설명 생성"
   },
-  "check-i18n-semantics": {
-    "description": "다국어 문서의 의미적 일관성과 품질 검사",
-    "argument-hint": "[소스_파일] [--lang <언어>] [--strict]"
-  },
-  "translate-docs": {
-    "description": "프로젝트 문서를 지정된 언어로 번역",
-    "argument-hint": "--lang <언어_코드> (예: 'zh,ja,ko') 또는 'all'로 모든 언어"
-  },
   "review-python-code": {
     "description": "Python 코드의 PEP 8 준수, 타입 안전성, 엔지니어링 견고성 및 헌법 정렬 검토",
     "argument-hint": "검토할 Python 파일 또는 디렉토리 경로\n\n예시:\n- `src/codexspec/` - 전체 패키지 검토\n- `src/codexspec/__init__.py` - 단일 파일 검토\n- `src/ tests/` - 여러 경로 검토"

{codexspec-0.5.16 → codexspec-0.5.18}/templates/translations/pt-BR.json

@@ -134,14 +134,6 @@
   "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",
-    "argument-hint": "[arquivo_origem] [--lang <idioma>] [--strict]"
-  },
-  "translate-docs": {
-    "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"
-  },
   "review-python-code": {
     "description": "Revisar código Python por conformidade PEP 8, segurança de tipos, robustez de engenharia e alinhamento com a constituição",
     "argument-hint": "Caminho para arquivo ou diretório Python a revisar\n\nExemplos:\n- `src/codexspec/` - Revisar pacote completo\n- `src/codexspec/__init__.py` - Revisar arquivo único\n- `src/ tests/` - Revisar múltiplos caminhos"

{codexspec-0.5.16 → codexspec-0.5.18}/templates/translations/zh-CN.json

@@ -134,14 +134,6 @@
   "pr": {
     "description": "基于 git diff 和可选的 spec.md 集成生成结构化的 Pull Request (GitHub) 或 Merge Request (GitLab) 描述"
   },
-  "check-i18n-semantics": {
-    "description": "检查多语言文档的语义一致性和质量",
-    "argument-hint": "[源文件] [--lang <语言>] [--strict]"
-  },
-  "translate-docs": {
-    "description": "翻译项目文档到指定语言",
-    "argument-hint": "--lang <语言代码> (如 'zh,ja,ko') 或 'all' 翻译所有语言"
-  },
   "review-python-code": {
     "description": "审查 Python 代码的 PEP 8 合规性、类型安全、工程健壮性和宪法一致性",
     "argument-hint": "要审查的 Python 文件或目录路径\n\n示例：\n- `src/codexspec/` - 审查整个包\n- `src/codexspec/__init__.py` - 审查单个文件\n- `src/ tests/` - 审查多个路径"

codexspec-0.5.16/templates/commands/check-i18n-semantics.md

@@ -1,138 +0,0 @@
----
-description: Check semantic consistency between source and translated documentation using AI
-argument-hint: "[source_file] [--lang <lang>] [--strict]"
-allowed-tools:
-  - Read
-  - Glob
-  - Grep
-  - Bash
----
-
-# Semantic Consistency Check
-
-## Language Preference
-
-**IMPORTANT**: Before proceeding, read the project's language configuration from `.codexspec/config.yml`.
-
-- If `language.output` is set to a language other than "en", respond and generate all content in that language
-- If not configured or set to "en", use English as default
-- Technical terms (e.g., API, JWT, OAuth) may remain in English when appropriate
-- All user-facing messages, questions, and generated documents should use the configured language
-
-## User Input
-
-```
-$ARGUMENTS
-```
-
-## Instructions
-
-You are a **Translation Quality Reviewer**. Your task is to analyze translated documentation for semantic consistency with the source English content.
-
-### Steps
-
-1. **Parse Arguments**
-   - `source_file`: Optional specific file to check (e.g., `user-guide/getting-started.md`)
-   - `--lang <lang>`: Target language code (e.g., `zh`, `ja`, `ko`). If not specified, check all languages
-   - `--strict`: Enable strict mode (fail on any semantic drift)
-
-2. **Load Configuration**
-   - Read `.codexspec/config.yml` for project settings
-   - Read `.codexspec/i18n/glossary.yml` for terminology guidelines
-
-3. **Identify Files to Check**
-   - If `source_file` specified: Check only that file across target languages
-   - If no file specified: Check all markdown files in `docs/<lang>/`
-
-4. **Perform Semantic Analysis**
-
-   For each source-target file pair:
-
-   a. **Read both files**
-      - Source: `docs/en/<path>`
-      - Target: `docs/<lang>/<path>`
-
-   b. **Compare semantic elements**:
-      - **Heading hierarchy**: Same structure and meaning
-      - **Key concepts**: All important terms present
-      - **Code examples**: Identical functionality
-      - **Links**: Valid and correctly translated
-      - **Warnings/Notes**: Same severity and meaning
-
-   c. **Identify issues**:
-      - **Missing content**: Sections or paragraphs omitted
-      - **Added content**: Extra information not in source
-      - **Semantic drift**: Meaning changed in translation
-      - **Inconsistent terminology**: Not following glossary
-
-5. **Generate Report**
-
-   Create a structured report with:
-
-   ```markdown
-   # Semantic Consistency Report
-
-   ## Summary
-   - **Files Checked**: X
-   - **Issues Found**: Y
-   - **Severity**: High/Medium/Low
-
-   ## Details
-
-   ### File: <path>
-
-   #### Source (en)
-   [Brief summary of source content]
-
-   #### Target (<lang>)
-   [Brief summary of translated content]
-
-   #### Issues
-   1. **[Severity]** <issue description>
-      - Source: "<original text>"
-      - Translation: "<translated text>"
-      - Problem: <what's wrong>
-      - Suggestion: <how to fix>
-
-   ## Recommendations
-   [List of recommended fixes]
-   ```
-
-6. **Exit Codes**
-   - `0`: No issues found (or only minor issues in non-strict mode)
-   - `1`: Issues found requiring attention
-   - `2`: Error during execution
-
-### Quality Criteria
-
-A translation passes semantic check if:
-
-- [ ] All sections from source are present
-- [ ] No significant content added or removed
-- [ ] Technical terms match glossary
-- [ ] Code examples are functionally equivalent
-- [ ] Links work and point to correct destinations
-- [ ] Warnings/notes maintain same severity
-
-### Example Usage
-
-```bash
-# Check all files in Chinese translation
-/codexspec:check-i18n-semantics --lang zh
-
-# Check specific file in Japanese
-/codexspec:check-i18n-semantics user-guide/installation.md --lang ja
-
-# Strict mode - fail on any drift
-/codexspec:check-i18n-semantics --lang ko --strict
-
-# Check all languages for a specific file
-/codexspec:check-i18n-semantics getting-started.md
-```
-
-### Notes
-
-- This command uses AI analysis and may not catch all semantic issues
-- For critical documentation, consider human review in addition to this check
-- The glossary helps ensure consistent terminology usage
-- Strict mode is recommended for production releases

codexspec-0.5.16/templates/commands/translate-docs.md

@@ -1,232 +0,0 @@
----
-description: Translate documentation to target languages using AI-assisted translation with glossary support
-argument-hint: "--lang <language_codes> (e.g., 'zh,ja,ko') or 'all' for all languages"
-handoffs:
-  - agent: claude
-    step: Execute document translation with glossary guidance
----
-
-# Document Translator
-
-## Language Preference
-
-**IMPORTANT**: Before proceeding, read the project's language configuration from `.codexspec/config.yml`.
-
-- If `language.output` is set to a language other than "en", respond and generate all content in that language
-- If not configured or set to "en", use English as default
-- Technical terms (e.g., API, JWT, OAuth) may remain in English when appropriate
-- All user-facing messages, questions, and generated documents should use the configured language
-
-## User Input
-
-$ARGUMENTS
-
-## Role
-
-You are a **Technical Document Translator** with expertise in:
-
-- Multi-language technical documentation
-- AI-assisted translation workflows
-- Terminology consistency and glossary management
-- Markdown formatting preservation
-- Cultural localization for developer audiences
-
-Your responsibility is to translate English documentation to target languages while maintaining technical accuracy, formatting consistency, and terminology standards.
-
-## When to Use This Command
-
-**Use `/codexspec:translate-docs` when:**
-
-- You need to translate documentation to one or more target languages
-- You want AI-assisted translation with terminology consistency
-- You need to generate initial translations for a new language
-- You want to update existing translations after source changes
-
-**Do NOT use this command for:**
-
-- Manual translation editing → Edit files directly
-- Translation quality review → Use `/codexspec:check-i18n-semantics`
-- Adding new languages to the project → Update mkdocs.yml first
-
-## Instructions
-
-### 1. Parse Arguments
-
-Parse the user input to determine:
-
-- **Target languages**: Extract from `--lang` or `-l` flag
-  - If "all" or not specified, translate to all supported languages
-  - Otherwise, parse comma-separated language codes (e.g., "zh,ja,ko")
-- **Source directory**: Extract from `--source` or `-s` flag (default: `docs/en/`)
-- **Incremental mode**: Check for `--incremental` or `-i` flag
-- **Dry run**: Check for `--dry-run` or `-d` flag
-
-Supported language codes:
-
-| Code | Language | Target Directory |
-|------|----------|-----------------|
-| zh | Chinese (Simplified) | docs/zh/ |
-| ja | Japanese | docs/ja/ |
-| ko | Korean | docs/ko/ |
-| es | Spanish | docs/es/ |
-| fr | French | docs/fr/ |
-| de | German | docs/de/ |
-| pt-BR | Portuguese (Brazil) | docs/pt-BR/ |
-
-### 2. Load Glossary
-
-Read `docs/i18n/glossary.yml` and extract:
-
-- **keep_english**: Terms that should NOT be translated
-- **translations**: Pre-defined translations for specific terms
-- **rules**: Patterns for intelligent term handling
-
-If glossary file doesn't exist, proceed with general translation (no terminology constraints).
-
-### 3. Scan Source Files
-
-Scan the source directory for all Markdown files:
-
-```
-docs/en/
-├── index.md
-├── getting-started/
-│   ├── installation.md
-│   └── quick-start.md
-├── user-guide/
-│   ├── workflow.md
-│   ├── commands.md
-│   └── i18n.md
-└── ...
-```
-
-If `--incremental` flag is set, only translate files where:
-
-- Target file doesn't exist, OR
-- Source file is newer than target file
-
-### 4. Execute Translation
-
-For each source file and target language:
-
-1. **Read source content**
-2. **Apply glossary rules**:
-   - Identify terms in `keep_english` list
-   - Apply pre-defined `translations` where available
-   - Apply `rules` patterns (regex matching)
-3. **Preserve formatting**:
-   - Keep YAML frontmatter unchanged
-   - Preserve code blocks (```...```) without translation
-   - Keep inline code (`...`) unchanged
-   - Preserve URLs and links
-   - Maintain heading structure and levels
-4. **Translate content**:
-   - Translate prose text to target language
-   - Maintain technical accuracy
-   - Use appropriate formality level for technical documentation
-5. **Write output** (unless `--dry-run`):
-   - Create target directory if needed
-   - Write translated content to target path
-
-### 5. Output Format
-
-Display progress during translation:
-
-```
-🌐 CodexSpec 文档翻译 / Document Translation
-
-📁 源目录 / Source: docs/en/
-🎯 目标语言 / Target: zh, ja
-📄 文件数量 / Files: 12
-
-[1/24] 翻译 index.md → zh ... ✅ 完成 (2.3s)
-[2/24] 翻译 index.md → ja ... ✅ 完成 (2.5s)
-[3/24] 翻译 getting-started/installation.md → zh ... ✅ 完成 (1.8s)
-...
-
-✅ 翻译完成 / Translation Complete
-📊 统计 / Stats: 24 个文件，0 个错误 / 24 files, 0 errors
-⏱️ 总耗时 / Total time: 45.2 秒
-```
-
-### 6. Error Handling
-
-If a translation fails:
-
-- Log the error with file path and language
-- Continue with remaining translations
-- Report all errors at the end
-
-## Translation Guidelines
-
-### Terms to Keep in English
-
-Based on glossary.yml `keep_english` list, these should NOT be translated:
-
-- Tool names: uv, pip, pytest, ruff, MkDocs
-- File formats: JSON, YAML, TOML, Markdown
-- Technical terms: CLI, API, SDK, TDD, CI/CD
-- Protocols: HTTP, HTTPS, REST, OAuth, JWT
-- Platforms: GitHub, PyPI
-- File names: spec.md, plan.md, tasks.md, CLAUDE.md
-
-### Content to NOT Translate
-
-1. **Code blocks**: Everything between ``` and ```
-2. **Inline code**: Text within backticks `...`
-3. **URLs**: All http/https links
-4. **File paths**: Paths like `/path/to/file`
-5. **Command examples**: Shell commands and options
-6. **Environment variables**: Variables like `$HOME`, `%USERPROFILE%`
-
-### Formatting Preservation
-
-1. **YAML frontmatter**: Keep unchanged
-2. **Markdown headings**: Translate text, preserve level (# ## ###)
-3. **Lists**: Translate items, preserve structure
-4. **Tables**: Translate content, preserve format
-5. **Admonitions**: Translate content, keep type (note, warning, tip)
-6. **Links**: Translate link text, preserve URL
-
-## Quality Standards
-
-Each translation should:
-
-1. **Be technically accurate**: Correct terminology and concepts
-2. **Read naturally**: Appropriate phrasing for target language
-3. **Maintain consistency**: Same term translated same way throughout
-4. **Preserve structure**: Same heading hierarchy and formatting
-5. **Respect glossary**: Follow terminology definitions
-
-## Example Usage
-
-```bash
-# Translate to all supported languages
-/codexspec:translate-docs
-
-# Translate to specific languages
-/codexspec:translate-docs --lang zh,ja
-
-# Incremental translation (only changed files)
-/codexspec:translate-docs --lang zh --incremental
-
-# Preview without writing files
-/codexspec:translate-docs --lang ko --dry-run
-```
-
-## Exit Codes
-
-- `0`: All translations completed successfully
-- `1`: Some translations failed (partial success)
-- `2`: All translations failed (complete failure)
-- `3`: Configuration error (missing source, invalid language)
-
-## Available Follow-up Commands
-
-After translation:
-
-- `/codexspec:check-i18n-semantics` - Verify translation quality
-- `uv run mkdocs build` - Test build with all languages
-
-> [!NOTE]
-> This command requires the source documentation to exist in `docs/en/`. Make sure Phase 1 (Foundation) tasks are completed before running translation.