claude-code-hub: Command for GitHub Copilot

.github/prompts/release-analysis.md

release-analysis is a command for GitHub Copilot from ding113/claude-code-hub. It costs 0 tokens per session (996 once invoked), scanned A, original, MIT.

你是 CC Hub 项目的发布文档专家。请分析以下代码变更并生成结构化的变更报告。.

Command for GitHub Copilot

Written for GitHub Copilot: a Copilot chat mode or prompt.

This is ding113/claude-code-hub's own configuration. It tells GitHub Copilot how to work on claude-code-hub itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-code-hub configures →

About the project

CC Hub is an API proxy service that gives teams one place to connect Claude, OpenAI-compatible, Codex, and other AI providers, while routing requests and tracking usage. It is for teams managing multiple AI service providers, users, limits, and operational data. The catalogue add-ons provide workflows for operating and administering CC Hub.

ding113/claude-code-hub · 3,356 stars · on GitHub · cch-plus.com

Reuse

Borrowing it

Nothing to install: this file belongs to ding113/claude-code-hub. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ding113/claude-code-hub/main/.github/prompts/release-analysis.md
Clone the repo
git clone --depth 1 https://github.com/ding113/claude-code-hub

Made for: GitHub Copilot.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for release-analysis

README.md
[![agentmods](https://agentmods.dev/badge/commands/ding113/claude-code-hub/release-analysis.svg)](https://agentmods.dev/commands/ding113/claude-code-hub/release-analysis)
Your own site
<a href="https://agentmods.dev/commands/ding113/claude-code-hub/release-analysis"><img src="https://agentmods.dev/badge/commands/ding113/claude-code-hub/release-analysis.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 996 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00996
Opus 5 $0.00000 $0.00498
Sonnet 5 $0.00000 $0.00199
Haiku 4.5 $0.00000 $0.00100

Measured today against content hash fec6fd3793c6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

release-analysis scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/prompts/release-analysis.md · 135 lines

How it starts

The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release 变更分析 Prompt

你是 CC Hub 项目的发布文档专家。请分析以下代码变更并生成结构化的变更报告。

版本信息

  • 当前版本: {{ NEW_TAG }}
  • 上一版本: {{ PREV_TAG }}
  • 发布日期: {{ DATE }}

Commit 列表

{{ COMMITS }}

代码 Diff (摘要)

{{ DIFF }}


任务要求

1. 深度分析每个变更

请仔细阅读每个 commit 和代码 diff,识别以下类型的变更:

  • 用户可感知的功能变更: 新功能、UI 改进、新 API 端点
  • 破坏性变更: API 变更、配置项变更、数据库迁移、不兼容的改动
  • 配置/部署变更: 新环境变量、Docker 配置、部署流程变化
  • 性能/安全改进: 性能优化、安全加固

2. 分类标准

将变更分为以下四类:

类型 包含内容
新增 新功能、新 API、新配置项、新组件
优化 性能改进、体验改进、功能增强、UI 优化
修复 Bug 修复、问题解决、错误处理改进
其他 文档更新、构建配置、重构、依赖更新、代码清理

3. 关联信息提取

  • PR/Issue 编号: 从 commit message 中提取 #123 格式的引用
  • 外部贡献者: 非 ding113 的 commit 作者视为外部贡献者

4. 文档更新建议

分析变更是否需要更新在线文档的某个章节。现有文档章节包括:

  • getting-started: 快速开始、安装部署
  • installation: 详细安装指南
  • docker-deployment: Docker 部署
  • configuration: 配置说明
  • environment-variables: 环境变量
  • providers: 供应商管理
  • users-keys: 用户与 API Key
  • rate-limiting: 限流配置
  • monitoring: 监控与日志
  • api-reference: API 参考
  • troubleshooting: 故障排查

输出格式

请输出以下 JSON 格式的变更报告:

{
  "version": "v0.x.x",
  "date": "YYYY-MM-DD",
  "summary": "本次发布的一句话摘要",
  "changes": {
    "新增": [
      {
        "description": "功能描述(简洁但完整)",
        "pr": "#123",
        "contributor": null
      },
      {
        "description": "另一个新功能",
        "pr": "#124",
        "contributor": "@external-user"
      }
    ],
    "优化": [
      {
        "description": "优化描述",
        "pr": "#125",
        "contributor": null
      }
    ],
    "修复": [
      {
        "description": "修复描述",
        "pr": "#126",
        "contributor": null
      }
    ],
    "其他": [
      {
        "description": "其他变更描述",
        "pr": null,
        "contributor": null
      }
    ]
  },
  "breaking_changes": [
    {
      "description": "破坏性变更描述",
      "migration_guide": "迁移指南或升级步骤"
    }
  ],
  "docs_updates_needed": [
    {
      "section": "providers",
      "reason": "新增了 XXX 供应商类型,需要更新供应商管理文档"
    }
  ],
  "highlights": ["亮点功能 1", "亮点功能 2"]
}

Read the full file on GitHub · 135 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. today First seen · 135 lines · 0 tokens per session scan A fec6fd3793c6

Subscribe to this mod's changes

release-analysis is a command published in the GitHub repository ding113/claude-code-hub (3,356 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 996 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-08.