setup-environment
Pre-install dependencies and configure tools before development work begins. Use at session start on a fresh clone, before kickoff-branch, or when user says setup environment or install deps.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 289
- Forks
- 24
01 前言 Front Matter
- name
- setup-environment
- model
- haiku
- effort
- standard
- description
- Pre-install dependencies and configure tools before development work begins. Use at session start on a fresh clone, before kickoff-branch, or when user says setup environment or install deps.
03 SKILL.md 正文
Setup Environment
HARD GATE — HARD GATE — Environment setup must be idempotent and reproducible. If setup fails, provide clear error messages and remediation steps. Do NOT assume prior state.
Idempotent prep so BUILD phase commands succeed on first run.
Checklist
- Read
CLAUDE.md/CONVENTIONS.mdfor required runtimes and commands. - Verify runtime versions (
node -v,swift --version, etc.). - Install dependencies (
npm ci,bundle install, etc.) — prefer lockfile installs. - Copy
.env.example→.envif documented; never commit secrets. - Run smoke: lint + one fast test or
--versionon key tools. - Record versions in
specs/state.yamlunder Environment.
BCP Plus Counter (optional)
The big-counter tool is an optional dependency for BCP Plus 13-dimension story sizing:
# Install from PyPI (recommended)
pip install big-counter
# Or from npm
npm install -g big-counter
Verify the install: big-counter --version
Skip if BCP Plus sizing is not needed for this project.
Verify
→ verify: test -f CLAUDE.md && grep -q Test CLAUDE.md
04 同仓库更多 Skills
skill-verify-fail-open-fixture
Negative-path fixture for run-skill-verify.sh — must never PASS.
negative-path
暂无简介
write-document
Write, organize, and sync high-integrity technical documents using the BMAD methodology. Ensures every document is Bold, Minimal, Actionable, and Durable. Use when creating architectural docs, technical guides, or organizing the specs/ directory.
wire-observability
Add structured JSON logging, observability commands, and idempotent setup scripts to a project. Use when a project needs production-readiness instrumentation, when user wants structured logging, or as a production-readiness gate at any phase of development.
wire-ci
CI pipeline setup with bundled, forge-neutral templates and local validation. Detects the forge from the git remote, generates workflows for supported forges, and skips honestly for the rest. The CI equivalent of wire-observability.
visual-dashboard
Start a browser-based dashboard that visualizes architecture, implementation plans, and project status. Persists artifacts in .bigpowers/dashboard/. Reads specs/state.yaml, release-plan.yaml, epics, and planning-status via HTTP API or opencode panel.