GitHub Content Publisher

Create high-quality GitHub-facing content from real repository facts. This Codex skill turns code, git history, and repository metadata into polished repo launches, PR descriptions, release notes, README positioning, and announcement posts in Chinese, English, or bilingual form.

基于真实仓库事实生成高质量 GitHub 发布内容。这个 Codex skill 可以把代码、git 历史和仓库元数据整理成更成熟的仓库发布文案、PR 描述、release notes、README 定位文案，以及中英双语公告内容。

Why this skill exists

Most GitHub publishing flows stop at git push. The public-facing layer is usually weaker:

• repo descriptions are vague
• PR bodies are mechanically written
• release notes read like raw changelogs
• launch posts oversell the repo or ignore important constraints

This skill is designed to close that gap. It combines:

• fact-first repo analysis
• structured GitHub-native writing
• stronger quality checks for clarity, positioning, and publish safety
• native support for zh-CN, en, and bilingual output

为什么做这个 skill

很多 GitHub 发布流程只管把代码推上去，不管“发布内容本身”的质量：

• repo description 很空
• PR 正文像模板堆出来的
• release notes 像原始变更日志
• 发布帖要么过度营销，要么忽略 license / attribution / 风险说明

这个 skill 的目标，就是把这层补上。它把这些能力揉在一起：

• 基于仓库事实先做采集
• 按 GitHub 原生发布场景写内容
• 用单独的质量门槛约束标题、首段、结构和合法性
• 原生支持中文、英文和中英双语

What it can produce

• Repository launch copy
• Repository name, description, homepage suggestions, and topics
• README openings and project positioning
• Pull request titles and bodies
• Release notes and changelog-style announcements
• GitHub Discussion launch posts
• Launch issues or pinned issue copy

可以生成什么

• 仓库首发文案
• repo 名称建议、description、homepage、topics
• README 首页定位和项目介绍
• PR 标题和正文
• release notes 和版本公告
• GitHub Discussion 发布帖
• 首发 issue / pinned issue 文案

What makes it different

• It starts from repository facts, not marketing fiction.
• It separates output by publish surface instead of forcing one template onto everything.
• It includes a quality bar for stronger GitHub writing, not just AI-generated filler.
• It handles bilingual publishing without awkward sentence-by-sentence translation.

它和普通“文案生成”有什么不同

• 它先看仓库事实，再写内容，不反过来编故事。
• 它按发布场景拆分输出，不用一个模板硬套所有场景。
• 它有独立的质量规则，不只是生成一段“看起来像文案”的文本。
• 它支持中英双语，但不是逐句生硬互译。

Skill structure

• SKILL.md: trigger rules, workflow, language strategy, publishing rules
• references/content-types.md: output templates by surface
• references/quality-bar.md: revision rubric for stronger GitHub copy
• scripts/collect-github-facts.ps1: quick repo fact collection for content drafting
• agents/openai.yaml: UI metadata for Codex skill discovery

目录结构

• SKILL.md：触发条件、主流程、语言策略、发布规则
• references/content-types.md：按发布场景拆分的内容模板
• references/quality-bar.md：质量门槛和修订清单
• scripts/collect-github-facts.ps1：快速采集仓库事实
• agents/openai.yaml：Codex skill UI 元数据

Installation

Copy the folder into your Codex skills directory.

Windows

Copy-Item -Recurse -Force .\github-content-publisher $env:USERPROFILE\.codex\skills\

macOS / Linux

cp -R ./github-content-publisher ~/.codex/skills/

If you keep a custom CODEX_HOME, install it under $CODEX_HOME/skills instead.

安装方式

把整个目录复制到你的 Codex skills 目录即可。

如果你使用自定义 CODEX_HOME，则安装到 $CODEX_HOME/skills。

Example prompts

English

Use $github-content-publisher to draft a high-quality GitHub launch post for this repository.

Use $github-content-publisher to generate a PR title and body from the current git diff.

Use $github-content-publisher to write bilingual release notes for this version.

中文

用 $github-content-publisher 根据当前仓库内容生成一版高质量 GitHub 发布文案。

用 $github-content-publisher 给当前 diff 生成一版高质量 PR 标题和正文。

用 $github-content-publisher 给这个版本写一版中英双语 release notes。

Recommended repository metadata

• Name: github-content-publisher
• Description: Codex skill for high-quality GitHub launches, PRs, release notes, and bilingual repository content.
• Topics:
  • codex-skill
  • github
  • release-notes
  • pull-request
  • readme
  • documentation
  • bilingual
  • prompt-engineering
  • developer-tools

License

MIT