스킬 requesting-code-review
📝

requesting-code-review

안전 ⚙️ 외부 명령어

請求 AI 程式碼審查

또한 다음에서 사용할 수 있습니다: davila7,sickn33,Cycleaddict,CodingCossack,obra,DYAI2025,DMJGilbert,Cygnusfear

開發者經常因為過於接近實作而忽略自己程式碼中的問題。此技能會派遣 AI 子代理程式來根據需求審查程式碼變更，在合併前檢查品質、架構、測試和生產環境就緒狀態。

지원: Claude Codex Code(CC)
🥉 74 브론즈
1

스킬 ZIP 다운로드

2

Claude에서 업로드

설정 → 기능 → 스킬 → 스킬 업로드로 이동

3

토글을 켜고 사용 시작

테스트해 보기

"requesting-code-review" 사용 중입니다. Request code review for my authentication module changes

예상 결과:

### Strengths
- Clean separation of concerns with auth service (auth.ts:1-50)
- Proper password hashing using bcrypt (hash.ts:15)
- Good test coverage for edge cases

### Issues

#### Important
1. **Missing token expiration check**
- File: auth.ts:45
- Issue: Tokens never expire, creating security risk
- Fix: Add expiration timestamp to JWT payload

#### Minor
1. **Inconsistent error messages**
- File: auth.ts:30-35

### Assessment
**Ready to merge: With fixes**

**Reasoning:** Core authentication logic is solid. Important issue with token expiration must be addressed before production use.

"requesting-code-review" 사용 중입니다. Review my database migration changes

예상 결과:

### Strengths
- Proper foreign key constraints (migrations/002.sql:20)
- Good rollback strategy

### Issues

#### Critical
1. **No backup before destructive operation**
- File: migrations/003.sql:15
- Issue: DROP TABLE without backup strategy
- Fix: Add data migration script or backup step

### Assessment
**Ready to merge: With fixes**

**Reasoning:** Critical data safety issue must be resolved.

보안 감사

안전
v1 • 2/24/2026

All 27 static findings are false positives. The skill uses legitimate git commands (git diff, git rev-parse) for code review - these are standard development operations. The detected 'weak cryptographic algorithm' patterns match the word 'security' in documentation headings, not actual crypto code. The 'system reconnaissance' matches are generic text. This is a safe code review workflow skill with no command injection risk - git commands use hardcoded arguments with template variable placeholders.

2
스캔된 파일
253
분석된 줄 수
1
발견 사항
1
총 감사 수

위험 요인

⚙️ 외부 명령어 (5)
code-reviewer.md:25-28 code-reviewer.md:112 SKILL.md:27-41 SKILL.md:51 SKILL.md:56-57

감지된 패턴

Git Command Execution (False Positive)Security Keyword Match (False Positive)Generic Text Pattern Match (False Positive)
감사자: claude

품질 점수

38
아키텍처
100
유지보수성
87
콘텐츠
50
커뮤니티
100
보안
91
사양 준수

만들 수 있는 것

合併前的程式碼審查

在合併功能分支前使用，以及早發現問題。子代理程式會根據需求審查所有變更並提供明確的準備就緒/未準備就緒判定。

子代理程式任務驗證

在代理程式驅動開發中每個子代理程式完成任務後，派遣程式碼審查者來驗證工作後再繼續下一個任務。

卡在問題上

當卡在複雜的錯誤或功能上時，請求程式碼審查以從 AI 子代理程式獲得關於潛在問題或更好方法的全新觀點。

이 프롬프트를 사용해 보세요

基本程式碼審查請求 
Request code review for the changes I just made. Use the requesting-code-review skill with: WHAT_WAS_IMPLEMENTED: [describe what you built], PLAN_OR_REQUIREMENTS: [link to plan or describe requirements], BASE_SHA: [starting commit], HEAD_SHA: [ending commit], DESCRIPTION: [brief summary]
完整功能審查 
Please review my latest feature implementation using the requesting-code-review skill. Compare against the requirements in docs/plans/[feature-name].md. Include architecture assessment and testing coverage evaluation.
子代理程式任務後審查 
Run the code-reviewer subagent to verify the task just completed. Check against the original task requirements and report any Critical or Important issues that need fixing before proceeding.
重構前的基準 
Request a code review of the current state of [component/module] before I refactor it. This will serve as a baseline to ensure the refactoring does not introduce regressions.

모범 사례

  • 請求審查時提供明確的需求或計劃參考 — 子代理程式會根據這些來比較實作
  • 在代理程式驅動開發中每個重要任務後進行審查，以防止問題累積
  • 在繼續之前修復 Critical 和 Important 問題；在後續工作中處理 Minor 問題

피하기

  • 因為變更看起來簡單就跳過審查 — 即使是小變更也可能有隱藏的錯誤
  • 忽略 Critical 問題或繼續進行未修復的 Important 問題
  • 請求審查時未提供明確的需求或計劃供子代理程式比較

자주 묻는 질문

此技能與直接使用 Claude 有何不同？
此技能會派遣具有結構化審查範本的专业程式碼審查子代理程式。它提供一致、全面的審查，並進行嚴重程度分類和生產環境就緒狀態評估。
這可以用於任何程式語言嗎？
可以。審查清單涵蓋適用於各種語言的通用程式碼品質、架構和測試原則。子代理程式會根據其審查的程式碼調整回饋。
如果我沒有正式的需求文件怎麼辦？
提供任何現有的文件、票證描述，或甚至是功能的清晰摘要。您提供的上下文越多，審查效果越好。
這會取代人類程式碼審查嗎？
不。這是 AI 輔助審查，可及早發現許多問題。人類審查對於上下文、團隊慣例和領域特定知識仍然很有價值。
如何取得 BASE_SHA 和 HEAD_SHA？
使用 git 命令：BASE_SHA=$(git rev-parse HEAD~1) 或特定提交，HEAD_SHA=$(git rev-parse HEAD) 取得最新。或者使用 origin/main 與 main 分支進行比較。
我可以自訂審查標準嗎？
可以修改 code-reviewer.md 範本以新增團隊特定檢查、語言特定指南或額外的審查標準。

개발자 세부 정보

작성자

ZhanlinCui

라이선스

MIT

리포지토리

https://github.com/ZhanlinCui/Ultimate-Agent-Skills-Collection/tree/main/requesting-code-review

참조

main

파일 구조

📄 code-reviewer.md

📄 SKILL.md