code-reviewer
Reviews code changes for bugs, security vulnerabilities, and performance issues.
- License 许可
- MIT
- 所属仓库
- goffity/dev-km
- 最近更新
- 2026-11-10
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- code-reviewer
- context
- fork
- description
- Reviews code changes for bugs, security vulnerabilities, and performance issues.
- user-invocable
- false
02 资源文件 2
- 参考文档example.html32.3 KB
- 参考文档README.md2.6 KB
03 SKILL.md 正文
Code Reviewer
Automated code review agent ตรวจสอบ code quality ก่อน commit หรือ push
Purpose
- ตรวจหา bugs และ logic errors
- ตรวจสอบ security vulnerabilities
- วิเคราะห์ performance issues
- ตรวจสอบ code style และ best practices
- หา potential edge cases
When to Use
- ก่อน commit code changes
- ก่อน push to remote
- เมื่อต้องการ review code ที่เขียนเสร็จ
- ใช้กับ
/reviewcommand
Instructions
Step 1: Identify Changed Files
git diff --name-only HEAD
git diff --cached --name-only
Step 2: Analyze Each File
For each changed file:
- Read the file using Read tool
- Analyze for issues:
- Logic errors and bugs
- Security vulnerabilities (injection, XSS, etc.)
- Performance problems (N+1 queries, memory leaks)
- Code duplication
- Missing error handling
- Hardcoded values that should be configurable
Step 3: Categorize Issues
| Severity | Meaning | Action |
|---|---|---|
| Critical | Must fix before merge | Block |
| Warning | Should fix | Review |
| Info | Nice to have | Optional |
Step 4: Check Best Practices
- [ ] Functions are small and focused
- [ ] Variables have meaningful names
- [ ] Error handling is comprehensive
- [ ] No commented-out code
- [ ] No debug/console statements
- [ ] Tests cover new functionality
Step 5: Security Checklist
- [ ] No hardcoded secrets/credentials
- [ ] Input validation present
- [ ] SQL/NoSQL injection prevention
- [ ] XSS prevention (if applicable)
- [ ] Authentication/Authorization checks
- [ ] Sensitive data not logged
Output Format
## Code Review Report
**Files Reviewed:** N files
**Issues Found:** X critical, Y warnings, Z info
---
### Critical Issues
#### [filename:line]
**Issue:** Description of the problem
**Risk:** Why this is critical
**Fix:** Suggested solution
---
### Warnings
#### [filename:line]
**Issue:** Description
**Recommendation:** Suggested improvement
---
### Info
#### [filename:line]
**Note:** Observation or suggestion
---
## Summary
| Category | Count |
|----------|-------|
| Critical | X |
| Warnings | Y |
| Info | Z |
**Recommendation:** [APPROVE / REQUEST CHANGES / BLOCK]
04 同仓库更多 Skills
wait-what
Stop. That last message did not land: re-pitch it.
tdd
Test-driven development loop (red-green-refactor) with commit-based phase state and Jira traceability. Use when the user wants to build a feature or fix a bug test-first, mentions "tdd", "red-green-refactor", or "test-first". Replaces the tdg plugin — combines its commit/phase discipline with seam-based test quality rules from kb Testing Standards.
td
Creates post-task retrospectives with Before/After context and session documentation.
summary
Generates weekly or monthly session summaries from retrospectives and activity logs.
share
Shares knowledge across projects by copying to shared-knowledge directory with cross-project metadata.
session-analyzer
Analyzes git changes and creates retrospective drafts with Before/After context.