# Ask Code Reviewer

> Start code reviews, PR checks, or bug analysis. Triggers: "review my code", "check this PR", "analyze for bugs", "code review". Do NOT use for: - Automating fixes (use `ask-python-refactor`). - Generating new features. Capabilities: - Static analysis: Correctness, Security, Performance, Style. - Feedback priority: Critical > Performance > Style.

- Skill: `navanithans/ask-code-reviewer` (Agent Skill, multi-file: 7 files)
- Install (CLI): `npx skillmds@latest add navanithans/ask-code-reviewer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/navanithans/ask-code-reviewer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: NavanithanS (https://skillmd.com/u/navanithans)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/navanithans/ask-code-reviewer

---


# Code Review Protocol

## <critical_constraints>
1. ❌ **NO** commands. Frame suggestions as questions ("Why not use X?" vs "Use X").
2. ❌ **NO** unexplained changes. Explain *why* it improves code.
3. ✅ **MUST** prioritize Critical (Bugs/Security) > Style.
4. ✅ **MUST** use `assets/report_template.md`.
5. ✅ **MUST** be constructive.
</critical_constraints>

## <process>
1. **Context**: identify language, framework, purpose.
2. **<thinking> Deep Scan**:
   - Check against `assets/checklist.md`.
   - **Correctness**: Logical flaws, null checks, race conditions.
   - **Security**: Injection, XSS, Secrets.
   - **Performance**: Big O, N+1 queries, leaks.
   - **Style**: Naming, idioms.
   </thinking>
3. **Draft Report**:
   - Group by severity.
   - Include Location, Problem, Suggested Fix.
4. **<validation_gate>**:
   - Check tone. Ensure critical issues have fixes.
   - Run validation script.
   </validation_gate>
5. **Final Output**: Present Markdown report.
</process>

## <templates>
See `assets/report_template.md`.
</templates>