원클릭으로 Manus에서 모든 스킬 실행

hexi-blog-update

스타1

포크0

업데이트2026년 6월 2일 06:38

Use when the user wants to publish, post, or update a blog article to their hexi-site blog (Hexi1997/hexi-site) — triggers include "发布博客", "更新博客", "post to my blog", "hexi-blog-update". Handles slug, frontmatter, file placement, and pushing to main via local git/gh.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

Hexi1997

Hexi1997/skills

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

hexi-blog-update

Publish a blog post to the hexi-site repo (Hexi1997/hexi-site) blog module, then commit and push directly to main via local git.

Repo facts (do not re-discover)

Local clone: /Users/hexi/OpenSource/hexi-site (remote git@github.com:Hexi1997/hexi-site.git, SSH).
Posts live in: apps/site/posts/<slug>/index.md — one folder per post, folder name = slug = URL.
Online URL: https://hexi-site... → path /blog/<slug>.
Author is hardcoded site-wide as WORLD3. Do NOT put author in frontmatter.
No build verification before push (user opted out). Just structural checks.
Push directly to main without asking for confirmation — the user explicitly authorized this for this skill, overriding the general "ask before git write ops" rule. Do not prompt before commit/push here.

Frontmatter template

---
title: '标题'
date: 'YYYY-MM-DD'
tags:
  - 'Tag1'
  - 'Tag2'
---

