code-review-assistant

Systematic code review checklist and pre-commit quality gates for PRs.Use when: reviewing pull requests, checking code quality, before committing code.Keywords: review, PR, pull request, checklist, quality, commit, 審查, 檢查, 簽入.

44stars10forksUpdated 2/25/2026

Security Code Review Documentation #pre-commit #security #quality-assurance #pull-request #documentation #code-review

Security Assessment

Safe(100/100)

Security Score100/100

About code-review-assistant

The code-review-assistant skill provides a systematic approach to code reviews and pre-commit checks, aiming to improve the overall quality of code before merging it into a project. It offers a structured checklist to ensure that every pull request (PR) is evaluated against essential quality, functionality, security, and performance criteria, helping teams maintain high standards and avoid common issues such as security vulnerabilities, poor performance, and inconsistent code formatting. By using this skill, teams can establish a more reliable and effective code review process, reducing the risk of bugs and technical debt in their codebase.

FAQ

What is the purpose of the code-review-assistant skill?

The purpose of the code-review-assistant skill is to provide a standardized checklist for reviewing code, ensuring it meets quality, security, performance, and readability standards before it is committed to the project.

Can this skill be used for any programming language?

Yes, the skill can be used with any programming language, as the guidelines focus on general code quality and process rather than specific syntax or language features.

How does the skill handle project-specific configurations?

The skill supports project-specific configurations by detecting settings from the project's `CONTRIBUTING.md` file, such as the language for code review comments and whether the skill is enabled or disabled.

What should I do if there is no configuration in the project?

If no configuration is found, the skill will prompt you to choose a language for the code review comments and suggest documenting the choice in the project's `CONTRIBUTING.md` file.

Are there any pre-commit checks required by this skill?

Yes, the pre-commit checklist includes ensuring that the build succeeds, all tests pass, the code follows project standards, no security vulnerabilities exist, documentation is updated, and the branch is synced with the target branch.