菜单
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.
用 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.
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.
Add a GitHub Actions workflow that spins up a temporary Fly.io preview app per pull request, backed by a fork of the production Turso database, and destroys both on close. Use when: adding PR previews, review apps, per-PR deploy environments.
| name | add-ci-workflow |
| description | 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. |
Add .github/workflows/ci.yml that gates every PR on build, lint, test, and formatting.
Check package.json for build, lint, test, and fmt:check. If any are missing, add them (or adapt the workflow to what the repo actually uses) — don't ship a workflow that calls scripts that don't exist.
name: CI
on:
pull_request:
push:
branches: [main]
jobs:
build:
name: Build
runs-on: ubuntu-latest
timeout-minutes: 15
steps:
- uses: actions/checkout@v6
- uses: pnpm/setup@v1
with:
cache: true
- run: pnpm install --frozen-lockfile
- run: pnpm build
fmt:
name: Format
runs-on: ubuntu-latest
timeout-minutes: 15
steps:
- uses: actions/checkout@v6
- uses: pnpm/setup@v1
with:
cache: true
- run: pnpm install --frozen-lockfile
- run: pnpm fmt:check
lint:
name: Lint
runs-on: ubuntu-latest
timeout-minutes: 15
steps:
- uses: actions/checkout@v6
- uses: pnpm/setup@v1
with:
cache: true
- run: pnpm install --frozen-lockfile
- run: pnpm lint
test:
name: Test
runs-on: ubuntu-latest
timeout-minutes: 15
steps:
- uses: actions/checkout@v6
- uses: pnpm/setup@v1
with:
cache: true
- run: pnpm install --frozen-lockfile
- run: pnpm test
Each check runs as its own job so they execute in parallel and a failure in one doesn't mask the others.
If build needs env vars (e.g. Turso credentials for a build-time db connection), add them from repo secrets.
If the repo is on GitHub and the user wants it pushed now, push and watch the run (gh run watch) until green. Otherwise note that verification happens on first push.
CI enforces pnpm's minimumReleaseAge supply-chain policy (local installs don't). If install fails with ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION, pin the flagged package to a release older than 24h rather than relaxing the policy.