Thanks for helping improve commitmentissues.dev.
- Keep PRs small and focused.
- One concern per PR (bugfix, feature, docs, or refactor).
- Preserve the existing product tone and UI style.
- Do not introduce heavy dependencies unless clearly justified.
npm install
npm run devOptional for higher GitHub API limits:
GITHUB_TOKEN=ghp_yourtokenRun:
npm run lint
npm testIf you changed runtime behavior, also run:
npm run build- Fork repo
- Create feature branch (
feat/...,fix/...,docs/...,chore/...) - Commit with clear message
- Open PR to
main
- Use issue templates when available.
- Include reproduction steps for bugs.
- Include acceptance criteria for feature requests.
Good first contributions:
- UI polish and micro-interactions
- Small bug fixes
- Docs improvements
- Tests around
src/lib/scoring.ts
Avoid in first PRs:
- Large rewrites
- Broad architecture refactors
- Unrelated cleanup mixed into feature work