Skip to content

fix: Require unique, unambiguous answers in generated flashcards#423

Merged
rjroy merged 1 commit intomainfrom
fix/question-specifity
Jan 26, 2026
Merged

fix: Require unique, unambiguous answers in generated flashcards#423
rjroy merged 1 commit intomainfrom
fix/question-specifity

Conversation

@rjroy
Copy link
Copy Markdown
Owner

@rjroy rjroy commented Jan 26, 2026

Summary

  • Added prompt guidelines requiring generated questions to have unique, unambiguous answers
  • Questions must include enough specifics (project name, feature name, date, version) to be uniquely identifiable
  • Explicitly discourages vague questions like "What did X implement?" that could have many valid answers

Test plan

  • Existing card-generator tests pass
  • Truncation test improved to check content directly rather than using fragile length arithmetic

🤖 Generated with Claude Code

Questions like "What did James implement?" fail because they could have
many valid answers depending on timeframe. Added prompt guidelines
requiring questions to include enough specifics (project name, feature
name, date) to uniquely identify what's being asked.

Also improved truncation test to check content directly rather than
using fragile length arithmetic.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@codecov
Copy link
Copy Markdown

codecov Bot commented Jan 26, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@rjroy rjroy merged commit 1727116 into main Jan 26, 2026
2 checks passed
@rjroy rjroy deleted the fix/question-specifity branch January 26, 2026 16:56
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