SkillsAdd

smithery/doanchienthangdev

requesting-code-reviews

AI agent requests effective code reviews through proper preparation, clear descriptions, and appropriate reviewer selection. Use when creating PRs, requesting feedback, or submitting for review.

Installation

$ npx skills add smithery/doanchienthangdev --skill requesting-code-reviews
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

find-skills Same topic
vercel-labs/skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "fi…

3.3M installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-prepare Same topic
microsoft/azure-skills

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Te…

568.3K installs

Also in this package

Other skills from smithery/doanchienthangdev · top by installs.

npx skills add smithery/doanchienthangdev
verifying-before-completion 0 tracing-root-causes 0 thinking-sequentially 0 testing-omega-quality 0 Test Task Generation 0 Test Enforcement 0 styling-with-tailwind 0 rails 0 rag-systems 0 Processing Images 0

Browse all from smithery/doanchienthangdev

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,442 B
  • docs SUMMARY.md 225 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Requesting Code Reviews

Quick Start

  1. Self-Review - Review your own diff first, catch obvious issues
  2. Prepare Code - Tests pass, no debug code, documentation updated
  3. Write Description - Clear summary, changes list, testing info, screenshots
  4. Select Reviewers - Match expertise to changes, respect workload
  5. Time Appropriately - Early week, morning hours, avoid Fridays

Features

Feature Description Guide
Self-Review Catch issues before requesting Check debug code, TODOs, test coverage
PR Description Guide reviewers effectively Summary, changes, testing, attention areas
Reviewer Selection Match expertise to needs Code owner, domain expert, security reviewer
PR Sizing Optimal size for review quality <400 lines ideal, split larger PRs
Timing When to request reviews Morning, early week, check availability
Reviewer Guidance Help reviewers focus Key areas, skip suggestions, questions

Common Patterns

# PR Description Template
## Summary
[What changed and why - 2-3 sentences]
Resolves #123

## Changes
- [Bullet point each significant change]

## Testing
### Automated Tests
- [x] Unit tests added/updated
- [x] Integration tests pass

### Manual Testing
1. [Step to verify]
2. [Expected result]

## Screenshots
[For UI changes]

## Areas Needing Review
- Security: [specific file/concern]
- Performance: [specific concern]

## Checklist
- [x] Self-review completed
- [x] Tests pass locally
- [x] Documentation updated
# PR Size Guide
| Size | Lines | Review Time | Recommendation |
|------|-------|-------------|----------------|
| Small | <100 | 15-30 min | Ideal for quality review |
| Medium | <400 | 30-60 min | Acceptable |
| Large | <800 | 1-2 hours | Consider splitting |
| Too Large | 800+ | 2+ hours | Split required |

# Reviewer Selection
1. Code owner - maintains affected area
2. Domain expert - knows the technology
3. Security - for auth/crypto changes
4. Architecture - for design changes

Max reviewers: 4 (too many = diffused responsibility)
# Self-Review Checklist
[ ] No console.log/debug statements
[ ] No commented-out code
[ ] No hardcoded values (should be config)
[ ] Error handling appropriate
[ ] All tests pass
[ ] New code has tests
[ ] Complex logic has comments
[ ] Commit messages clear
[ ] Rebased on latest main

Best Practices

Do Avoid
Self-review first Submitting PRs without testing
Keep PRs small (<400 lines) Creating massive PRs
Write clear descriptions Leaving descriptions empty
Highlight key review areas Expecting reviewers to find everything
Choose reviewers wisely Overloading single reviewers
Be responsive to feedback Ignoring reviewer availability
Include screenshots for UI Rushing reviewers
Test thoroughly first Wasting reviewer time on broken code

Related Skills

  • receiving-code-reviews - Handle feedback professionally
  • finishing-development-branches - Complete PR preparation
  • verifying-before-completion - Pre-submission verification
  • writing-plans - Plan review-ready deliverables