Menu
代码追溯专家 - 查找代码修改者、关联PR、获取改动背景。 触发词: 谁改的, 谁写的, blame, 追溯, 找作者, 这行代码, 提交记录, 谁提交的, PR, 代码历史
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when about to claim work is complete, fixed, passing, verified, release-ready, or ready to commit, merge, publish, or hand off.
Manage persistent coding sessions across Claude Code, Codex, Gemini, Cursor, and OpenCode engines. Use when orchestrating multi-engine coding agents, starting/sending/stopping sessions, running multi-agent council collaborations, cross-session messaging, ultraplan deep planning, ultrareview parallel code review, autoloop autonomous workspace iteration, ultraapp building deployable web apps from a structured Q&A interview, switching models/tools at runtime, or exposing the orchestrator's 65 tools as an MCP server to Hermes Agent / Claude Desktop / Cursor / Cline / Continue / Zed / Windsurf / Goose. Triggers on "start a session", "send to session", "run council", "ultraplan", "ultrareview", "autoloop", "ultraapp", "Forge tab", "build a web app", "one-click app", "AppSpec", "autonomous iteration", "iterate until goal", "deep paper review", "auto research", "switch model", "multi-agent", "coding session", "session inbox", "cursor agent", "opencode", "mcp server", "clawo-mcp", "hermes mcp", "model context protocol
Use when starting a turn or checking Aegis skill routing.
Summarizes WeChat group chat highlights into a structured digest using the local wx-cli binary (https://github.com/jackwener/wx-cli). Generates a normal digest by default; a roast (毒舌) version is opt-in. Maintains per-group history (history.json + history-digests.jsonl), per-user profiles, and per-group fact memory (memory.md) across runs, with privacy guardrails baked in. Use when the user asks to "总结群聊", "群聊精华", "群聊摘要", "summarize group chat", "group chat digest", mentions a WeChat group name with a time range, says "帮我看看 XX 群最近聊了什么", "XX 群有什么值得看的", or asks to "回溯画像" / "初始化画像" / "backfill profiles". Adds the roast version when the user says "毒舌版", "roast 版", "再来个毒舌的", or similar.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
| name | git-blame |
| description | 代码追溯专家 - 查找代码修改者、关联PR、获取改动背景。 触发词: 谁改的, 谁写的, blame, 追溯, 找作者, 这行代码, 提交记录, 谁提交的, PR, 代码历史 |
帮助定位代码修改者，获取改动背景，便于协作解决问题
🔍 **正在执行: 代码追溯** (`#git-blame`)
✅ 已加载 Skill 指引
⭕ 当前步骤: 识别追溯目标
✅ **执行完成**: 代码追溯
参考来源:
- Skill: `#git-blame`
- 数据来源: [本地 Git / MCP DevOps]
产出物: 代码追溯报告
步骤1: 识别追溯目标
↓
步骤2: 执行代码追溯
↓
步骤3: 获取关联 PR
↓
步骤4: 输出追溯报告
目标: 确定要追溯的代码位置
识别信息:
判断代码位置:
| 情况 | 处理方式 |
|---|---|
| 工作区内的文件 | 使用本地 git blame |
| 远程仓库文件 | 使用 mcp_azuredevops_list_commits |
| 用户提供代码片段 | 先搜索定位，再追溯 |
# 查看某行的提交信息
git blame -L <起始行>,<结束行> <文件路径>
# 查看提交详情
git show <commit-hash> --stat
# 查看提交的完整信息
git log -1 --format="%H%n%an%n%ae%n%s%n%b" <commit-hash>
调用: mcp_azuredevops_list_commits
参数:
- repositoryId: 仓库名称
- branchName: 分支名
- top: 返回数量
从返回结果提取：
author.name - 作者姓名author.email - 作者邮箱comment - 提交信息（含 PR 号）files[].path - 修改的文件files[].patch - 具体改动从 commit message 提取 PR 号:
常见格式：
已合并 PR 236436: ...Merged PR 236436: ...(#236436)获取 PR 详情:
调用: mcp_azuredevops_get_pull_request_comments
参数:
- repositoryId: 仓库名
- pullRequestId: PR 号
使用以下模板输出结果：
## 🔍 代码追溯报告
### 📍 追溯目标
- **文件**: `path/to/file.cs`
- **行号**: L100-L110
- **代码片段**: [如有]
### 👤 修改者信息
| 字段 | 值 |
|------|-----|
| 作者 | [姓名] |
| 邮箱 | [email] |
| 时间 | [日期] |
| Commit | [hash 前8位] |
### 🔗 关联 PR
- **PR #[号码]**: [标题]
- **链接**: [DevOps 链接]
### 📝 改动说明
[commit message 或 PR 描述]
### 💬 PR 讨论摘要
[如果有评论]
### 📌 后续建议
- 联系 **[作者]** 了解改动背景
- 查看 PR 中的测试用例
- [其他建议]
| 场景 | 命令 |
|---|---|
| 查看某行作者 | git blame -L 100,110 file.cs |
| 查看文件历史 | git log --oneline -10 -- file.cs |
| 查看提交详情 | git show <hash> |
| 查找包含关键词的提交 | git log --grep="关键词" --oneline |
| 查看某人的提交 | git log --author="姓名" --oneline |
| Skill | 用途 |
|---|---|
#expert-index | 需要找对应模块专家时 |