code-review

Review Go code for idioms, testing patterns, security, and project conventions.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/riddopic/cc-tools --skill code-review-riddopic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/riddopic/cc-tools/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/riddopic/cc-tools --skill code-review-riddopic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the code review process by providing a structured checklist and verification protocol to ensure code adheres to project standards, best practices, and security guidelines, reducing manual oversight and improving overall code quality.

Core Features & Use Cases

  • Structured Review Checklists: Guides reviewers through common and judgment-based issues.
  • Verification Protocols: Ensures thorough checks for specific issue types like "unused variables" or "missing error handling."
  • Severity Calibration: Helps reviewers distinguish between critical bugs and minor style preferences.
  • Use Case: When reviewing a pull request, use this Skill to systematically check for potential goroutine leaks, ensure interfaces are well-defined, and verify that error handling is robust before approving the changes.

Quick Start

Use the code-review skill to apply code review standards to the provided code snippet.

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I apply Go idioms and project conventions to a pull request code review?

Use a structured code review checklist to systematically verify Go idioms, testing patterns, security, and project conventions, reducing manual oversight and ensuring code quality.

What is the best way to verify error handling and check for goroutine leaks in Go?

Use a verification protocol during code review to systematically check for potential goroutine leaks, ensure interfaces are well-defined, and verify robust error handling in your Go code.

How does severity calibration distinguish between critical bugs and minor style preferences?

Severity calibration distinguishes critical bugs from minor style preferences by guiding reviewers through judgment-based issue identification, ensuring code quality and maintainability.

Can I use a structured review checklist to ensure software security and testing patterns?

Yes, structured review checklists guide reviewers through common and judgment-based issues, applying verification protocols to ensure software adheres to security guidelines and testing patterns.

What are the limitations of automated checks compared to judgment-based code review?

Automated checks cannot identify nuanced judgment-based issues; a structured review workflow with pre-report verification checklists is needed to catch complex problems like missing error handling.