How do I install the Agent Relay skill?

Run npx skillmds@latest add tr1v3r/agent-relay in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Agent Relay safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Agent Relay?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Agent Relay free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Agent Relay?

tr1v3r (@tr1v3r) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Agent Relay by tr1v3r — Agent Skill

Name: Agent Relay
Author: tr1v3r

Agent Relay

Summarize what a git branch changed versus its baseline as a concise five-section Markdown report: one-liner, scale, core flow, new modules, development phases. Use when the user asks to “总结修改内容”, “总结分支”, “看看这个分支改了什么”, “总结一下改动”, “summarize changes”, “branch summary”, or wants a high-level digest of a diff or commit range.

tr1v3r 0c23fd4 5 files · 15.1 KB Updated Sep 17, 2026

File contents

Branch Summary

Summarize what a branch changed compared to a baseline. The report is for a human who wants to understand the work without reading the diff: what was delivered, how big it is, how it works, what was added, and how it evolved.

1. Collect facts

Establish the baseline first — default master, fall back to main, then to whatever the user names — then gather numbers from git:

git merge-base <base> HEAD
git log --oneline --date=short --pretty=format:'%ad %s' <base>..HEAD
git diff --stat <base>...HEAD | tail -1

Drill into the biggest changed directories to name modules:

git diff --stat <base>...HEAD -- <dir>

Adapt the same commands to other inputs: two arbitrary refs, a commit range, or uncommitted work via git status and git diff. Every number in the report comes from command output — never estimate.

2. Report format

Render exactly these five sections, in the user's language:

# <branch> vs <base> 总结

**一句话**：<分支交付了什么、为了解决什么问题，一两句说完>

**规模**：<N> 个 commit，<M> 个文件，+<X>/-<Y> 行<（生成代码/大块配套占大头时注明）>。

## 核心业务流程

<入口或起点> → <步骤>（<关键文件>）
  → <步骤> → <步骤>
  → <最终动作和下游影响>

## 主要新增模块

| 模块 | 内容 |
| --- | --- |
| <目录/包名（约 N 行）> | <职责一句话 + 关键能力> |

## 开发演进

1. <阶段名>（<日期或日期范围>）：<该阶段 commit 主题的归纳>
2. …

3. Deliver

Show the report in the conversation, then persist it in the summarized project so other agents can find it:

.agents/handoff/<branch>-vs-<base>.md

Sanitize / in ref names to -. If .agents/handoff/ is not covered by the project's .gitignore, say so — the file should not be committed accidentally.

4. Writing constraints

一句话 answers “这个分支交付了什么”, not “我做了哪些动作”.
规模 numbers must come from git output; note when generated code (kitex_gen, protobuf, vendored files, lock files) dominates the line count.
核心业务流程 is the single main chain: arrows between steps, key file in parentheses, indented continuation lines. Do not enumerate branches or edge cases.
主要新增模块 aggregates by directory or package with its rough size, not file by file; include modified-but-existing modules only when the change is substantial.
开发演进 groups the commit timeline into 3–6 named phases with dates, one line each summarizing what its commits did.
Report facts only — no review, no advice, no process narrative.

---name: agent-relaydescription: Summarize what a git branch changed versus its baseline as a concise five-section Markdown report: one-liner, scale, core flow, new modules, development phases. Use when the user asks to “总结修改内容”, “总结分支”, “看看这个分支改了什么”, “总结一下改动”, “summarize changes”, “branch summary”, or wants a high-level digest of a diff or commit range.---# Branch SummarySummarize what a branch changed compared to a baseline. The report is for ahuman who wants to understand the work without reading the diff: what wasdelivered, how big it is, how it works, what was added, and how it evolved.## 1. Collect factsEstablish the baseline first — default `master`, fall back to `main`, then towhatever the user names — then gather numbers from git:```bashgit merge-base <base> HEADgit log --oneline --date=short --pretty=format:'%ad %s' <base>..HEADgit diff --stat <base>...HEAD | tail -1```Drill into the biggest changed directories to name modules:```bashgit diff --stat <base>...HEAD -- <dir>```Adapt the same commands to other inputs: two arbitrary refs, a commit range,or uncommitted work via `git status` and `git diff`. Every number in thereport comes from command output — never estimate.## 2. Report formatRender exactly these five sections, in the user's language:```markdown# <branch> vs <base> 总结**一句话**：<分支交付了什么、为了解决什么问题，一两句说完>**规模**：<N> 个 commit，<M> 个文件，+<X>/-<Y> 行<（生成代码/大块配套占大头时注明）>。## 核心业务流程<入口或起点> → <步骤>（<关键文件>） → <步骤> → <步骤> → <最终动作和下游影响>## 主要新增模块| 模块 | 内容 || --- | --- || <目录/包名（约 N 行）> | <职责一句话 + 关键能力> |## 开发演进1. <阶段名>（<日期或日期范围>）：<该阶段 commit 主题的归纳>2. …```## 3. DeliverShow the report in the conversation, then persist it in the summarizedproject so other agents can find it:```text.agents/handoff/<branch>-vs-<base>.md```Sanitize `/` in ref names to `-`. If `.agents/handoff/` is not covered by theproject's `.gitignore`, say so — the file should not be committed accidentally.## 4. Writing constraints- **一句话** answers “这个分支交付了什么”, not “我做了哪些动作”.- **规模** numbers must come from git output; note when generated code (kitex_gen, protobuf, vendored files, lock files) dominates the line count.- **核心业务流程** is the single main chain: arrows between steps, key file in parentheses, indented continuation lines. Do not enumerate branches or edge cases.- **主要新增模块** aggregates by directory or package with its rough size, not file by file; include modified-but-existing modules only when the change is substantial.- **开发演进** groups the commit timeline into 3–6 named phases with dates, one line each summarizing what its commits did.- Report facts only — no review, no advice, no process narrative.

Frequently asked questions