codexspec 0.5.17__tar.gz → 0.5.18__tar.gz

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

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

@@ -1,6 +1,6 @@
 [project]
 name = "codexspec"
-version = "0.5.17"
+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.17 → 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:*)
@@ -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