aiskillstore/requesting-code-review
skills/dmjgilbert/requesting-code-review/SKILL.md
Request and process code reviews with proper context. Use after completing significant implementation work.
$ install --global
skillsauthnpx skillsauth add aiskillstore/marketplace requesting-code-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 1, 2026, 12:16 PM67.0s2 files scanned
SKILL.md
- name:
- requesting-code-review
- description:
- Request and process code reviews with proper context. Use after completing significant implementation work.
Requesting Code Reviews
Review early, review often - catch issues before they compound.
When Reviews Are Required
| Scenario | Timing | | --------------------------------- | ------------------ | | Each task in subagent-driven work | After each task | | Major feature completion | Before integration | | Before merging to main | Pre-merge | | When stuck on a problem | As needed | | Before refactoring | Pre-refactor | | After complex bug fix | Post-fix |
How to Request Review
1. Gather Context
# Get commit range for review
git log --oneline -5
git diff main..HEAD --stat
2. Dispatch Reviewer
Task(code-reviewer, prompt="
Review the changes in commits [base]..[head]
**What was implemented:**
[Description of changes]
**Requirements reference:**
[Link or description of requirements]
**Areas of concern:**
[Any specific areas you want extra attention]
**Files changed:**
[List key files]
")
3. Process Feedback
| Severity | Action Required | | --------- | ------------------------------------------ | | Critical | Fix immediately - blocks all other work | | High | Resolve before proceeding to next task | | Medium | Address in current session if time permits | | Low/Minor | Document for future improvement |
Review Request Template
## Code Review Request
**Commits:** [base-sha]..[head-sha]
**Branch:** [branch-name]
### Summary
[1-2 sentences on what changed]
### Changes by File
| File | Change Type | Description |
| ------------ | -------------- | -------------- |
| path/to/file | Added/Modified | [What changed] |
### Requirements
[Link to issue/spec or brief description]
### Testing Done
- [ ] Unit tests pass
- [ ] Integration tests pass
- [ ] Manual testing completed
### Areas Needing Attention
- [Specific concern 1]
- [Specific concern 2]
### Questions for Reviewer
- [Any specific questions]
Handling Feedback
Agree with Feedback
- Acknowledge the issue
- Fix immediately (Critical/High) or document (Medium/Low)
- Respond with what was changed
Disagree with Feedback
- Never dismiss without explanation
- Provide technical justification with evidence
- Reference code patterns or documentation
- Explain trade-offs considered
- Be open to being wrong
Example Response
## Review Response
### Critical Issues
- **[File:Line]**: Fixed - [what was changed]
### High Priority
- **[File:Line]**: Fixed - [what was changed]
### Disagreement: [Issue]
I believe [current approach] is correct because:
1. [Technical reason]
2. [Evidence from codebase]
However, open to discussion if I'm missing something.
### Deferred
- **[Minor issue]**: Added to tech debt tracker for future
Integration Points
- After executing-plans batches
- After systematic-debugging fixes
- Before finishing branches (merge/PR)
Related Skills
aiskillstore/hig-components-content
development
VerifiedTrustedCommunity
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/helpdesk-automation
tools
VerifiedTrustedCommunity
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/haskell-pro
testing
VerifiedTrustedCommunity
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/graphql
tools
VerifiedTrustedCommunity
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.
244SKILL.mdUpdated Apr 10, 2026