nadavWeisler / nadavWeisler/MedCodeTranslator
[Search] Improve search bug reporting and benchmark triage process
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 7m
- Merged PRs (30d)
- 7
Description
Problem summary
As real-world bug reports arrive, the project needs a lightweight process to evaluate whether issues are search-ranking problems, data problems, or UI problems — and route them to the right area labels.
Affected area
.github/ISSUE_TEMPLATE/bug_report.ymlagents/search-benchmarker/CONTRIBUTING.mdtriage workflow
Expected behavior
Search-related bug reports include enough structured detail (query, scheme, expected code, actual top result) to reproduce and optionally add a benchmark case.
Acceptance criteria
- Bug template prompts for scheme, query, expected code, and top-3 actual results.
- Triage doc explains how to convert repeatable search bugs into
data/benchmarks/cases. - At least one example benchmark case is added from a hypothetical or real report pattern.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with .github/ISSUE_TEMPLATE/bug_report.yml, then read the triage workflow in CONTRIBUTING.md and inspect agents/search-benchmarker/. Confirm how benchmark cases are represented under data/benchmarks/. Done means the template captures scheme, query, expected code, and top-three results, the triage path explains repeatable cases, and one example benchmark case is added.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, yaml
- Domain
- documentation, search, testing
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100