requesting-code-review
請求對已完成工作進行程式碼審查
متاح أيضًا من: DMJGilbert,sickn33,CodingCossack,Cycleaddict,Cygnusfear,obra,ZhanlinCui,DYAI2025
程式碼品質問題會隨著時間累積惡化。此技能提供了一個結構化的工作流程，可在完成開發任務後請求程式碼審查，在問題擴大之前發現錯誤和改進機會。
تنزيل ZIP المهارة
رفع في Claude
اذهب إلى Settings → Capabilities → Skills → Upload skill
فعّل وابدأ الاستخدام
اختبرها
استخدام "requesting-code-review". Request code review for my authentication module. Base SHA: a7981ec. Head SHA: 3df7661. What was implemented: User login and session management with JWT tokens. Requirements: auth-spec.md in docs folder.
النتيجة المتوقعة:
- ### Strengths
- - Clean separation of concerns in auth module (auth.ts:15-45)
- - Proper JWT token handling with expiration (token.ts:22-31)
- - Good test coverage for login flow (auth.test.ts:8-67)
- ### Issues
- #### Important
- 1. Missing rate limiting on login endpoint (auth.ts:89)
- Fix: Add express-rate-limit middleware
- #### Minor
- 1. Error messages reveal whether user exists (auth.ts:95)
- Impact: User enumeration risk in login form
- ### Assessment
- **Ready to merge: With fixes**
- **Reasoning:** Solid architecture with good security practices. Rate limiting should be added before production deployment.
التدقيق الأمني
آمنThis skill consists purely of documentation and prompt templates with no executable code. The static scanner misinterpreted shell command examples (shown as documentation to users) and git SHA references as actual security risks. No network calls, file system access, or environment variable reads occur. All 39 flagged findings are false positives.
عوامل الخطر
⚙️ الأوامر الخارجية (18)
🌐 الوصول إلى الشبكة (1)
درجة الجودة
ماذا يمكنك بناءه
每個任務後進行審查
在完成開發任務後立即發現問題，而不是等到後續的審查週期
合併前的品質閘道
透過結構化的審查流程，確保所有程式碼在合併到主分支前符合品質標準
驗證 AI 產生的程式碼
審查 AI 產生的實作，確認它們符合需求並遵循最佳實踐
جرّب هذه الموجهات
Request code review for my recent work. Base SHA: [git commit]. Head SHA: [current HEAD]. What was implemented: [brief description]. Requirements reference: [link to plan or requirements].
I just completed a major feature. Request comprehensive code review. Base SHA: [previous main]. Head SHA: [current]. Feature description: [what was built]. Full requirements: [spec document].
Request final code review before merging to main. Base SHA: [origin/main]. Head SHA: [current]. Description: [summary of all changes]. Assessment needed: production readiness, security concerns, and migration requirements.
Request code review before refactoring. Base SHA: [current HEAD]. Head SHA: [same as base - this is baseline]. Document current implementation strengths and weaknesses to establish refactoring baseline.
أفضل الممارسات
- 及早且頻繁地進行審查，而不是等待難以修改的大型 PR
- 在繼續下一個任務之前修復重要和較重要的問題
- 使用特定的 git SHA 以確保準確的差異審查
تجنب
- 因為程式碼看起來很簡單就跳過審查
- 為了節省時間而忽略重要問題
- 繼續處理可能有問題的未修復較重要問題