First Issue Matcher
First Issue Matcher
Use this page when you want to contribute but do not know which issue to pick. Choose the row that matches your skill and time. Each route is scoped so a maintainer can review it quickly.
You do not need generated audio, local speech engines, private data, API keys, or app-store builds for any issue in the browser-only section.
Pick In One Minute
- Choose the row that matches your language, docs, mobile, API, or test skill.
- Open the issue and comment
/claimif you want the maintainer to reserve it for you. - Open the edit link, make one focused change, and put
Closes #ISSUE_NUMBERin the PR body.
If you are here from an external directory, the safest first PR routes are docs, wording review, beginner dialogue examples, API examples, and focused tests. They are useful even when you do not run the full mobile/backend stack.
Thirty-Second Match
| If you can help with… | Time | Start with | Edit path | Check |
|---|---|---|---|---|
| Korean wording or learner notes | 10-30 min | #46 sentence-final particles | edit Korean guide | Docs/content review only |
| Japanese naturalness | 10-30 min | #8 yui Japanese naturalness | edit story source | Keep line IDs stable |
| Beginner dialogue examples | 10-30 min | #36 restaurant preferences | edit variants CSV | Keep CSV columns unchanged |
| First-time OSS docs | 10-20 min | #44 first PR walkthrough | edit walkthrough | Docs review only |
| Local-first explanation | 10-20 min | #31 no-runtime-LLM FAQ | edit contributor page | Docs review only |
| Backend examples | 20-45 min | #19 provider status examples | edit API runbook | Docs review or API check |
| OpenAPI examples | 30-60 min | #24 auth device trust examples | edit OpenAPI contract | Keep YAML valid |
| Mobile accessibility | 30-60 min | #13 bottom tab touch targets | mobile source | npm run verify if possible |
| Python tests | 30-60 min | #49 malformed STT upload test | API tests | python -m pytest |
| Repo/community process | 10-30 min | #45 maintainer checklist | edit review runbook | Docs review only |
Low-Collision Starter-Issue Menu
These routes spread first PRs across different files and review lanes so contributors can choose work that improves the learner experience or project without all colliding on the same edit.
| Slot | Best for | Issue | First file |
|---|---|---|---|
| 1 | Korean setup docs | #1 | docs/backend/API_RUNBOOK.md |
| 2 | Japanese mobile docs | #2 | docs/ja/index.md |
| 3 | macOS STT setup docs | #3 | docs/backend/API_RUNBOOK.md |
| 4 | Local TTS setup docs | #4 | docs/backend/API_RUNBOOK.md |
| 5 | Architecture glossary | #5 | docs/ARCHITECTURE.md |
| 6 | API curl examples | #6 | docs/backend/API_RUNBOOK.md |
| 7 | Korean translation review | #7 | packs/yui/v1/story.json |
| 8 | Japanese naturalness | #8 | packs/yui/v1/story.json |
| 9 | Korean learner notes | #11 | docs/ko/index.md |
| 10 | Cultural review checklist | #12 | docs/community/CONTRIBUTOR_LANDING.md |
| 11 | Mock-mode docs | #16 | docs/ARCHITECTURE.md |
| 12 | Korean UI consistency | #18 | apps/mobile/src/i18n.ts |
| 13 | Provider-status examples | #19 | docs/backend/API_RUNBOOK.md |
| 14 | Match-threshold explanation | #20 | docs/ARCHITECTURE.md |
| 15 | OpenAPI examples | #24 | contracts/openapi_v0.yaml |
| 16 | Local-first FAQ | #31 | docs/index.md |
| 17 | Restaurant examples | #36 | packs/yui/v1/variants.csv |
| 18 | Fallback labels | #41 | docs/backend/API_RUNBOOK.md |
| 19 | Sentence-final particles | #46 | docs/ko/index.md |
| 20 | Cultural-safety examples | #47 | apps/mobile/src/culture/cultureNotes.ts |
If your first choice is already claimed, pick another row in the same skill area or ask in the First PR help desk.
If a listed issue is already claimed, use the no-install first PR board for more browser-editable options.
Quick Claim
- Open the issue.
- Comment
/claim. - Make one focused change.
- Open a PR with
Closes #ISSUE_NUMBERin the body. - Mention the check you ran, or write
Docs/content review only.
The repo will reply automatically with first-PR guidance after /claim and
mark the issue with the claimed label for maintainer triage.
Good PR Shape
Closes #ISSUE_NUMBER
What changed:
-
Review/check:
- Docs/content review only; no local setup required.
Notes:
- I did not add generated audio, archives, SQLite files, screenshots, secrets,
or local engine files.
What Makes a Useful Contribution
Useful docs, content review, accessibility, API examples, and tests solve a learner or project need. Keep the work focused, link the issue or problem in your PR, and avoid splitting trivial typo fixes across separate PRs.