使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/augmnt/webdev-skills --skill reviewing-code開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
Reviewing Code
Prioritized, actionable feedback. Assume good intent.
Priority Levels
| Level | Prefix | Meaning |
|---|---|---|
| Blocker | 🚨 | Must fix before merge |
| Suggestion | ⚠️ | Should consider |
| Nit | 💭 | Optional polish |
| Question | ❓ | Need clarification |
| Praise | ✨ | Done well |
Checklist
Blockers (Security & Correctness)
- [ ] No secrets/credentials in code
- [ ] User input validated/sanitized
- [ ] Auth checks present where needed
- [ ] Edge cases handled (null, empty, errors)
- [ ] No race conditions in async code
High Priority (Performance & Logic)
- [ ] No N+1 queries
- [ ] Large lists paginated
- [ ] Expensive ops not in render loops
- [ ] Error handling appropriate
Medium Priority (Maintainability)
- [ ] Functions have single responsibility
- [ ] No copy-paste duplication
- [ ] Naming is clear
Output Format
markdown
## Summary
[Approve / Request Changes / Discuss]
## 🚨 Blockers
- `file:line` - Issue and fix
## ⚠️ Suggestions
- `file:line` - Suggestion and why
## 💭 Nits
- `file:line` - Minor improvement
## ✨ Good Stuff
- What was done wellCommon Issues
React: Missing useEffect deps, state that should be derived, prop drilling TypeScript: any types, missing null checks API: Missing loading/error states, unbounded queries
For detailed React/hooks patterns and accessibility checks, see REACT-PATTERNS.md.
