ai_git 0.0.2 → 0.0.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 65259ec68cad081e1e9a8de3918eae4b338ae23211c5ccde67ef98e089d2fd29
-  data.tar.gz: 8de30045b286d41c52cd4bae828ae6236ae513a693c9fcc9dd2ba1fb4c30b197
+  metadata.gz: 36409c80888ac303814accb279c6908e55693271fc92b22c2eb151a0539285a4
+  data.tar.gz: b17d56e53f81da126bdd231d12964b799555231eab76dc2cf7002c3a4d01e368
 SHA512:
-  metadata.gz: ff8d20bb06a60b58e4a8fe07b4632541e8a2a8fc00ffd3d8f2b06d22a6800a06e04f59b6f14562104374640a21e44d0621d1621f25fda66da3fcb246144ddcc6
-  data.tar.gz: 9a32d475d621cfdc506f9c2459c879d9e33de9696e3feac98c755cb86066102cde8a05db2f769b6173cac16e32577940721464224e3a80165de46d28a99f5554
+  metadata.gz: e760bbd37b63c7ba1cfcb486e084742718033924990b590f03e51fd9c3ec31ece730c287c0f364680fff34962a68a9d4046f66611d2f9b350c8ac520a76f165d
+  data.tar.gz: e2d581350863a6b9dd6ff67a537b57aa126233f9cbfc921dcd63cd5f64b79cd404befff9e4157940f3ee921a4c47c4f749f37e12ed3d750fdb41f0e5303624c9

data/lib/ai_git/ollama.rb

@@ -14,36 +14,67 @@ module AIGit
         .gsub("\t", '\\t')
     end
 
-    def generate_commit_message(diff)
+    def generate_commit_message(diff, model_name)
       raise 'No staged changes to generate commit message for' if diff.to_s.strip.empty?
 
       prompt = <<~PROMPT
-    You are an expert Git commit message writer. Your only job is to output a commit message — nothing else.
+  You are an expert Git commit message writer. Output ONLY the commit message — no explanations, no markdown, no backticks, no preamble.
 
-    Here are the changes:
-    #{diff}
+  Here are the changes:
+  #{diff}
 
-    Rules you MUST follow exactly:
-    - Output ONLY the commit message. No explanations, no quotes, no markdown, no "Here is the commit message", no backticks.
-    - Use this exact structure:
-      1. First line: Conventional commit type + short imperative title (max 72 chars, ideally < 50)
-      2. Second line: blank
-      3. Body (optional but recommended): Clear, concise explanation of WHAT changed and WHY.
+  STRICT OUTPUT FORMAT (follow exactly):
 
-    Examples of good output:
-    feat: add user authentication flow
+  <short imperative title, max 72 chars>
 
-    Implemented JWT-based login with refresh tokens. Added protected routes middleware.
+  <blank line>
 
-    fix: prevent null pointer on missing metadata
+  ## Summary
+  <2–4 bullet points covering the most important changes. Each bullet starts with a verb.>
 
-    Added nil check in ReportGenerator#process before accessing user preferences.
+  ## Why
+  <1–3 sentences explaining the motivation or context behind the change. Omit if the reason is obvious.>
 
-    Now generate the commit message:
+  RULES:
+  - Title line: short, specific, imperative mood (e.g. "Add JWT login with refresh token support"). Avoid vague titles like "Update stuff" or "Fix bug".
+  - Summary bullets: describe WHAT changed, not HOW the code looks. Focus on behaviour and impact.
+  - Why section: explain the problem being solved or the goal being achieved. Skip if it adds no value.
+  - No filler phrases ("this commit", "this PR", "as per discussion").
+  - No line should exceed 72 characters.
+
+  EXAMPLES OF GOOD OUTPUT:
+
+  Add JWT-based login with refresh token support
+
+  ## Summary
+  - Implement login endpoint with access and refresh token issuance
+  - Add token refresh route with rotation and expiry validation
+  - Protect private routes via middleware that verifies access tokens
+  - Store refresh tokens using encrypted HTTP-only cookies
+
+  ## Why
+  Users were being logged out on every page reload. Refresh tokens allow
+  sessions to persist securely without requiring re-authentication.
+
+  ---
+
+  Prevent nil crash when user preferences are missing
+
+  ## Summary
+  - Add nil guard in ReportGenerator#process before accessing preferences
+  - Fall back to system defaults when preferences object is absent
+
+  ## Why
+  Reports were raising NoMethodError in production for users created
+  before the preferences feature shipped.
+
+  ---
+
+  Now generate the commit message:
       PROMPT
 
       json_body = {
-        model: 'phi4:14b',
+        model: model_name,
         prompt: prompt,
         stream: false,
         # These parameters help a lot with strictness:

data/lib/ai_git/version.rb

@@ -1,3 +1,3 @@
 module AIGit
-  VERSION = "0.0.2"
+  VERSION = "0.0.3"
 end

data/lib/ai_git.rb

@@ -7,18 +7,21 @@ module AIGit
   module_function
 
   def run
+    model_name = ENV["AI_GIT_MODEL_NAME"] || "phi4:14b"
+
     staged = AIGit::Git.staged_files
     abort 'Error: No staged files. Use `git add` first.' if staged.to_s.strip.empty?
 
     diff = AIGit::Git.diff
     branch = AIGit::Git.current_branch
 
+    puts "\e[1mModel Name:\e[0m #{model_name}"
     puts "\e[1mStaged Files:\e[0m #{staged}"
     puts "\e[1mBranch:\e[0m #{branch}"
     puts "\e[1mAI Generating Commit Message\e[0m"
 
     result = Benchmark.measure do
-      message = AIGit::Ollama.generate_commit_message(diff)
+      message = AIGit::Ollama.generate_commit_message(diff, model_name)
       message = message.gsub(/\n{2,}/, "\n")
 
       puts "\e[1mCommit Message:\e[0m\n\n#{message}\n"

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: ai_git
 version: !ruby/object:Gem::Version
-  version: 0.0.2
+  version: 0.0.3
 platform: ruby
 authors:
 - Kaíque Kandy Koga