title (required), date (required, today if unspecified), tags (list, single-quoted).
Optional: pinned: true (置顶), cover: '...' (else first image / default), source: '...' (external link).
Existing tag vocabulary (reuse, don't invent gratuitously): AI, Design, Email, Frontend, Next.js, Web3, Zustand.

Slug rules

English title → kebab-case of the title (lowercase, spaces→-, strip punctuation).
Chinese title → pinyin kebab-case (no tones), e.g. 邮件开发二三事 → you-jian-kai-fa-er-san-shi. Embedded English/numbers follow the same kebab-case treatment (lowercase, strip punctuation): Next.js 16.2 … → next-js-16-2-…, Bun → bun.
Folder name must be unique — if apps/site/posts/<slug>/ already exists, STOP and ask the user (overwrite vs new slug).

Workflow

Get content. Use markdown the user pasted. If none in the message, look in the current conversation context. If still none, ask the user for the article.
Sync repo: cd /Users/hexi/OpenSource/hexi-site && git checkout main && git pull.
Infer metadata, then confirm in ONE message before writing:
- title (first # heading or user-given), date (today: get with date +%Y-%m-%d), tags (recommend from content + existing vocab), slug (per rules above).
- Show all four; let the user edit. Proceed once approved. (tags is a recommendation — if no existing tag fits, suggest the closest and let the user override.)
Write the post:
- mkdir -p apps/site/posts/<slug> and write index.md = frontmatter + body.
- If the title came from the body's first # heading, REMOVE that heading line from the body — the frontmatter title is rendered separately, so leaving it duplicates the title on the page.
- If the body has local images: copy them into apps/site/posts/<slug>/assets/ and rewrite refs to ![image](assets/<file>.png). No images → skip.
- If the body already includes frontmatter, use it as-is (still validate required fields).
Verify structure (no build): index.md exists, frontmatter parses, required fields present, image refs resolve.

Commit & push to main (no confirmation prompt):

git add apps/site/posts/<slug>
git commit -m "feat(blog): add <slug>"   # English, conventional commit
git push origin main

Report: slug, file path, commit hash, online path /blog/<slug>.

Quick reference

Item	Value
Repo	`/Users/hexi/OpenSource/hexi-site`
Post path	`apps/site/posts/<slug>/index.md`
Images	`apps/site/posts/<slug>/assets/`, ref `assets/x.png`
Branch	`main` (commit + push directly, no prompt)
Commit msg	`feat(blog): add <slug>` (English)
URL	`/blog/<slug>`

Common mistakes

❌ Adding author to frontmatter — it's hardcoded WORLD3.
❌ Asking permission before push — this skill is pre-authorized to push to main.
❌ Running a build to verify — user opted out; only structural checks.
❌ Overwriting an existing slug folder silently — STOP and ask first.
❌ Chinese characters in slug — always romanize to pinyin kebab-case.
❌ Forgetting git pull first — always sync main before writing.

이 저장소의 다른 Skills

같은 저장소

git-commit-and-push

Hexi1997/skills

Use when the user wants to commit and push in one go (用户提到 "提交并推送"、"提交后推上去"、"commit 并 push"、"commit and push"、"/git-commit-and-push"). Covers what that single request does and does NOT authorize, and when to stop between the two halves.

2026-07-271

git-push

Hexi1997/skills

Use when pushing commits to the remote (用户提到 "push"、"推一下"、"推到远程"、"git push"、"强推"、"force push"). Always resolves the push target to the CURRENT branch instead of master/main, sets upstream on first push, brakes on protected branches, and uses --force-with-lease for force pushes.

2026-07-221

pr-generate

Hexi1997/skills

Use when the user asks to summarize recent commits into a PR description or write a pull request title and body from git history (用户提到 "生成 PR"、"总结最近 commit"、"输出 PR"、"pr-generate"). Also when the PR may touch env vars or database/SQL that need highlighting. Supports two diff ranges - recent N commits, or the diff against a remote base branch (如 "跟 master 的 diff"、"对比 origin/develop"、"base=master").

2026-07-011

new-worktree

Hexi1997/skills

Use when starting work on a new branch in a multi-worktree repo and need to create the git worktree (用户提到 "新开 worktree"、"建 worktree"、"开个 worktree 做 X"、"切个分支并行开发"、"new worktree"). Enforces fetch-first, branch off latest origin/master, and sibling-of-repo-root dir named after the branch.

2026-06-231

update-user-memory

Hexi1997/skills

Use when the user wants to save, update, persist, or "remember" a global / user / AI / AGENT instruction or memory so it applies across all coding clients (Claude, Codex, Cursor). Triggers include "更新用户记忆", "保存全局指令", "记住…到全局 AGENT 指令", "save to global agent memory", "remember this globally". Assumes agent-root-cli has been set up once (init + link).

2026-06-021

interview-qa-generator

Hexi1997/skills

当用户提出“生成面试题”、“生成面试问答”、“根据我的简历生成面试题”、“帮我准备面试”、“模拟面试”，或希望基于其简历和项目描述生成面试问题与答案时，应使用此 skill。

2026-05-131

name	hexi-blog-update
description	Use when the user wants to publish, post, or update a blog article to their hexi-site blog (Hexi1997/hexi-site) — triggers include "发布博客", "更新博客", "post to my blog", "hexi-blog-update". Handles slug, frontmatter, file placement, and pushing to main via local git/gh.

hexi-blog-update

Publish a blog post to the hexi-site repo (Hexi1997/hexi-site) blog module, then commit and push directly to main via local git.

Repo facts (do not re-discover)

Local clone: /Users/hexi/OpenSource/hexi-site (remote git@github.com:Hexi1997/hexi-site.git, SSH).
Posts live in: apps/site/posts/<slug>/index.md — one folder per post, folder name = slug = URL.
Online URL: https://hexi-site... → path /blog/<slug>.
Author is hardcoded site-wide as WORLD3. Do NOT put author in frontmatter.
No build verification before push (user opted out). Just structural checks.
Push directly to main without asking for confirmation — the user explicitly authorized this for this skill, overriding the general "ask before git write ops" rule. Do not prompt before commit/push here.

Frontmatter template

---
title: '标题'
date: 'YYYY-MM-DD'
tags:
  - 'Tag1'
  - 'Tag2'
---

title (required), date (required, today if unspecified), tags (list, single-quoted).
Optional: pinned: true (置顶), cover: '...' (else first image / default), source: '...' (external link).
Existing tag vocabulary (reuse, don't invent gratuitously): AI, Design, Email, Frontend, Next.js, Web3, Zustand.

Slug rules

English title → kebab-case of the title (lowercase, spaces→-, strip punctuation).
Chinese title → pinyin kebab-case (no tones), e.g. 邮件开发二三事 → you-jian-kai-fa-er-san-shi. Embedded English/numbers follow the same kebab-case treatment (lowercase, strip punctuation): Next.js 16.2 … → next-js-16-2-…, Bun → bun.
Folder name must be unique — if apps/site/posts/<slug>/ already exists, STOP and ask the user (overwrite vs new slug).

Workflow

Get content. Use markdown the user pasted. If none in the message, look in the current conversation context. If still none, ask the user for the article.
Sync repo: cd /Users/hexi/OpenSource/hexi-site && git checkout main && git pull.
Infer metadata, then confirm in ONE message before writing:
- title (first # heading or user-given), date (today: get with date +%Y-%m-%d), tags (recommend from content + existing vocab), slug (per rules above).
- Show all four; let the user edit. Proceed once approved. (tags is a recommendation — if no existing tag fits, suggest the closest and let the user override.)
Write the post:
- mkdir -p apps/site/posts/<slug> and write index.md = frontmatter + body.
- If the title came from the body's first # heading, REMOVE that heading line from the body — the frontmatter title is rendered separately, so leaving it duplicates the title on the page.
- If the body has local images: copy them into apps/site/posts/<slug>/assets/ and rewrite refs to ![image](assets/<file>.png). No images → skip.
- If the body already includes frontmatter, use it as-is (still validate required fields).
Verify structure (no build): index.md exists, frontmatter parses, required fields present, image refs resolve.

Commit & push to main (no confirmation prompt):

git add apps/site/posts/<slug>
git commit -m "feat(blog): add <slug>"   # English, conventional commit
git push origin main

Report: slug, file path, commit hash, online path /blog/<slug>.

Quick reference

Item	Value
Repo	`/Users/hexi/OpenSource/hexi-site`
Post path	`apps/site/posts/<slug>/index.md`
Images	`apps/site/posts/<slug>/assets/`, ref `assets/x.png`
Branch	`main` (commit + push directly, no prompt)
Commit msg	`feat(blog): add <slug>` (English)
URL	`/blog/<slug>`

Common mistakes

❌ Adding author to frontmatter — it's hardcoded WORLD3.
❌ Asking permission before push — this skill is pre-authorized to push to main.
❌ Running a build to verify — user opted out; only structural checks.
❌ Overwriting an existing slug folder silently — STOP and ask first.
❌ Chinese characters in slug — always romanize to pinyin kebab-case.
❌ Forgetting git pull first — always sync main before writing.