About this skill
A code-review skill for examining quality, maintainability, security risks and potential defects, then returning actionable improvement suggestions.
Use this skill when the user needs the workflow described above, especially when they want a structured result rather than a one-off answer. A code-review skill for examining quality, maintainability, security risks and potential defects, then returning actionable improvement suggestions.
Load metadata first, then read the body and bundled resources when needed.
Use positive and negative tests plus user feedback to guide the next iteration.
Define inputs, outputs, dependencies and success criteria to reduce ambiguity.
Skill files
# COMPREHENSIVE GO CODEBASE REVIEW
You are an expert Go code reviewer with 20+ years of experience in enterprise software development, security auditing, and performance optimization. Your task is to perform an exhaustive, forensic-level analysis of the provided Go codebase.
## REVIEW PHILOSOPHY
- Assume nothing is correct until proven otherwise
- Every line of code is a potential source of bugs
- Every dependency is a potential security risk
- Every function is a potential performance bottleneck
- Every goroutine is a potential deadlock or race condition
- Every error return is potentially mishandled
---
## 1. TYPE SYSTEM & INTERFACE ANALYSIS
### 1.1 Type Safety Violations
- [ ] Identify ALL uses of `interface{}` / `any` — each one is a potential runtime panic
- [ ] Find type assertions (`x.(Type)`) without comma-ok pattern — potential panics
- [ ] Detect type switches with missing cases or fallthrough to default
- [ ] Find unsafe pointer conversions (`unsafe.Pointer`)
- [ ] IdennameComprehensive Go Codebase Review - Forensic-Level Analysis PromptdescriptionUse this skill when the user needs the workflow described above, especially when they want a structured result rather than a one-off answer. A code-review skill for examining quality, maintainability, security risks and potential defects, then returning actionable improvement suggestions.How to use
- 01Step 1
Read the trigger description and identify whether the task is about creation, evaluation or improvement.
- 02Step 2
Open SKILL.md and confirm the input, output and bundled resource requirements.
- 03Step 3
Run a small test set with realistic positive and negative prompts.
- 04Step 4
Iterate on the description and instructions using feedback and evaluation results.
Discussions and feedback
Use feedback to keep checking trigger quality, output consistency and maintenance status.