requesting-code-review
合併前請求程式碼審查
متاح أيضًا من: DMJGilbert,sickn33,CodingCossack,davila7,Cygnusfear,obra,ZhanlinCui,DYAI2025
手動程式碼審查耗時且不一致。此技能會派遣結構化的程式碼審查子代理，依據需求、架構標準和生產就緒標準系統性地評估程式碼變更。
تنزيل ZIP المهارة
رفع في Claude
اذهب إلى Settings → Capabilities → Skills → Upload skill
فعّل وابدأ الاستخدام
اختبرها
استخدام "requesting-code-review". Review Task 2: Add verification function for conversation index
النتيجة المتوقعة:
- ### Strengths
- - Clean architecture with proper separation of concerns
- - Comprehensive test coverage for all 4 issue types
- - Good error handling with descriptive messages
- ### Issues
- #### Important
- - Missing progress indicators (indexer.ts:130) - Users don't know operation progress
- - No timeout handling for long-running verifications
- #### Minor
- - Magic number (100) for reporting interval should be configurable
- - Could add more inline comments for edge case logic
- ### Assessment
- Ready to proceed after adding progress indicators
التدقيق الأمني
آمنThis is a documentation-only skill containing markdown files with code review guidelines and prompt templates. No executable code exists in the skill. All 35 static findings are false positives: the scanner incorrectly flagged documentation examples of git commands as 'external_commands', template placeholders like {HEAD_SHA} as 'weak cryptographic algorithms', and legitimate git operations as 'system reconnaissance'. This skill only provides markdown content to guide AI agents; it cannot execute commands, access filesystems, or make network calls.
عوامل الخطر
⚙️ الأوامر الخارجية (18)
🌐 الوصول إلى الشبكة (1)
درجة الجودة
ماذا يمكنك بناءه
審查已完成的任务
在子代理驅動開發中的每個任務之後，及時發現問題以避免問題在各任務之間累積
合併前品質把關
在合併到主分支之前審查程式碼，確保符合需求且架構健全
以新視角審視卡住的程式碼
當遇到問題卡住時，從系統化程式碼審查的角度獲得客觀的回饋意見
جرّب هذه الموجهات
Review the code I just implemented. Use the code-reviewer subagent. What was implemented: {WHAT_WAS_IMPLEMENTED}. Plan or requirements: {PLAN_OR_REQUIREMENTS}. Base commit: {BASE_SHA}. Head commit: {HEAD_SHA}.I completed a major feature. Request a code review using the requesting-code-review skill. Fill in: What was built: {WHAT_WAS_IMPLEMENTED}. Requirements: {PLAN_OR_REQUIREMENTS}. Git range from {BASE_SHA} to {HEAD_SHA}.Before merging to main, run a code review. Use superpowers:code-reviewer subagent with the full template from requesting-code-review/code-reviewer.md. Base: origin/main, Head: HEAD.
Perform comprehensive code review before production release. Use code-reviewer template. Include checking: code quality, architecture, security concerns, testing, migration strategy, backward compatibility, and documentation. Output strengths, issues by severity, and clear assessment.
أفضل الممارسات
- 在每個任務之後進行審查，而不只是合併前，這樣可以及早發現問題
- 始終取得 git SHA 值（BASE_SHA 和 HEAD_SHA）以進行準確的差異審查
- 根據回饋採取行動：立即修復 Critical 問題，在繼續之前修復 Important 問題
تجنب
- 因為程式碼看起來很簡單就跳過審查 - 小錯誤會累積
- 忽略 Critical 問題並繼續前進
- 回饋內容模糊，沒有具體的檔案:行號參考