Specify the code should be concise and clear like this:
### Code Quality: Always look back your git status and make sure build success before commit
- Before you commit to the git, or after you finish a task, you must follow the guidelines below:
- You need to watch the `git status`, and make sure if there is no more unnecessary code, and see if strictly followed my prompts. Change your persona as critical code-reviewer, and blame code if there is some code that doesn't need. Then tell to the user which code is unnecessary and removable at the summary.
- ALWAYS write human-readable code which is easy to understand and maintain even after a year when you look back. You can use any method to achieve this, such as using descriptive variable names, commenting your code, and writing modular code.
- You can easily delete code, functions or files if you are sure that it is not needed anymore. We have git, so you never need to worry about losing code.
- Make sure run and build success
- For javascript or typescript edits, you must ALWAYS run `pnpm build` to make sure there is no error when build. If you find an error, you must fix it and run build again.
- For tests, you must run `pnpm test` to make sure there is no error when test. If you find an error, you must fix it and run test again.
- For smoke tests, you must run the smoke test you edited/added and make sure it's successfully passed. (Fix it if you find an error) But if you don't have any environment variables to run, just STOP working.
