codexspec 0.6.4__tar.gz → 0.6.5__tar.gz

{codexspec-0.6.4 → codexspec-0.6.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: codexspec
-Version: 0.6.4
+Version: 0.6.5
 Summary: CodexSpec - A Requirements-First SDD toolkit for Claude Code
 Project-URL: Homepage, https://github.com/Zts0hg/codexspec
 Project-URL: Repository, https://github.com/Zts0hg/codexspec

{codexspec-0.6.4 → codexspec-0.6.5}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "codexspec"
-version = "0.6.4"
+version = "0.6.5"
 description = "CodexSpec - A Requirements-First SDD toolkit for Claude Code"
 readme = "README.md"
 requires-python = ">=3.11"

{codexspec-0.6.4 → codexspec-0.6.5}/src/codexspec/__init__.py

@@ -471,9 +471,11 @@ def init(
         "--force",
         "-f",
         help=(
-            "Overwrite existing files and auto-confirm prompts (skips the language "
-            "prompt and command-update/migration confirms). Language config is updated "
-            "surgically, never fully regenerated."
+            "Overwrite regenerable files (commands/scripts) and auto-confirm prompts "
+            "(skips the language prompt and command-update/migration confirms). "
+            "User-authored content is preserved: language config is updated surgically "
+            "and an existing CLAUDE.md body is never overwritten (only the constitution "
+            "@import is prepended if missing)."
         ),
     ),
     no_git: bool = typer.Option(
@@ -772,15 +774,19 @@ def init(
         console.print(f"[dim]{translate('cli.init.language_dimensions_hint', normalized_lang)}[/dim]")
 
     # Create CLAUDE.md
+    # CLAUDE.md is user-authored content (like the constitution), not a
+    # regenerable artifact (like commands/scripts). Never overwrite an existing
+    # body -- even under --force. --force only auto-confirms the one safe,
+    # idempotent change: prepending the constitution @import if it is missing.
     claude_md = target_dir / "CLAUDE.md"
-    if not claude_md.exists() or force:
+    if not claude_md.exists():
         project_name = target_dir.name
         claude_md.write_text(_get_claude_md_content(project_name), encoding="utf-8")
         console.print(f"[green]{translate('cli.init.created_file', normalized_lang, file='CLAUDE.md')}[/green]")
     else:
-        # Check if existing CLAUDE.md has compliance section
+        # Existing CLAUDE.md: ensure the compliance @import, never clobber the body.
         if not has_compliance_section(claude_md):
-            if confirm_add_compliance(normalized_lang):
+            if force or confirm_add_compliance(normalized_lang):
                 prepend_compliance_section(claude_md)
                 console.print(f"[green]{translate('cli.init.compliance_added', normalized_lang)}[/green]")
 

{codexspec-0.6.4 → codexspec-0.6.5}/templates/commands/implement-tasks.md

@@ -133,10 +133,103 @@ When encountering problems, create/update `issues.md` in the same directory as `
 - **Status**: Blocked / Workaround Found / Needs Discussion
 ```
 
-### 6. Completion
+### 6. Pre-Review Baseline
 
-After all tasks:
+After all tasks are implemented:
 
-- Run full test suite (if applicable)
-- Final commit if needed
-- Report completion summary with files modified
+- Run the full test suite.
+- Confirm the suite is green. This green state is the baseline for the Final
+  Code Review Loop; no auto-fix may regress it. If the suite is already red at
+  this point, stop and fix the implementation before reviewing.
+
+### 7. Final Code Review Loop
+
+After the baseline is green, review the implemented code and auto-fix verified
+defects. This mirrors the `review-spec` / `review-plan` / `review-tasks` loops
+the sibling generation commands run.
+
+#### 7.1 Determine the Review Target
+
+Review only the analyzable code changed by this implementation, not the whole
+repository and not per task. Compute the candidate file set:
+
+```
+git diff --name-only $(git merge-base HEAD <main>)..HEAD
+git diff --name-only                       # uncommitted tracked changes
+git ls-files --others --exclude-standard   # untracked files
+```
+
+`<main>` is the project's default branch, resolved from `git.main_branches` in
+`.codexspec/config.yml` (default: `main`, `master`, `develop`).
+
+Then filter the candidate set:
+
+- Keep only analyzable source extensions: `.py .ts .tsx .js .jsx .go .rs .java
+  .kt .kts .rb .sh .bash .zsh .c .h .cpp .hpp .cc .cxx .cs .swift .php`.
+- Exclude `.codexspec/specs/` and generated/vendored paths (e.g. `dist/`,
+  lockfiles, `.venv/`).
+
+If the filtered set is empty (e.g. the implementation produced only docs,
+config, or assets), report "no code to review", skip this loop, and proceed to
+step 8.
+
+Fallback: if git is unavailable or the current branch is not a feature branch
+(so the diff base cannot be determined), review the project's primary source
+directory as `/codexspec:review-code` would by default, and explicitly note the
+degraded fidelity (the review may include pre-existing code).
+
+#### 7.2 Invoke the Review
+
+Invoke `/codexspec:review-code <filtered-paths>`.
+
+`/codexspec:review-code` is **review-only**; it produces findings and scores but
+does not edit code. Apply every fix **yourself**, under this command's tool
+scope (which includes `Edit`/`Write` and running the test suite via `Bash`).
+
+#### 7.3 Auto-Fix Scope
+
+- Auto-fix **CRITICAL, HIGH, and MEDIUM** findings only.
+- **LOW** (suggestion) findings are report-only; never auto-fix them.
+- A **MEDIUM** finding is auto-fixed only when it is grounded in
+  `.codexspec/memory/constitution.md` and the confirmed requirements/spec, and
+  it concerns **maintainability, readability, or testability**. Ungrounded or
+  purely stylistic MEDIUM findings are report-only.
+- Do not auto-fix advisories or design opportunities, and do not introduce any
+  new product decision.
+
+#### 7.4 Test-Safe Fixes (never ship red)
+
+Every fix must be test-safe. A fix that breaks tests is, by definition, an
+incorrect change — it is never shipped and never silently skipped.
+
+- **Functional defects** (logic, correctness, security): follow TDD — add a
+  failing test that reproduces the defect (red), apply the fix until that test
+  passes (green), then refactor while tests stay green.
+- **Non-functional fixes** (refactors for maintainability, readability,
+  testability): run the suite before and after the change. If the change turns
+  any test red, revert it, confirm the suite is green again, and re-attempt the
+  refactor.
+- If a fix cannot be made green after retry, treat it as **unresolved** and stop
+  (see 7.5).
+
+#### 7.5 Loop Bounds and Stop Conditions
+
+- Run at most **two** fix-and-review rounds. (The per-fix TDD retry in 7.4
+  happens within a round; the two-round limit bounds overall effort.)
+- Stop when a defect repeats, remains unresolved, or requires a user or
+  architecture decision.
+- After each green round, commit the fixes (see step 8).
+
+#### 7.6 Terminal Status
+
+- If CRITICAL or HIGH defects remain unresolved after the maximum rounds, the
+  status is **"needs work"** — do not claim success.
+- Otherwise report the review outcome: scores, items fixed, items deferred, and
+  the final test status.
+
+### 8. Final Report and Commit
+
+- Commit any review-driven changes from step 7 that are not already committed.
+- Report the completion summary: files modified, review status (scores, items
+  fixed, items deferred, final test status), and the overall status (success or
+  "needs work").