菜单
Craft a conventional commit message from staged changes, get user approval, then commit and push. Use when: writing a commit message, committing staged changes, pushing a commit.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Scaffold a web repo with pnpm, Astro, and astro-bulma — plus Drizzle when the site needs a database — including package.json scripts for build/lint/test/fmt (and db:migrate when db-backed). Use when: setting up a new Astro project, scaffolding a web repo, initializing the standard web stack. Building block for create-website.
Add a GitHub Actions CI workflow running build, lint, test, and fmt checks with pnpm. Use when: adding CI, setting up GitHub Actions checks, adding a build/lint/test workflow. Building block for create-website.
Create a new website end-to-end: Astro repo with pnpm/astro-bulma; GitHub Pages for static sites, or Turso + Fly.io when the site needs a database; GitHub Actions for CI and deploy. Use when: creating a new website, spinning up a new web project, new site, scaffolding a static or full-stack Astro project.
Create a new app on Fly.io for the current project without deploying it, generating fly.toml and a Dockerfile. Use when: creating a Fly.io app, setting up Fly hosting, fly launch. Building block for create-website.
Add a GitHub Actions workflow that builds a static site and deploys it to GitHub Pages, with an optional custom domain. Use when: deploying a static site, GitHub Pages hosting, static site with a custom domain. Building block for create-website.
Add a GitHub Actions workflow that deploys to Fly.io on merge to main, with db migrations run as a Fly release_command. Use when: adding a deploy workflow, deploying on merge, setting up continuous deployment to Fly.io. Building block for create-website.
| name | conventional-commit |
| description | Craft a conventional commit message from staged changes, get user approval, then commit and push. Use when: writing a commit message, committing staged changes, pushing a commit. |
| argument-hint | Optional: Jira ticket (e.g. DT-1234) for the Refs footer |
Analyze git diff --staged and produce a message following Conventional Commits:
<type>(<optional scope>): <short description>
<optional body: bullet points of notable changes>
<optional footer: "Refs: TICKET-###" if a ticket is known>
Types: feat, fix, refactor, chore, docs, test, style, perf, ci, build, revert
Refs: footer if a Jira ticket is knowngit commit until the user explicitly approves. This is a hard stop.git commit -m "<approved message>"
git push origin HEAD
If the push is rejected (non-fast-forward), report the error — do not force-push.