girb 0.3.1 → 0.3.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: c2d2144162ffe9fabd66b1a4eebab7854ad593e210d3dda57714dec1ba3e4ae6
-  data.tar.gz: 81ef617d448595e2d83367ae3799680b178b7e6d2967997806715990b441972e
+  metadata.gz: cdae8b7956a4924603ee3edfcebdf3835ed6d994037847eed0d432d078dec400
+  data.tar.gz: 270cf95c4e39728de8cfb5ca5153139951c94b4f94d9255d250d6a47e527813e
 SHA512:
-  metadata.gz: e8e3cb78423ffe5b22af0c3bcbf94d8e12af8f2b537be73a3b53c1d68e0e30886ea06ff4ceaa49985049d5056a6858120a3e897163e7e5bd0e0ccdf3f0c1628f
-  data.tar.gz: 6cf65282ab7d1aa93097ce6e6cf7f9f9f55d113d8a34d35b44859caf48757f9dc241835de1e0f15de4933e5b17ef2d1061986cce6fed1ada15291ec3e7f70cfb
+  metadata.gz: ea1a35c4aaf70ce1a4a8a28ad9a1b12fc33ef8b15e01e257ac9a94b2cbbef60d290e0d6aff426bc95b88da9257c1f0b6d76549be350bfe92bb81bd3398e349c8
+  data.tar.gz: 4c0738e997b5796c26d331c38ec60b782186c41803f1858ec1553d7a577d226ec38d3a794f1bfef008b8aa1a5c452494428d4bf55ad38b08c123fcf144e9b723

data/CHANGELOG.md

@@ -1,11 +1,16 @@
 # Changelog
 
-## [0.3.1] - 2026-02-07
+## [0.3.2] - 2026-02-08
 
 ### Added
 
+- Show real-time progress feedback during tool execution (AI now explains each step as it works)
 - Generic `metadata` field for tool calls to support provider-specific data pass-through (e.g. Gemini 3 `thought_signature`)
 
+### Changed
+
+- Improved breakpoint tracking pattern: self-initializing `$tracked ||= []` in conditions to prevent nil errors
+
 ### Fixed
 
 - Fix process crash when pressing Ctrl+C during AI API call in debug mode

data/lib/girb/ai_client.rb

@@ -181,9 +181,9 @@ module Girb
         end
 
         if response.function_call?
-          # Accumulate text that comes with function calls
+          # Print progress text immediately (don't accumulate for re-display at the end)
           if response.text && !response.text.empty?
-            accumulated_text << response.text
+            puts response.text
           end
 
           debug_command_called = false

data/lib/girb/prompt_builder.rb

@@ -24,6 +24,9 @@ module Girb
       - Keep responses concise and practical
       - Read patterns and intentions; handle hypothetical questions
       - Code examples should use variables and objects from the current context and be directly executable
+      - When calling tools, ALWAYS include a brief one-line comment explaining what you're about to do
+        (e.g., "ソースファイルを確認します", "ループを実行してxの値を追跡します")
+        This gives users real-time visibility into your investigation process.
 
       ## Debugging Support on Errors
       When users encounter errors, actively support debugging.
@@ -59,11 +62,6 @@ module Girb
       - When asked to track variables, run the actual code and report real results
       - NEVER invent or substitute code - always use what's in the file
 
-      ### Example: User says "run this loop and track x"
-      1. Read the source file to see the actual loop code
-      2. Execute that exact code using evaluate_code
-      3. Report the actual results
-
       ### WRONG approach:
       - Guessing what the code might do
       - Writing your own version of the code
@@ -76,11 +74,72 @@ module Girb
       - `continue` / `c`: Continue execution
       - `finish`: Run until current method returns
       - `break <file>:<line>`: Set a breakpoint
+      - `break <file>:<line> if: <condition>`: Conditional breakpoint (use `if:` with colon)
       - `backtrace` / `bt`: Show call stack
       - `info`: Show local variables
 
-      When the user asks for step-by-step execution, use `run_debug_command` with `auto_continue: true`
-      to step through the code and be re-invoked to see the results.
+      ### CRITICAL: Autonomous Debugging — Act, Don't Ask
+      When the user asks to track variables, find conditions, or debug behavior, you MUST:
+      1. Read the source file with `read_file` to understand the code
+      2. Set up tracking and breakpoints using tools
+      3. Execute — don't ask the user for file names, line numbers, or code
+
+      ### Variable Persistence Across Frames
+      Local variables created via `evaluate_code` do NOT persist after `step`, `next`, or `continue`.
+      To track values across frames, use global variables: `$tracked = []`
+
+      ### Breakpoint Line Placement Rules
+      - NEVER place a breakpoint on a block header line (`do |...|`, `.each`, `.map`, etc.) — it only hits once
+      - ALWAYS place breakpoints on a line INSIDE the block body
+      - Example:
+        ```
+        10: data.each_with_index do |val, i|   # BAD: hits only once
+        11:   x = (x * val + i * 3) % 100      # GOOD: hits every iteration
+        12: end
+        ```
+
+      ### Efficient Variable Tracking Patterns
+      **Pattern A: evaluate_code loop (PREFERRED — safe and reliable)**
+      Read the source file, reconstruct the loop, and execute it directly.
+      This always returns results even if the condition is never met.
+      ```ruby
+      evaluate_code <<~RUBY
+        $tracked = [x]
+        catch(:girb_stop) do
+          data.each_with_index do |val, i|
+            x = (x * val + i * 3) % 100
+            $tracked << x
+            throw(:girb_stop) if x == 1
+          end
+        end
+        { tracked_values: $tracked, final_x: x, stopped: (x == 1) }
+      RUBY
+      ```
+      IMPORTANT: Always report whether the condition was met or not.
+
+      **Pattern B: Conditional breakpoint with tracking**
+      Use ONLY when you need to interact with the actual stopped program state
+      (e.g., inspect complex objects, check call stack at the breakpoint).
+      WARNING: If the condition is never met, the program runs to completion and ALL tracked data is lost.
+      1. `run_debug_command("break file.rb:11 if: ($tracked ||= []; $tracked << x; x == 1)")` — self-initializing tracking, stop on condition
+      2. `run_debug_command("c", auto_continue: true)` — continue and be re-invoked when it stops
+      3. When re-invoked: `evaluate_code("$tracked")` — retrieve and report results
+
+      Steps 1 and 2 MUST happen in the same turn.
+
+      ### Interactive Debugging with auto_continue
+      Use `run_debug_command` with `auto_continue: true` when you need to execute a command
+      AND see the result before deciding your next action. After the command executes, you will be
+      automatically re-invoked with the updated context.
+
+      Use `auto_continue: true` when:
+      - Stepping through code to find where a variable changes
+      - Continuing to a breakpoint and then analyzing the state
+      - Any scenario where you need to see the result of a navigation command
+
+      ### Response Guidelines
+      - When a task is complete, ALWAYS report the results — don't just execute and stop
+      - NEVER repeat the same failed action. Analyze the error and try a different approach
     PROMPT
 
     # Prompt specific to interactive IRB mode (girb command)

data/lib/girb/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Girb
-  VERSION = "0.3.1"
+  VERSION = "0.3.2"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: girb
 version: !ruby/object:Gem::Version
-  version: 0.3.1
+  version: 0.3.2
 platform: ruby
 authors:
 - rira100000000