Transform pull request assessments into severity-labeled, structured feedback.
npx skills add https://github.com/Muvon/octomind-tap --skill code-review-muvon
Please help me install this Agent Skill. Skill: code-review Source: https://github.com/Muvon/octomind-tap/tree/main/skills/code-review Command: npx skills add https://github.com/Muvon/octomind-tap --skill code-review-muvon
This skill helps teams perform consistent, constructive code reviews by turning vague opinions into actionable, severity-based feedback that improves quality before merge.
Ask the AI to review the changes in your pull request and produce a checklist-based set of comments with severity labels, focusing on correctness, tests, security, and readability.
High-intent search queries and answers about installing and using this skill.
Standardizing code review involves applying structured, severity-labeled feedback to pull requests. It enforces coverage across correctness, design, readability, tests, security, and performance, transforming vague opinions into actionable, constructive guidance for developers.
To structure PR comments constructively, use clear severity labels such as nit, suggestion, question, issue, or blocker. Provide specific, line-level references to code changes so that the developer receiving feedback can resolve, fix, or explain decisions respectfully.
A thorough PR reviewer checklist should cover correctness, design, readability, tests, security, and performance. Reviewing these dimensions ensures that engineering best practices are met and that code quality is verified before merging changes into the codebase.
Yes, this code review process is language-agnostic and applies to any development workflow. It focuses on establishing team review norms and evaluating code correctness, security, and performance without relying on language-specific linting tools or frameworks.
Preparing code for review requires checking changes against a structured rubric of design, readability, tests, security, and performance. Self-assessing your pull request against these criteria before submission helps minimize blockers and severe issues.
Using severity labels like issue, suggestion, or blocker standardizes assessment and clarifies urgency. It transforms subjective opinions into actionable feedback, ensuring reviewers communicate effectively and developers understand exactly what must be fixed before merge.
BhaveshYReview code diffs and generate code health checklists.
mr-daedaliumMerge PRs, trigger deployment, and verify canary health in CI/CD pipelines.
gztcodeAutomate code review with static security scanning, quality gates, and an independent reviewer subagent.
monforjeEvaluate Go code against golangci-lint style guidelines.
