worktree-setup
Create a ready-to-work git worktree — branch, deps, local config, green build — and report it.
- License 许可
- MIT
- 所属仓库
- niieani/caara
- 最近更新
- 2026-11-09
- Stars
- ★ 5
- Forks
- 0
01 前言 Front Matter
- name
- worktree-setup
- description
- Create a ready-to-work git worktree — branch, deps, local config, green build — and report it.
- disable-model-invocation
- true
02 资源文件 1
- 其他worktree-setup35 B
03 SKILL.md 正文
Make a git worktree another agent can start working in immediately, without stumbling over missing dependencies or config. Invoked with a target path and branch name; base ref defaults to HEAD.
Steps
- Preconditions. The repo has at least one commit and the target path does not exist. A worktree checks out committed state only — if the caller's task depends on uncommitted changes, stop and report "commit or stash first".
- Create.
git worktree add <path> -b <branch> [<base-ref>]. - Replicate local config. Copy from the main checkout the untracked files the project needs
to run —
.env,.env.*, and similar gitignored local config. When unsure what is needed, check the project's README and agent instructions for required local files. - Install dependencies. Use the package manager the lockfile implies (
bun.lock→bun install, and so on), run inside the worktree. - Verify green. Run the project's cheapest defined health check — typecheck, build, or test script — inside the worktree. Ready means it passes the same check the main checkout passes.
- Report. Reply with: path, branch, base commit, and which check passed. On any failure, report it verbatim and stop — never hand off a broken worktree as ready.
04 同仓库更多 Skills
panel
Convene a cross-model panel of Caara-backed subagents — ensemble, debate, or cross-review — for results no single model reaches.
logging-best-practices
Logging best practices focused on wide events (canonical log lines) for powerful debugging and analytics
imagegen-frontend-web
Elite frontend image-direction skill for generating premium, conversion-aware website design references. CRITICAL OUTPUT RULE — generate ONE separate horizontal image FOR EVERY section. A landing page with 8 sections produces 8 images. Never compress multiple sections into one image. Enforces composition variety (not always left-text / right-image), background-image freedom, varied CTAs, varied hero scales (giant / mid / mini minimalist), narrative concept spine, second-read moments, and a single consistent palette across all images. Optimized for landing pages, marketing sites, and product comps that developers or coding models can accurately recreate.
effect-ts
Write idiomatic Effect v4 TypeScript following official best practices from effect-solutions and the Effect source. Use when writing, reviewing, or refactoring Effect code: services (ServiceMap.Service), layers and dependency injection, error handling (Schema.TaggedErrorClass), data modeling (Schema.Class, branded types, variants), testing (@effect/vitest), HTTP clients (effect/unstable/http), CLI tools (effect/unstable/cli), config, observability, and project setup. Triggers on: 'Effect', 'effect-ts', '@effect/', 'Schema', 'ServiceMap', 'Layer', 'Effect.gen', 'Effect.fn', 'TaggedError', 'branded types', or any Effect-TS related code.
effect-review
This skill should be used when the user asks to "review code", "review my changes", "check effect patterns", "run effect review", "effect review", "review for effect best practices", or wants a comprehensive code review against Effect-TS conventions, branded types, observability, error handling, test coverage, and UI quality.
effect-best-practices
Enforces Effect-TS patterns for services, errors, layers, and atoms. Use when writing code with Effect.Service, Schema.TaggedError, Layer composition, or effect-atom React components.