Qiaomu Github Publisher

Qiaomu GitHub Publisher

Turn a working project into a GitHub repository people can understand, try, star, install, and trust.

Copyright (c) 向阳乔木

• X: https://x.com/vista8
• GitHub: https://github.com/joeseesun/
• Profile source: ~/.agents/skills/qiaomu-profile

Core Workflow

1. Inspect the repo before writing:

• README.md, package.json / project metadata, screenshots, examples, docs, license, deploy scripts, test scripts.
• GitHub remote state via gh repo view --json name,description,homepageUrl,repositoryTopics,url.

2. Decide the public positioning:

• One-line hook in Chinese and English.
• Target users and why they should try it now.
• Clear boundary between product value, technical architecture, and private/local setup.

3. Rewrite or patch README as a product page:

• Chinese first, English second unless the repo is explicitly English-first.
• Put hook, CTAs, badges, screenshot, feature list, quick start, examples, verification, limitations, and troubleshooting near the top.
• Use real screenshots or output samples when available; do not invent screenshots.

4. Set GitHub About:

• Use bilingual description when the user asks or the repo targets both Chinese and English audiences.
• Add homepage URL when there is a live demo.
• Add focused topics; avoid topic spam.

5. Verify what the README promises:

• Run project-provided lint/build/test commands when relevant.
• For skills, verify npx skills add discoverability/installability.
• For websites, verify live URL/API/health after deployment when applicable.

6. Publish through a clean GitHub flow:

• Use a feature branch and PR.
• Never push directly to main.
• If verification passes and the user has not explicitly asked to hold, merge the PR into main.
• In the final response, include the PR URL and merge commit.

README Standard

Public README must answer five questions fast:

• What pain does this solve?
• What do I get after installing/running it?
• Can I see proof in a screenshot, demo, or example output?
• How do I try it in less than five minutes?
• What are the limits, costs, or prerequisites?

Recommended structure:

# Project Name

> 中文价值主张
> English value proposition

[Live Demo] [Install] [License] [Stars]

![Screenshot](docs/assets/product-screenshot.png)

**中文** | [English](#english)

## 为什么值得用
## 核心能力
## 样例输出
## 快速开始
## 部署 / API / Skill
## 限制与边界
## Troubleshooting
## 关于向阳乔木

---

<a name="english"></a>
# English section

GitHub About Standard

Use a compact bilingual form when appropriate:

中文短描述 | English short description.

Keep it concrete. Good examples:

• 用 DeepSeek flash 将 App Store 评价转成 SEO/GEO 友好的产品洞察页 | Turn App Store reviews into SEO/GEO-friendly product insights with DeepSeek flash.
• 把任意资料整理成 NotebookLM 可用知识包 | Turn messy sources into NotebookLM-ready knowledge packs.

Topics should be narrow and useful:

• domain: app-store, app-reviews, notebooklm, geo
• stack: nextjs, agent-skill, deepseek
• audience/workflow: product-management, ai-workflow

Avoid generic topics like tool, website, ai unless they add discoverability.

Qiaomu Profile Block

For Qiaomu-owned public repos, include profile/support links by default:

• qiaomu.ai
• blog.qiaomu.ai
• tuijian.qiaomu.ai
• X @vista8
• GitHub @joeseesun
• WeChat public account 向阳乔木推荐看

Use qiaomu-profile as the source of truth for bios and assets. Do not invent personal claims.

Release Checklist

Before claiming done:

• README has no TODO/placeholders.
• Screenshots and links exist.
• LICENSE exists or the repo intentionally omits one.
• gh repo view confirms About/homepage/topics.
• Relevant build/test/install checks passed.
• Git diff was scanned for secrets.
• PR was merged into main unless explicitly held.

Guardrails

• Do not publish secrets, .env.local, private paths, cache data, tokens, or runtime databases.
• Do not overpromise current features; mark roadmap items clearly.
• Do not bury setup failures in the README; make prerequisites explicit.
• Do not leave a verified PR dangling when the user expects publication.

qiaomu-github-publisher

把一个能跑的项目，包装成 GitHub 上别人愿意点开、试用、安装、star 的开源项目。

Turn a working project into a GitHub-ready public release with a sharper README, bilingual About, topics, verification, PR, and merge flow.

  

为什么需要它

很多项目已经能跑，但 GitHub 首屏仍然像内部备忘录：README 没有痛点、没有截图、没有清晰安装路径，About 也没有抓住关键词。qiaomu-github-publisher 专门处理最后这一步：把项目变成一个陌生人也能理解、信任并愿意尝试的公开仓库。

它会帮你做什么

• 重写或修补 README，让它像产品页而不是开发日志
• 写中英双语 GitHub About 描述
• 设置 homepage 和 focused topics
• 检查截图、徽章、安装步骤、API 示例和 Troubleshooting
• 跑项目对应的 lint/build/test/install 验证
• 扫描 diff 中的敏感信息
• 创建 PR，并在验证通过后合并到 main
• 对 Qiaomu-owned 项目默认加入向阳乔木 profile、链接和支持入口

Install

npx skills add joeseesun/qiaomu-github-publisher

Usage

安装后你可以这样说：

• 把这个项目整理成适合 GitHub 发布的 README，并设置 About
• 这个 repo 要开源，帮我包装一下再发到 GitHub
• 重写 README，中英双语，验证后自动合并 main
• 优化 GitHub topics、homepage 和项目描述

Workflow

1. Inspect repo state and existing metadata. 2. Rewrite README with Chinese-first bilingual structure when appropriate. 3. Update GitHub About, homepage, and topics via gh. 4. Run project-specific verification. 5. Create a PR and merge verified changes into main unless explicitly held.

English

qiaomu-github-publisher is an Agent Skill for GitHub release polish. It helps turn working projects into public repositories with a clear README, bilingual About text, useful topics, real verification, and a complete PR-to-main publishing flow.

About Qiaomu

向阳乔木 / Joe is a practical AI product and workflow builder. He turns frontier AI changes into usable workflows, product judgment, AI coding practice, and GEO / AI-marketing methods.

• Website: https://qiaomu.ai
• Blog: https://blog.qiaomu.ai
• Qiaomu tools and recommendations: https://tuijian.qiaomu.ai/
• X: https://x.com/vista8
• GitHub: https://github.com/joeseesun/

<!-- qiaomu-profile:start -->

关于向阳乔木

向阳乔木（乔向阳 / Joe）是一位实践型 AI 产品与内容创作者，长期把前沿 AI 变化转译成可复用的工作流、产品判断、AI 编程实践、AI 搜索实践和 GEO/AI 营销方法。

• 个人网站: https://qiaomu.ai
• 博客: https://blog.qiaomu.ai
• X: https://x.com/vista8
• GitHub: https://github.com/joeseesun/
• 微信公众号: 向阳乔木推荐看

支持与关注

<!-- qiaomu-profile:end -->

License

MIT