ci
Set up or normalize one project Verify command and matching GitHub Actions checks while preserving existing CI. Use for /ci, GitHub Actions setup, pull-request checks, automatic checks, or aligning typecheck, test, and build verification.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 510
- Forks
- 132
01 前言 Front Matter
- name
- ci
- description
- Set up or normalize one project Verify command and matching GitHub Actions checks while preserving existing CI. Use for /ci, GitHub Actions setup, pull-request checks, automatic checks, or aligning typecheck, test, and build verification.
- disable-model-invocation
- true
03 SKILL.md 正文
ci - set up automatic GitHub checks
Context reuse: Reuse any required file already loaded in project instructions or the current session. Read it again only if absent, changed, or exact current bytes or line references are needed.
First action: Before project inspection, preflight, or any other tool call,
publish running to blueprint/.state/run.json when blueprint/.state/
exists. From the project root, run the first helper that exists,
node .agents/skills/blueprint-doctor/scripts/run-state.mjs or
node .claude/skills/blueprint-doctor/scripts/run-state.mjs, with start --command <skill> --summary "<truthful summary>" --boundary <read-only|reviewed|local-only>. Use update at milestones, with --status blocked --resume <command> for a blocker, and finish --status ready|completed
at the end; --help lists every option and blueprint/workflow.md has the full
activity contract. A missing or failing helper is a warning, not a blocker.
Where this sits in the workflow:
/onboard or /adopt -> [ci] -> Verify locally -> GitHub runs Verify
(project commands) (setup) (same recipe) (pull requests)
This skill gives local work and GitHub one shared automated command. It is an optional setup task, not a requirement for using the Blueprint.
Keep the beginner explanation simple:
- Verify is the recipe. It runs checks the project already has.
- GitHub Actions is the worker. It runs the same recipe automatically.
- A GitHub ruleset is the lock. That optional remote setting can require the worker to report green before merge.
This skill configures the recipe and worker. It never changes the remote ruleset, pushes, publishes, or deploys.
Input
No argument is required. A named provider or workflow preference is a request to review, not permission to replace existing CI. This skill's default provider is GitHub Actions because it creates GitHub pull-request checks.
Step 1 - inspect without changing files
Read enough to identify the real project setup:
AGENTS.md, especially Commands and any documentedVerifycommand- package or language manifests and task-runner files
- lockfiles and the package manager they imply
- existing typecheck, test, build, lint, and other quality commands
- test configuration and actual test files
- runtime version files such as
.nvmrc,.node-version,.python-version,go.mod, orrust-toolchain.toml .github/workflows/and any documented external CI- git's current branch, configured default branch, and remotes when available
Do not assume npm, Node.js, main, or GitHub from the Blueprint template. Do not
run installs or edit files during inspection.
If an existing workflow already provides equivalent pull-request checks, explain what it runs. If it is healthy and aligned with a documented Verify command, report that no setup is needed. If normalization would change existing CI, show the proposed change and get explicit approval before editing it.
Step 2 - define one Verify command
Build one command from meaningful checks that actually exist, in this order:
- typecheck
- tests, only when a runner and real test command are configured
- build
Omit missing checks. Do not install a test runner, invent an empty test suite, or add a placeholder command. Lint, formatting, coverage, browser tests, security scans, dependency audits, and version matrices are not part of the beginner default. Preserve them when existing CI already requires them, and discuss any normalization before changing that behavior.
For JavaScript and TypeScript, add or reuse a package script named verify and
invoke it with the detected package manager. For other stacks, use the existing
native task runner or the smallest clear combined command. Document the exact
invocation as Verify in the Commands section of AGENTS.md.
Examples are explanatory only. Never copy them without detecting the project:
Verify: npm run verify
Verify: make verify
Verify: cargo test && cargo build --locked
If no meaningful check exists, stop and explain what is missing. Do not create a workflow that always passes.
Step 3 - create or align the workflow
Create .github/workflows/verify.yml only when that path is free. If it already
exists, never overwrite it silently. Show the exact proposed diff and ask before
changing it.
The workflow should contain only what the detected project needs:
- a clear workflow name such as
Verify pull_request- pushes to the detected default branch
permissions: contents: read- the real runtime version
- checkout and the appropriate runtime setup action
- the lockfile-safe dependency install command
- one final step that runs the exact
Verifycommand fromAGENTS.md
If the default branch cannot be identified from git or project context, ask before writing the push trigger instead of guessing. Preserve all other workflow files. When another workflow overlaps, report the overlap and ask whether to reuse, align, or leave it alone.
Step 4 - prove the setup locally
Run the exact documented Verify command locally. The individual build, test,
or typecheck commands may still be run separately for diagnosis, but the final
proof must use Verify because that is what GitHub will run.
A passing local run proves the recipe against the current working copy. It does not prove dependency installation or command behavior from a fresh checkout. Until the workflow is pushed and reports green on GitHub, describe the setup as prepared locally, not CI verified. The first successful GitHub run is the authoritative clean-checkout proof.
If Verify fails, report the failing subcommand and stop. Do not weaken the command, remove a legitimate check, or describe CI as ready.
Do not push the workflow. A local workflow file does nothing on GitHub until the user later approves a push.
Step 5 - report
Finish with a concise setup report:
- existing CI found and whether it was preserved or changed
- exact
Verifycommand - checks included and checks omitted
- test gate status
- workflow path and triggers
- local Verify result and whether CI is only prepared locally or confirmed by a successful GitHub run
- files changed
- any overlap, uncertainty, or follow-up
Explain that making the GitHub check required is a separate remote ruleset choice after the workflow is pushed. Do not change repository settings or treat that as part of this skill.
Interaction with other skills
/testsadds the real test command to an existing Verify command, but never creates CI by itself./implement,/complete, and/autopilotrun Verify when it is documented, with their existing fallback behavior when it is absent./blueprint-doctordiagnoses drift betweenAGENTS.md, the project command, and the workflow. Missing CI remains informational.
Rules
- Preserve existing CI and custom checks.
- Never invent tests or install a runner as part of CI setup.
- Never add coverage, browser tests, security scans, or matrices by default.
- Never push or change a remote ruleset without separate explicit approval.
- Keep one exact Verify command shared by local work and GitHub.
Formatting
Format the output to match the project's conventions in
blueprint/context/ai-interaction.md: concise, scannable markdown, with lists for
enumerations and tables for matrices rather than dense paragraphs.
04 同仓库更多 Skills
status
暂无简介
status
暂无简介
tests
Set up unit testing with /tests or /tests unit, or explicitly set up browser and end-to-end testing with /tests browser. Reuse or install a suitable test runner, add one example or smoke test, document commands, and verify. Use check for one-time live verification.
prototype
Plan and create throwaway static HTML and CSS mockups with shared design tokens before feature implementation. Use for /prototype, screen mockups, layout exploration, themes, or deciding a project's look and feel.
overview
Validate and normalize project-plan.md and build-plan.md, then generate the durable project-overview.md used by agents. Use for /overview, plan cleanup, generating the first overview, or refreshing context after either plan changes.
onboard
Onboard a fresh or early scaffold after Blueprint is overlaid by tuning commands, standards, adapters, visibility, and context loading. Use for /onboard, fresh installation setup, or what to do after installing Blueprint. Use adopt for an established app.