n2b 0.7.1 → 2.0.0

data/lib/n2b/message_utils.rb

@@ -0,0 +1,59 @@
+module N2B
+  module MessageUtils
+    MAX_MESSAGE_LENGTH = 500
+    TRUNCATION_NOTICE = "... (truncated)"
+
+    # Validates the message length.
+    # Truncates if it exceeds MAX_MESSAGE_LENGTH.
+    def self.validate_message(message_str)
+      return nil if message_str.nil?
+      # Ensure message is a string before calling length
+      message = String(message_str)
+      if message.length > MAX_MESSAGE_LENGTH
+        return message[0...(MAX_MESSAGE_LENGTH - TRUNCATION_NOTICE.length)] + TRUNCATION_NOTICE
+      end
+      message
+    end
+
+    # Performs basic sanitization on the message.
+    def self.sanitize_message(message_str)
+      return nil if message_str.nil?
+      message = String(message_str) # Ensure it's a string
+
+      # Strip leading/trailing whitespace
+      sanitized = message.strip
+
+      # Replace triple backticks with single backticks to prevent code block formatting issues in prompts
+      sanitized.gsub!('```', '`')
+
+      # Remove multiple consecutive newlines, leaving only single newlines
+      # This helps prevent prompt injection or excessive spacing.
+      sanitized.gsub!(/\n{2,}/, "\n")
+
+      # Example: Escape specific control characters if needed, e.g., null bytes
+      # sanitized.gsub!(/\x00/, '') # Remove null bytes
+
+      # Add more sanitization rules here as needed, e.g.:
+      # - Removing or escaping other characters that might break formatting or cause security issues.
+      # - For now, keeping it relatively simple.
+
+      sanitized
+    end
+
+    # Logs the message to STDOUT.
+    # level can be :info, :debug, :warn, :error
+    def self.log_message(message, level = :info)
+      return if message.nil? || message.strip.empty?
+
+      prefix = case level
+               when :debug then "[N2B Message DEBUG]"
+               when :warn  then "[N2B Message WARN]"
+               when :error then "[N2B Message ERROR]"
+               else "[N2B Message INFO]" # Default to info
+               end
+
+      output_stream = (level == :error || level == :warn) ? $stderr : $stdout
+      output_stream.puts "#{prefix} #{message}"
+    end
+  end
+end

data/lib/n2b/templates/diff_system_prompt.txt

@@ -1,23 +1,43 @@
+
 You are a senior software developer reviewing a code diff.
+
 Your task is to provide a constructive and detailed analysis of the changes.
 Focus on identifying potential bugs, suggesting improvements in code quality, style, performance, and security.
-Also, provide a concise summary of the changes.
-
-IMPORTANT: When referring to specific issues or improvements, always include:
-- The exact file path (e.g., "lib/n2b/cli.rb")
-- The specific line numbers or line ranges (e.g., "line 42" or "lines 15-20")
-- The exact code snippet you're referring to when possible
-
-This helps users quickly locate and understand the issues you identify.
-
-SPECIAL FOCUS ON TEST COVERAGE:
-Pay special attention to whether the developer has provided adequate test coverage for the changes:
-- Look for new test files or modifications to existing test files
-- Check if new functionality has corresponding tests
-- Evaluate if edge cases and error conditions are tested
-- Assess if the tests are meaningful and comprehensive
-- Note any missing test coverage that should be added
-
-NOTE: In addition to the diff, you will also receive the current code context around the changed areas.
-This provides better understanding of the surrounding code and helps with more accurate analysis.
-The user may provide additional instructions or specific requirements below.
+Also, provide a concise summary of the changes at the beginning.
+
+Important guidelines for your review:
+	•	When referring to specific issues or improvements, always include:
+	•	The exact file path (e.g., lib/n2b/cli.rb)
+	•	The specific line numbers or line ranges (e.g., “line 42” or “lines 15-20”)
+	•	The exact code snippet you’re referring to when possible
+This helps the recipient quickly locate and understand the issues you identify.
+	•	Be pragmatic and balanced:
+	•	Highlight genuinely critical issues, but avoid excessive speculation or alarmism.
+	•	Only flag a security or architectural problem as high-priority if there is clear evidence or reasonable suspicion based on the diff and provided context.
+	•	If you notice patterns that could be problematic (e.g., use of deprecated libraries or unclear data handling), mention them, but avoid assuming issues in unseen code unless the context clearly suggests a risk.
+	•	Limit your review to the provided context:
+	•	Do not assume missing methods or classes are absent or incorrectly implemented if they are simply not visible in the diff.
+	•	Focus your analysis on the code changes and their direct surroundings.
+	•	If code relies on methods or classes not included in the diff, you can briefly note that the implementation or contract is not visible, but do not speculate about their correctness unless the usage is clearly problematic.
+
+Special Focus: Test Coverage
+	•	Pay special attention to whether the developer has provided adequate test coverage for the changes:
+	•	Look for new test files or modifications to existing test files.
+	•	Check if new functionality is covered by corresponding tests.
+	•	Evaluate if edge cases and error conditions are tested.
+	•	Assess if the tests are meaningful and comprehensive.
+	•	Note any missing test coverage that should reasonably be added.
+
+Tone and Focus
+	•	Be clear, direct, and actionable, but keep a professional and supportive tone.
+	•	Prioritize feedback on issues that would materially affect the codebase, such as maintainability, correctness, reliability, and realistic security concerns.
+	•	Encourage improvements, but avoid nitpicking on trivial or subjective style points unless they significantly affect readability or consistency.
+
+⸻
+
+Summary:
+Provide a balanced, practical review of the visible code diff, focusing on genuine issues and actionable improvements. Avoid speculation about unseen code, and maintain a pragmatic and professional approach, especially regarding potential security concerns and architectural risks.
+
+⸻
+
+Let me know if you want any additional points, or further simplification!

