Implementation must be test driven with all relevant and affected tests passing. Run linting and formatting (npm run checks) and ensure the build succeeds (npm run build).
Create focused PRs with meaningful titles that describe what the change accomplishes. The description must explain what the PR introduces and why it's needed. Document any important design decisions or architectural choices. Keep PRs small and focused for easier review and incremental feedback.
Use conventional commits and communicate the why, not just what. Focus on the reasoning behind changes rather than describing what was changed.
Project root path can be specified so that tests can be run from any directory in the project. For security, validate that the project root path is absolute and that it is the current working directory or an ancestor of it. Relevant cases must be added to reporter integration tests.
No emojis in code or documentation. Avoid generic or boilerplate content. Be deliberate and intentional. Keep it clean and concise.
- Development Guide - Setup instructions and testing
- Dev Container setup - Consistent development environment