Thanks for contributing to clawvisual.
- Create an issue first for major changes.
- Keep changes focused and small when possible.
- Use English for code comments, commit messages, and error messages.
- Install dependencies:
npm install- Create env file:
cp .env.local.template .env.local- Start development server:
npm run devRun these before opening a PR:
npm run typecheck
npm run lintIf you changed behavior, add/update tests or evaluation cases when relevant.
- Use clear branch names, for example:
feat/landscape-ratioorfix/mcp-timeout. - Write concise commit messages in imperative mood.
- Prefer one logical change per commit.
Include in your PR:
- What changed
- Why it changed
- Any breaking changes
- How to test locally
For UI changes, include screenshots. For API changes, include example request/response.
When changing behavior, update related docs in:
README.mdREADME.zh-CN.mddocs/
- Never commit real API keys, tokens, or private data.
- Report vulnerabilities privately to maintainers instead of opening public issues.