GitHub Content Publisher is live: roadmap and feedback

[Quehd]

GitHub Content Publisher is live: roadmap and feedback

github-content-publisher is now public.

This repository contains a Codex skill for turning real repository facts into stronger GitHub-facing content: repo launches, PR descriptions, release notes, README positioning, and bilingual announcement copy.

如果你也遇到过这些问题，这个 skill 就是为这类场景做的：

• 代码已经 push 了，但 repo 首页还是很空
• PR 正文能用，但不够像一个成熟项目的维护者写出来的
• release notes 只是原始变更列表，没有结构和重点
• 想发中文、英文或双语内容，但不想要那种很重的机翻味

What it does today

• Draft repository launch copy
• Generate repo description, topics, and positioning text
• Turn a diff into a cleaner PR title and body
• Write structured release notes
• Produce GitHub-native discussion or issue announcement copy
• Support zh-CN, en, and bilingual output

Why it may be useful

The goal is not to generate louder copy. The goal is to generate more publishable copy.

That means:

• starting from real repo facts
• choosing the right structure for the GitHub surface
• writing for an actual reader
• keeping legal, attribution, and release-safety constraints visible when they matter

Included in v1.0.0

• SKILL.md
• references/content-types.md
• references/quality-bar.md
• scripts/collect-github-facts.ps1
• agents/openai.yaml
• bilingual README

Short roadmap

What I most likely want to improve next:

• direct publishing workflows for repo metadata, releases, and discussions
• better PR and release-note variants for different repository sizes
• stronger bilingual output patterns for Chinese-first and English-first launches
• more examples based on real repository packaging workflows

Feedback I want

If you try this skill, the most useful feedback would be:

• which GitHub surface you wanted to publish to
• whether the draft felt too generic, too long, or too cautious
• which part was strong: title, opener, bullets, CTA, or release structure
• what was still missing from the workflow

中文也欢迎直接提，尤其是这些方向：

• 你最想让它支持哪种 GitHub 发布场景
• 你觉得文案更像“会写的人写的”，还是更像“AI 自动拼出来的”
• 你更需要中文、英文，还是双语一起发
• 你希望它最终只生成内容，还是能直接帮你发布

Try it

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

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

Links

• Repo: https://github.com/Quehd/github-content-publisher
• Release: https://github.com/Quehd/github-content-publisher/releases/tag/v1.0.0

If you use Codex for repo packaging, PR writing, or release writing, I would especially like feedback on real publishing workflows rather than toy examples.

[Quehd]

To make feedback easier, here are 3 concrete questions:

1. Which GitHub surface do you most want this skill to handle better first?
   Repo launch / README / PR / release notes / discussion post / issue post

2. If you care about bilingual output, which mode matters more in practice?
   Chinese-first / English-first / both equally

3. Would you rather use this as:

   • content generation only
   • content + direct publishing actions
   • both, depending on the repo

Short replies are useful. Even one-line answers help shape the next version.