Skip to content

Vinix24/vnx-orchestration / skills/reviewer

reviewer

Verified

Senior engineer conducting thorough, constructive code reviews. Round-2+ reviews use adversarial framing to find missed cases and convergent failure modes.

FileKindSize
SKILL.mdskill md3.9 KB
references/_MAPPING.mdmarkdown341 B
scripts/intelligence.shexecutablescript1.3 KB
template.mdmarkdown1.5 KB

template.md

View on GitHub
# Reviewer Report Template

## Output Location
Write your report to: `$VNX_DATA_DIR/unified_reports/`

## Filename Format
`{timestamp}-{track}-review-{title}.md`

Example: `20260202-143000-C-review-authentication-pr.md`

## Report Structure

### Summary
Brief overview of code review findings (3-4 sentences)

### Tags (Required)
- [tag1, tag2, tag3]  # Use specific, compound tags (e.g., sse-streaming, browser-pool, kvk-validation). Avoid general-only tags.

### Code Quality Assessment
- Overall code quality score
- Adherence to coding standards
- Design pattern usage
- SOLID principles compliance

### Issues Found
#### Critical Issues
- Security vulnerabilities
- Data integrity risks
- Performance bottlenecks

#### Major Issues
- Design flaws
- Missing error handling
- Inadequate testing

#### Minor Issues
- Code style violations
- Documentation gaps
- Naming improvements

### Positive Observations
- Well-implemented patterns
- Good practices followed
- Effective solutions

### Detailed Findings
- File-by-file review comments
- Line-specific feedback
- Code snippets with issues
- Suggested improvements

### Recommendations
- Refactoring priorities
- Testing additions needed
- Documentation updates required
- Architecture improvements

### Intelligence Feedback
<!-- If your dispatch included [INTELLIGENCE_DATA] with offered_pattern_hashes, report which patterns you actually used: -->
used_pattern_hashes: []

## Quality Standards
- Check for security vulnerabilities
- Verify test coverage
- Ensure documentation completeness
- Validate performance implications
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 323kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 323kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 323kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 323kUpdated Claude CodeCodexVerifiedInstall