What is forge-doc-release?

A post-release documentation workflow for a software project. It checks project documents against the released code and updates the documentation, changelog, and selected version information.

Use it to update README, architecture, contribution, and project guidance files after a release, polish changelog entries, clean up completed TODOs, and optionally update the version.

It removes the mismatch between what the software does and what its documentation says. It also identifies completed tasks and outdated references.

forge-doc-release — Skill for Claude Code by yike-gunshi

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add yike-gunshi/forge-skills --skill forge-doc-release

Clone the repo

git clone --depth 1 https://github.com/yike-gunshi/forge-skills

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/yike-gunshi/forge-skills/forge-doc-release/github.svg)](https://agentmods.dev/skills/yike-gunshi/forge-skills/forge-doc-release)

Your own site

<a href="https://agentmods.dev/skills/yike-gunshi/forge-skills/forge-doc-release"><img src="https://agentmods.dev/badge/skills/yike-gunshi/forge-skills/forge-doc-release/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/yike-gunshi/forge-skills/forge-doc-release"><img src="https://agentmods.dev/badge/skills/yike-gunshi/forge-skills/forge-doc-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 108 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,939 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 original 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.

Model	Per session	Once invoked
Fable 5.1	$0.00108	$0.01939
Opus 5	$0.00054	$0.00970
Sonnet 5	$0.00022	$0.00388
Haiku 4.5	$0.00011	$0.00194

Measured 11d ago against content hash 484347267522, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

forge-doc-release 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 11d ago.

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.

skills/forge-doc-release/SKILL.md · 157 lines

How it starts

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

文档落地路径：遵循 forge-doc-policy 规范。完整白名单 + frontmatter schema 见 ~/.claude/skills/forge-doc-policy/doc-paths.md。 当前文档加载顺序：优先审查 CLAUDE.md、docs/README.md、docs/INDEX.md、根级当前真相源、相关模块附录和 .features；docs/archive/raw/ 只作历史证据，不纳入默认同步。详细规则见 ~/.claude/skills/_shared/current-doc-loading.md。

/forge-doc-release：发布后文档更新

前置脚本（每次先运行）

_BRANCH=$(git branch --show-current 2>/dev/null || echo "unknown")
echo "当前分支: $_BRANCH"

提问格式与批量策略见 ~/.claude/skills/_shared/interaction-protocol.md。

第0步：检测基础分支

确定此 PR 的目标分支。后续所有步骤以此为"基础分支"。

检查是否已有 PR： gh pr view --json baseRefName -q .baseRefName 如果成功，使用打印的分支名。
如果没有 PR（命令失败），检测仓库默认分支： gh repo view --json defaultBranchRef -q .defaultBranchRef.name
如果都失败，回退到 main。

角色定义

你在运行 /forge-doc-release 工作流。这在 /forge-ship（代码已提交，PR 已存在或即将创建）之后、PR 合并之前运行。你的任务：确保项目中的每个文档文件都准确、最新、用友好且面向用户的语气书写。

你主要是自动化的。明显的事实性更新直接做。只在风险或主观决策时停下来问。

只在以下情况停下来问：

风险/可疑的文档变更（叙事、理念、安全、删除、大规模重写）
VERSION 更新决策（如果尚未更新）
要添加的新 TODOS 项
叙事性的跨文档矛盾

绝不因以下原因停下来：

从 diff 明确可得的事实性更正
向表格/列表添加条目
更新路径、数量、版本号
修复过期的交叉引用
CHANGELOG 语气润色（小幅措辞调整）
标记 TODOS 已完成
跨文档事实性不一致（如版本号不匹配）

绝不做：

覆盖、替换或重新生成 CHANGELOG 条目——只润色措辞，保留所有内容
不经询问就更新 VERSION——始终用 AskUserQuestion 确认版本变更
对 CHANGELOG.md 使用 Write 工具——始终用 Edit 精确匹配 old_string

执行手册（按需加载，执行时必读）

本文件只保留铁律、流程总览和出口。进入执行阶段前，必须先读对应手册：

场景	必读文件	内容
第1步~第9步全部执行细节	references/release-details.md	diff 收集命令、逐文件审计启发式、CHANGELOG 润色规则、TODOS/VERSION 决策树、提交与 PR body 更新流程、文档健康摘要模板

规矩：不允许凭记忆执行细则——骨架没写的操作细节，一律以手册为准；手册与骨架冲突时，以骨架的铁律为准。

流程总览（9 步）

第1步：预检与 Diff 分析

确认不在基础分支上，收集 git diff <base>...HEAD 的 stat/log/文件清单，用 find 发现待同步文档，将变更分为新功能/行为变更/移除/基础设施四类并输出摘要。命令与分类细则见手册"第1步"。

第2步：逐文件文档审计

读取每个文档文件与 diff 交叉对照，按文件类型套用通用审计启发式（README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md/其他各有清单），把所需更新分成"自动更新"与"询问用户"两类。各文件的检查清单与分类标准见手册"第2步"。

第3步：应用自动更新

Read the full file on GitHub · 157 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

references/release-details.md 11 KB

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.

11d ago First seen · 157 lines · 108 tokens per session scan A 484347267522

Subscribe to this mod's changes

forge-doc-release is a skill published in the GitHub repository yike-gunshi/forge-skills (13 stars, last pushed 1mo ago), licensed MIT. It adds 108 tokens to every session and 1,939 once invoked, about $0.0005 per session on Opus 5. 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-08-30.

Claude Code Git and workflow Releases Writing and docs agent-skills ai-development forge skill-md skillsmp

swarm-migrate

Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…

yonatangross/orchestkit · 103 tokens

release-management

Automates GitHub releases with semantic versioning, changelog generation from merged PRs, and gh CLI integration. Supports draft, prerelease, and standard release workflows with task-tracked multi-phase execution. Use when creating releases, tagging versions, or publishing changelogs.

yonatangross/orchestkit · 58 tokens

release-sync

Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.

yonatangross/orchestkit · 62 tokens

forge-doc-release