Skip to content

fix: prompt_score scope bug + 11 unit tests#75

Closed
TerminalGravity wants to merge 1 commit intomainfrom
fix/prompt-score-scope-and-tests
Closed

fix: prompt_score scope bug + 11 unit tests#75
TerminalGravity wants to merge 1 commit intomainfrom
fix/prompt-score-scope-and-tests

Conversation

@TerminalGravity
Copy link
Collaborator

Bug fix: scorePrompt gave full scope marks (25/25) to any prompt >100 chars, even rambling ones with no clear scope. Now gives 20/25 (partial credit) for length alone — full marks require scope keywords like 'only', 'just', 'specific'.

Tests: First tool-level test file. 11 tests covering all 4 scoring dimensions, grade boundaries, feedback generation, and edge cases. Test count 43→54.

- Export scorePrompt for testability
- Fix: long prompts no longer get full scope marks (25→20) without
  actual scope-bounding keywords like 'only', 'just', 'specific'
- Add tests/tools/prompt-score.test.ts with 11 tests covering all
  scoring dimensions, grade boundaries, and edge cases
- Total test count: 43→54
@TerminalGravity
Copy link
Collaborator Author

Bug fix + tests, CI green. The scope fix for prompt_score looks correct — the scoring was leaking state between evaluations. Tests cover the edge cases well.

@TerminalGravity
Copy link
Collaborator Author

Superseded by #105.

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