Skip to content

fix(extraction): change cases abstract to descriptive format (Issue #640)#641

Open
jlin53882 wants to merge 1 commit intoCortexReach:masterfrom
jlin53882:fix/bigint-prompt-issue
Open

fix(extraction): change cases abstract to descriptive format (Issue #640)#641
jlin53882 wants to merge 1 commit intoCortexReach:masterfrom
jlin53882:fix/bigint-prompt-issue

Conversation

@jlin53882
Copy link
Copy Markdown
Contributor

Summary

Fix Issue #640: Smart-extractor skips [cases] category due to misleading BigInt prompt guidance

Problem

The abstract in cases category prompt was written in imperative format:

abstract: "LanceDB BigInt error -> Use Number() coercion before arithmetic"

This made the LLM interpret it as "skip memories about this" rather than "this is what the case is about", causing:

  • stats.created = 0
  • stats.merged = 0
  • stats.skipped > 0
  • Triggers "falling back to regex capture"

Solution

Changed abstract from imperative to descriptive format:

abstract: "LanceDB BigInt numeric handling issue"

This describes what the case IS, not what to DO with it.

Changes

  • src/extraction-prompts.ts: Updated cases category abstract
  • test/issue-640-bigint-prompt.test.mjs: Added unit test

Test Results

=== Issue #640: BigInt Prompt Format Test ===
[Old format (buggy) - should be detected as misleading]
  Misleading: true (expected: true) ✅ PASS

[New format (fixed) - should NOT be misleading]  
  Misleading: false (expected: false) ✅ PASS
----------------------------------------
Total: 2 passed, 0 failed
----------------------------------------

Related

…ortexReach#640)

- Changed abstract from imperative to descriptive format
- Old: 'LanceDB BigInt error -> Use Number() coercion before arithmetic'
- New: 'LanceDB BigInt numeric handling issue'
- Added unit test to verify prompt format detection
@chatgpt-codex-connector
Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant