Name: publish
Author: yaodong

Prompt file imported from yaodong/yaodong.dev (.claude/commands/publish.md). Copyright stays with the author.

Publish all newly added blog posts.

Instructions

Follow these steps in order. Stop and report if any step fails.

Step 1 — Find new posts

Run git status to find newly added or modified files in src/content/blog/. Only process posts that are untracked or have uncommitted changes. If there are no new posts, tell the user and stop.

Step 2 — Generate excerpts

For each new post, check if it already has an excerpt in its front matter. If not, generate one:

Read the post completely
Write a 30-50 word excerpt that:
- Matches the author's voice (direct, concise, understated)
- Hooks the reader without giving everything away
- Avoids em-dashes
- Stands alone as a compelling teaser
Add the excerpt field to the post's YAML front matter (quoted)
Show the generated excerpt and word count for confirmation

Step 3 — Generate OG images

For each new post, check if it already has an image in its front matter pointing to an existing file. If not, run:

bun run scripts/generate-og-image.ts <post-path>

Step 4 — Review staged files

Before committing, run git status and review ALL untracked and modified files. Look for:

Temporary files (e.g., files in /tmp, .DS_Store, *.swp, *.bak)
Files that likely shouldn't be committed (credentials, .env, large binaries, editor backups)
Files unrelated to the blog posts being published

If any suspicious files are found, ask the user whether to include, ignore, or delete them before proceeding. Do NOT silently commit unexpected files.

Step 5 — Commit and push

Stage only the relevant files: the new post(s), generated OG image(s), and any modified front matter
Create a one-line commit message in the repository's style (imperative, Title Case), e.g.:
- Add post on AI economic disruption with OG image and excerpt
- Publish three new journal entries
Push to the remote

Important

Always show the user what will be committed before committing
Never force-push
If multiple posts are new, handle them all in a single commit

Install publish and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

Publish all newly added blog posts. ## Instructions Follow these steps in order. Stop and report if any step fails. ### Step 1 — Find new posts Run `git status` to find newly added or modified files in `src/content/blog/`. Only process posts that are untracked or have uncommitted changes. If there are no new posts, tell the user and stop. ### Step 2 — Generate excerpts For each new post, check if it already has an `excerpt` in its front matter. If not, generate one: 1. Read the post completely 2. Write a 30-50 word excerpt that: - Matches the author's voice (direct, concise, understated) - Hooks the reader without giving everything away - Avoids em-dashes - Stands alone as a compelling teaser 3. Add the `excerpt` field to the post's YAML front matter (quoted) 4. Show the generated excerpt and word count for confirmation ### Step 3 — Generate OG images For each new post, check if it already has an `image` in its front matter pointing to an existing file. If not, run: ``` bun run scripts/generate-og-image.ts <post-path> ``` ### Step 4 — Review staged files Before committing, run `git status` and review ALL untracked and modified files. Look for: - Temporary files (e.g., files in `/tmp`, `.DS_Store`, `*.swp`, `*.bak`) - Files that likely shouldn't be committed (credentials, `.env`, large binaries, editor backups) - Files unrelated to the blog posts being published If any suspicious files are found, ask the user whether to include, ignore, or delete them before proceeding. Do NOT silently commit unexpected files. ### Step 5 — Commit and push 1. Stage only the relevant files: the new post(s), generated OG image(s), and any modified front matter 2. Create a one-line commit message in the repository's style (imperative, Title Case), e.g.: - `Add post on AI economic disruption with OG image and excerpt` - `Publish three new journal entries` 3. Push to the remote ## Important - Always show the user what will be committed before committing - Never force-push - If multiple posts are new, handle them all in a single commit

{ "prompt": "Publish all newly added blog posts.\n\n## Instructions\n\nFollow these steps in order. Stop and report if any step fails.\n\n### Step 1 — Find new posts\n\nRun `git status` to find newly added or modified files in `src/content/blog/`. Only process posts that are untracked or have uncommitted changes. If there are no new posts, tell the user and stop.\n\n### Step 2 — Generate excerpts\n\nFor each new post, check if it already has an `excerpt` in its front matter. If not, generate one:\n\n1. Read the post completely\n2. Write a 30-50 word excerpt that:\n - Matches the author's voice (direct, concise, understated)\n - Hooks the reader without giving everything away\n - Avoids em-dashes\n - Stands alone as a compelling teaser\n3. Add the `excerpt` field to the post's YAML front matter (quoted)\n4. Show the generated excerpt and word count for confirmation\n\n### Step 3 — Generate OG images\n\nFor each new post, check if it already has an `image` in its front matter pointing to an existing file. If not, run:\n\n```\nbun run scripts/generate-og-image.ts <post-path>\n```\n\n### Step 4 — Review staged files\n\nBefore committing, run `git status` and review ALL untracked and modified files. Look for:\n\n- Temporary files (e.g., files in `/tmp`, `.DS_Store`, `*.swp`, `*.bak`)\n- Files that likely shouldn't be committed (credentials, `.env`, large binaries, editor backups)\n- Files unrelated to the blog posts being published\n\nIf any suspicious files are found, ask the user whether to include, ignore, or delete them before proceeding. Do NOT silently commit unexpected files.\n\n### Step 5 — Commit and push\n\n1. Stage only the relevant files: the new post(s), generated OG image(s), and any modified front matter\n2. Create a one-line commit message in the repository's style (imperative, Title Case), e.g.:\n - `Add post on AI economic disruption with OG image and excerpt`\n - `Publish three new journal entries`\n3. Push to the remote\n\n## Important\n\n- Always show the user what will be committed before committing\n- Never force-push\n- If multiple posts are new, handle them all in a single commit", "variables": [], "notes": "Publish new blog posts (generate excerpts, OG images, review staged files, commit and push)", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/yaodong/yaodong.dev", "path": ".claude/commands/publish.md", "ref": "e7057cf18edce5706f953fcccfa9d80e72ef39dd", "url": "https://github.com/yaodong/yaodong.dev/blob/e7057cf18edce5706f953fcccfa9d80e72ef39dd/.claude/commands/publish.md", "key": "yaodong/yaodong.dev/.claude/commands/publish.md" } } }

publish

About

Instructions

Step 1 — Find new posts

Step 2 — Generate excerpts

Step 3 — Generate OG images

Step 4 — Review staged files

Step 5 — Commit and push

Important

Install publish and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews