Analyze code changes and prioritize P0/P1/P2 issues before merging.
npx skills add https://github.com/huangwb8/skills --skill code-reviewer-huangwb8
Please help me install this Agent Skill. Skill: code-reviewer Source: https://github.com/huangwb8/skills/tree/main/awesome-code/agents/code-reviewer Command: npx skills add https://github.com/huangwb8/skills --skill code-reviewer-huangwb8
Identify and prioritize critical code quality issues (security, correctness, data integrity, maintainability) quickly, and provide actionable fixes to prevent merged defects.
Review the latest PR diff and generate a prioritized, actionable list of issues with suggested fixes.
High-intent search queries and answers about installing and using this skill.
Prioritize code review issues using a structured severity system like P0, P1, and P2. This guides developers to fix critical security, correctness, and data integrity defects first, ensuring fatal issues are caught early before merging.
A comprehensive code review checklist should include security, performance, maintainability, testing, and design checks. Standardizing these checks ensures consistent identification of critical code quality issues across different platforms and programming languages.
Write constructive feedback for a post-commit code review by using actionable and respectful templates. This approach guides developers with specific, prioritized fixes, maintaining code quality and team collaboration during feature completions and refactors.
Yes, you can apply a structured code review process across platforms and languages. By utilizing a standardized checklist and severity-based prioritization, you can identify critical maintainability and security issues regardless of the specific technology stack.
The best way to catch security and data integrity issues during a refactor is to analyze code changes against a comprehensive checklist. This identifies critical vulnerabilities quickly and provides actionable fixes to prevent merged defects.
Severity-based prioritization is needed for pull request reviews to quickly identify and address critical issues. Categorizing issues by P0, P1, and P2 prevents merged defects by guiding developers to resolve the most fatal problems first.
navidemadGenerate conventional commit messages and GitHub pull request descriptions.
phrazzldAudits a specified domain or diagnoses error messages to resolve the highest-priority issue.
eliottbusinessAutomate pre-commit code review with static analysis and security scanning.
richkuoAutomate GitHub issue implementation, pull request creation, and review feedback resolution.
