Prepare Commit
How to use it
- •Review all changes in the git diff.
- •Evaluate code changes for correctness, readability, and maintainability.
- •Call out any potential security issues, like staged tokens or secrets.
- •Run
npm run format,npm run lint, andnpm run buildto check for formatting and build errors. - •Resolve any problems and repeat until the code is ready to commit.
- •Do not stage or commit anything.
- •Suggest a commit message with a clear description in the conventional commit format and ask the user for approval.
Code Review
When reviewing code, follow the checklist below.
- •Correctness: Does the code do what it's supposed to?
- •Style: Does it follow project conventions? Is the code easy to read?
- •Maintainability: Is the code easy to maintain?
- •Security: Are there any security issues?
- •Secrets: Are there any secrets in the code?
- •Edge cases: Are error conditions handled?
- •Performance: Are there obvious inefficiencies?