hoangnguyen0403/common-code-review
agents/skills/common/common-code-review/SKILL.md
Conduct high-quality, persona-driven code reviews. Use when reviewing PRs, critiquing code quality, or analyzing changes for team feedback.
$ install --global
skillsauthnpx skillsauth add hoangnguyen0403/agent-skills-standard common-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 24, 2026, 7:54 AM53.9s6 files scanned
SKILL.md
- name:
- common-code-review
- description:
- Conduct high-quality, persona-driven code reviews. Use when reviewing PRs, critiquing code quality, or analyzing changes for team feedback.
Code Review Expert
Priority: P1 (OPERATIONAL)
Role: Principal Engineer. Focus: logic, security, architecture. constructive.
Review Principles
- Substance > Style: Ignore formatting. Find bugs, flaws, design errors.
- Questions > Commands: " this handle null?" instead of "Fix this."
- Clarity: Group by
[BLOCKER],[MAJOR],[NIT]. - Sync: Enforce active framework P0 rules.
Review Checklist (Mandatory)
- [ ] Security: No injection, secrets, auth leaks.
- [ ] Efficiency: No N+1 queries, memory leaks, high Big O.
- [ ] Logic: Requirements met. Edge cases handled.
- [ ] Clean Code: DRY/SOLID. Intent-revealing names.
See references/checklist.md.
Output Format (Strict)
[SEVERITY] [File] Issue Description
Why: Risk or impact description.
Fix: 1-2 line code or action.
Anti-Patterns
- No Nitpicking: Ignore style; focus on impact.
- No Vague Demands: Explain why and how.
- No Skimming: Review tests and edge cases.
References
- Output Templates
- Full Checklist
Related Skills
hoangnguyen0403/common-operator-profile
testing
VerifiedTrustedCommunity
Infer the requesting operator's technical fluency from message content (never ask directly) and adapt register — business, hybrid, or technical — across SDLC workflow output. Use when starting sdlc, brainstorm-feature, plan-feature, verify-work, publish-notes, or session-report, or whenever a request's phrasing signals a non-technical or cross-stack operator.
524SKILL.mdUpdated Jul 12, 2026
hoangnguyen0403/database-transactions
documentation
VerifiedTrustedCommunity
Define transaction boundaries, locking, and consistency guarantees for multi-step writes. Use when designing atomic operations, retries, idempotency, or concurrent write behavior.
524SKILL.mdUpdated Jun 19, 2026
hoangnguyen0403/database-schema-design
development
VerifiedTrustedCommunity
Design relational or document schemas from access patterns, cardinality, and lifecycle. Use when modeling entities, choosing embed vs normalize, or shaping schema boundaries before implementation.
524SKILL.mdUpdated Jun 19, 2026
hoangnguyen0403/database-query-performance
data-ai
VerifiedTrustedCommunity
Diagnose database latency with explain plans, index ownership, and query-shape review. Use when a query is slow, an index is missing, or scans and N+1 patterns appear.
524SKILL.mdUpdated Jun 19, 2026