kaminocorp/hermes-alpha/requesting-code-review
Claude Code and agent skill by kaminocorp/hermes-alpha
- community
Checking that the SKILL.md file is still in the repository.
Use when completing tasks, implementing major features, or before merging. Validates work meets requirements through systematic review process.
Install
npx vskill@latest install kaminocorp/hermes-alpha/requesting-code-reviewSKILL.md
The same SKILL.md was published earlier as kaminocorp/hermes-alpha/requesting-code-review.
Requesting Code Review
Overview
Dispatch a reviewer subagent to catch issues before they cascade. Review early, review often.
Core principle: Fresh perspective finds issues you'll miss.
When to Request Review
Mandatory:
- After each task in subagent-driven development
- After completing a major feature
- Before merge to main
- After bug fixes
Optional but valuable:
- When stuck (fresh perspective)
- Before refactoring (baseline check)
- After complex logic implementation
- When touching critical code (auth, payments, data)
Never skip because:
- "It's simple" — simple bugs compound
- "I'm in a hurry" — reviews save time
- "I tested it" — you have blind spots
Review Process
Step 1: Self-Review First
Before dispatching a reviewer, check yourself:
- [ ] Code follows project conventions
- [ ] All tests pass
- [ ] No debug print statements left
- [ ] No hardcoded secrets or credentials
- [ ] Error handling in place
- [ ] Commit messages are clear
Step 2: Gather Context
Step 3: Dispatch Reviewer Subagent
Use delegate_task to dispatch a focused reviewer:
Step 4: Act on Feedback
Critical Issues (block merge):
- Security vulnerabilities
- Broken functionality
- Data loss risk
- Test failures
- Action: Fix immediately before proceeding
Important Issues (should fix):
- Missing edge case handling
- Poor error messages
- Unclear code
- Missing tests
- Action: Fix before merge if possible
Minor Issues (nice to have):
- Style preferences
- Refactoring suggestions
- Documentation improvements
- Action: Note for later or quick fix
If reviewer is wrong:
- Push back with technical reasoning
- Show code/tests that prove it works
- Request clarification
Review Dimensions
Correctness
- Does it implement the requirements?
- Are there logic errors?
- Do edge cases work?
- Are there race conditions?
Code Quality
- Is code readable?
- Are names clear and descriptive?
- Is it too complex? (Functions >20 lines = smell)
- Is there duplication?
Testing
- Are there meaningful tests?
- Do they cover edge cases?
- Do they test behavior, not implementation?
- Do all tests pass?
Security
- Any injection vulnerabilities?
- Proper input validation?
- Secrets handled correctly?
- Access control in place?
Performance
- Any N+1 queries?
- Unnecessary computation in loops?
- Memory leaks?
- Missing caching opportunities?
Review Output Format
Standard format for reviewer subagent output:
Integration with Other Skills
With subagent-driven-development
Review after EACH task — this is the two-stage review:
- Spec compliance review (does it match the plan?)
- Code quality review (is it well-built?)
- Fix issues from either review
- Proceed to next task only when both approve
With test-driven-development
Review verifies:
- Tests were written first (RED-GREEN-REFACTOR followed?)
- Tests are meaningful (not just asserting True)?
- Edge cases covered?
- All tests pass?
With writing-plans
Review validates:
- Implementation matches the plan?
- All tasks completed?
- Quality standards met?
Red Flags
Never:
- Skip review because "it's simple"
- Ignore Critical issues
- Proceed with unfixed Important issues
- Argue with valid technical feedback without evidence
Quality Gates
Must pass before merge:
- [ ] No critical issues
- [ ] All tests pass
- [ ] Review verdict: APPROVE
- [ ] Requirements met
Should pass before merge:
- [ ] No important issues
- [ ] Documentation updated
- [ ] Performance acceptable
Remember
A good review catches what you missed.
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckinghermes-agent/skills/software-development/requesting-code-review/SKILL.md
Popularity
- Repository stars
- 228
- Repository forks
- 34
- 7-day trend score
- 27
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/kaminocorp/hermes-alpha/requesting-code-review)