data/lib/n2b/templates/github_comment.txt

@@ -0,0 +1,67 @@
+### N2B Code Analysis Report
+
+**Implementation Summary**
+{implementation_summary}
+
+{{#if custom_analysis_focus}}
+---
+
+**Custom Analysis Focus**
+> {{custom_analysis_focus}}
+{{/if}}
+---
+
+{#if critical_errors_empty}
+_No critical issues found._
+{#else}
+**Critical Issues**
+{#each critical_errors}
+- {file_reference} - {description}
+{/each}
+{/if}
+
+{#if important_errors_empty}
+_No important issues found._
+{#else}
+**Important Issues**
+{#each important_errors}
+- {file_reference} - {description}
+{/each}
+{/if}
+
+{#if improvements_empty}
+_No suggested improvements._
+{#else}
+**Improvements**
+{#each improvements}
+- {file_reference} - {description}
+{/each}
+{/if}
+
+{#if missing_tests_empty}
+_No missing tests identified._
+{#else}
+**Missing Tests**
+{#each missing_tests}
+- {description}
+{/each}
+{/if}
+
+**Requirements Status**
+{#each requirements}
+{#if status == 'IMPLEMENTED'}
+- ✅ {description}
+{/if}
+{#if status == 'PARTIALLY_IMPLEMENTED'}
+- ⚠️ {description}
+{/if}
+{#if status == 'NOT_IMPLEMENTED'}
+- ❌ {description}
+{/if}
+{#if status == 'UNCLEAR'}
+- 🔍 {description}
+{/if}
+{/each}
+
+*Generated on {timestamp} | Branch: {branch_name} | Files changed: {files_changed} | Lines: +{lines_added} -{lines_removed}*
+

data/lib/n2b/templates/jira_comment.txt

@@ -4,6 +4,13 @@
 *Implementation Summary:*
 {implementation_summary}
 
+{{#if custom_analysis_focus}}
+---
+*Custom Analysis Focus:*
+{quote}
+{{custom_analysis_focus}}
+{quote}
+{{/if}}
 ---
 
 *Automated Analysis Findings:*

data/lib/n2b/templates/merge_conflict_prompt.txt

@@ -3,7 +3,7 @@ You are a merge assistant. Combine the following conflict into a single version
 FULL FILE CONTENT FOR CONTEXT:
 {full_file_content}
 
-CONFLICT TO RESOLVE:
+CONFLICT TO RESOLVE (Lines {start_line}-{end_line}):
 Context before:
 {context_before}
 
@@ -17,4 +17,4 @@ Context after:
 {context_after}
 {user_comment}
 
-Respond in JSON with keys "merged_code" and "reason".
+Respond in JSON with keys "merged_code" and "reason". In your reason, reference the specific line numbers ({start_line}-{end_line}) that were affected by the conflict resolution.

data/lib/n2b/version.rb

@@ -1,4 +1,4 @@
 # lib/n2b/version.rb
 module N2B
-  VERSION = "0.7.1"
+  VERSION = "2.0.0"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: n2b
 version: !ruby/object:Gem::Version
-  version: 0.7.1
+  version: 2.0.0
 platform: ruby
 authors:
 - Stefan Nothegger
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2025-06-06 00:00:00.000000000 Z
+date: 2025-06-09 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: json
@@ -81,14 +81,17 @@ extensions: []
 extra_rdoc_files: []
 files:
 - README.md
+- bin/branch-audit.sh
 - bin/n2b
 - bin/n2b-diff
+- bin/n2b-test-github
 - bin/n2b-test-jira
 - lib/n2b.rb
 - lib/n2b/base.rb
 - lib/n2b/cli.rb
 - lib/n2b/config/models.yml
 - lib/n2b/errors.rb
+- lib/n2b/github_client.rb
 - lib/n2b/irb.rb
 - lib/n2b/jira_client.rb
 - lib/n2b/llm/claude.rb
@@ -98,10 +101,12 @@ files:
 - lib/n2b/llm/open_router.rb
 - lib/n2b/merge_cli.rb
 - lib/n2b/merge_conflict_parser.rb
+- lib/n2b/message_utils.rb
 - lib/n2b/model_config.rb
 - lib/n2b/template_engine.rb
 - lib/n2b/templates/diff_json_instruction.txt
 - lib/n2b/templates/diff_system_prompt.txt
+- lib/n2b/templates/github_comment.txt
 - lib/n2b/templates/jira_comment.txt
 - lib/n2b/templates/merge_conflict_prompt.txt
 - lib/n2b/version.rb
@@ -128,7 +133,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.5.22
+rubygems_version: 3.5.3
 signing_key:
 specification_version: 4
 summary: AI-powered development toolkit with merge conflict resolution and Jira integration