cmt-cli 1.1.2__tar.gz → 1.1.3__tar.gz

{cmt_cli-1.1.2 → cmt_cli-1.1.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: cmt-cli
-Version: 1.1.2
+Version: 1.1.3
 Summary: AI-powered Git commit message generator
 Project-URL: Homepage, https://github.com/bijaydas/cmt
 Project-URL: Documentation, https://github.com/bijaydas/cmt#readme

{cmt_cli-1.1.2 → cmt_cli-1.1.3}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "cmt-cli"
-version = "1.1.2"
+version = "1.1.3"
 description = "AI-powered Git commit message generator"
 readme = "README.md"
 requires-python = ">=3.12"

{cmt_cli-1.1.2 → cmt_cli-1.1.3}/src/cmt/ai/prompt.py

@@ -31,13 +31,22 @@ such as `chore`.
 10. Use imperative mood.
 11. Do not mention individual files unless necessary.
 12. Do not generate multiple commit messages.
-13. Do not include a commit body.
-14. Return ONLY the commit message.
-15. Do not include markdown, quotes, explanations, or additional text.
+13. Only add a description if the change is complex enough that the short description alone is
+insufficient to understand it (e.g., multiple distinct changes, non-obvious rationale, or
+breaking changes).
+14. When a description is required, format it as a bullet list, with one point per notable
+change, placed after a blank line following the short description.
+15. Keep each bullet point concise and in imperative mood.
+16. Return ONLY the commit message.
+17. Do not include markdown formatting (headers, bold, code blocks, etc.), quotes, explanations,
+or additional text, other than the hyphen-prefixed bullet list described above.
 
 ## Commit message format
 
 <type>[optional scope]: <short description>
+
+- <description bullet point 1>
+- <description bullet point 2>
 """
 
 COMMIT_DATA_PROMPT = """## Change statistics

{cmt_cli-1.1.2 → cmt_cli-1.1.3}/uv.lock

@@ -175,7 +175,7 @@ wheels = [
 
 [[package]]
 name = "cmt-cli"
-version = "1.0.3"
+version = "1.1.3"
 source = { editable = "." }
 dependencies = [
     { name = "langchain" },