Users frequently switch back and forth between multiple AI tools, having them review each other's code changes. This skill standardizes the entire process, ensuring every handoff has a consistent format and a complete tracking record.
Determine identity
Determine which AI you are based on the execution environment:
- Claude Code →
claude - OpenAI Codex →
codex - Google Gemini →
gemini - Other → lowercase tool name
Review process
Whether the user invokes /discuss-multi-ai, or pastes in a review request containing a commit hash, the same process is followed.
1. Read the changes
When a commit hash is specified:
git show [commit hash]
git diff [commit hash]~1..[commit hash]
When no commit hash is specified:
Check git status：
- There are uncommitted changes: first understand the changes before entering the review
- No changes: use the latest commit (
git show HEAD）
2. Review item by item
For each change, check:
- Logical correctness and potential bugs
- Whether side effects are introduced or existing functionality is broken
- Code quality and consistency with project conventions
- Security considerations
- Any other points of disagreement or concern
3. Handle the review results
When there are concerns:
- Directly modify the code to resolve the issue
- In
docs/discuss-ai/create a documentation file, naming format:[AI名稱]-[commit短hash]-[簡述].md
Documentation file structure:
# 審議：[簡述主題]
- **來源 commit**: [完整 hash]
- **審議者**: [AI 名稱]
- **日期**: [YYYY-MM-DD]
## 變更摘要
[原始 commit 做了什麼]
## 疑慮與修改
### [檔案路徑]
**問題**：[描述問題]
**修改**：[說明如何修正]
**理由**：[為什麼這樣改比較好]
## 結論
[整體評估與建議]
When there are no issues:
- Clearly state agreement and explain why these changes are reasonable
- Do not make meaningless modifications just to assert your presence
- No need to create a documentation file
4. Commit the changes
Commit all modifications (including code fixes and documentation files) together:
discuss: [AI名稱] changes
[簡述本次審議的重點]
5. Output the review text
After committing is complete, obtain the commit hash and output the handoff text:
git rev-parse HEAD
If the user has provided a target AI name parameter, use that name; otherwise use "other AI".
Output text:
你的修改我跟 [AI名稱或「其他 AI」] 討論後他做了以下變更 commit [完整commit hash] 你評估看看有沒有問題，如果有任何不同意或疑慮的地方請直接修改，並建立文件進行詳細說明。
Tell the user they can copy this text and paste it into another AI tool.
Important principles
- Be truthful: if there are no issues, say there are no issues; do not make unnecessary modifications just to show presence
- Create documentation files only when there are substantive concerns：
docs/discuss-ai/is not a running log - Respect the original intent: understand the purpose of the change before evaluating it; do not reject logically correct code just because of style preferences
- Stay traceable: commit hashes and documentation files make the entire review process traceable