Problem Statement
There is no CONTRIBUTING.md file. New contributors (especially GSSoC participants) have no documented process for: forking, branch naming, commit message style, running the project locally, or what to include in a PR. This leads to inconsistent PRs and repeated review feedback.
Proposed Solution
Create CONTRIBUTING.md at the repo root with:
- Local setup — clone, install, env vars,
npm run dev
- Branch naming —
feat/<description>, fix/<description>, docs/<description>
- Commit messages — Conventional Commits format
- PR checklist — runs without errors, no console warnings, screenshots for UI changes
- Code style — ESLint/Prettier config, no unused imports
- Issue claiming — comment on issue before starting work
Acceptance Criteria
Additional Context
This is especially important for GSSoC — most participants are making their first open source contribution. Clear guidelines reduce maintainer review burden significantly.
Problem Statement
There is no
CONTRIBUTING.mdfile. New contributors (especially GSSoC participants) have no documented process for: forking, branch naming, commit message style, running the project locally, or what to include in a PR. This leads to inconsistent PRs and repeated review feedback.Proposed Solution
Create
CONTRIBUTING.mdat the repo root with:npm run devfeat/<description>,fix/<description>,docs/<description>Acceptance Criteria
CONTRIBUTING.mdcreated at repo rootAdditional Context
This is especially important for GSSoC — most participants are making their first open source contribution. Clear guidelines reduce maintainer review burden significantly.