New Feature Setup

What it does

When your agent uses it

• Starting a new feature
• Start a new feature
• Spin up a worktree

Example prompts

• “start a new feature”
• “spin up a worktree”
• “begin ticket”
• “/new-feature-setup”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

1. 1Create the worktree from origin/main
2. 2Let the hook do everything else
3. 3Start the dev server — coordinate with the "active worktree" rule
4. 4Code the feature
5. 5When done, clean up

What it can do on your machine

Read from SKILL.md and the folder at commit 1bf4d52. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • bun
  • git
  • bunx

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md. Its commands use git and bunx, which can reach the network depending on how they are called.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

New Feature Setup loads about 1.4k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 610 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~78

When it runs · the whole SKILL.md, loaded when a task matches

~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

• NoteMentions a .env fileSKILL.md:16

  - Before copying `.env` files around by hand

• NoteMentions a .env fileSKILL.md:42

  2. Links `.env*` files from the main clone (copies the ones with `DATABASE_URL`, rewriting it to the isolated URL; symli

• NoteMentions a .env fileSKILL.md:62

  01` (or `3334`, etc.) to the worktree's `.env.local`. `.env.local` is not symlinked and stays per-worktree.

• NoteMentions a .env fileSKILL.md:88

  orktree (no trigger dev, custom port via .env.local)

• NoteMentions a .env fileSKILL.md:89

  echo "PORT=3001" >> apps/app/.env.local

• NoteMentions a .env fileSKILL.md:101

  - `cp` or `ln -s` to copy `.env` files into a worktree

• NoteMentions a .env fileSKILL.md:111

  | Editing `.env` in a worktree and expecting it to propagate | If it's a symlink, yes; if it's a real copy (has `DATABAS

• NoteMentions a .env fileSKILL.md:112

  ut `PORT=<free-port>` in the worktree's `.env.local` |

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from trycompai/comp at commit 1bf4d52, republished under its AGPL-3.0 licence (© trycompai). 610 words, ~1,385 tokens.

name

new-feature-setup

description

Use when starting a new feature, Linear ticket, or bugfix in this repo — establishes the branch + worktree + env + DB + dev-server conventions so the work is immediately ready to code without fighting infra. Triggers on "start a new feature", "spin up a worktree", "begin ticket", "new branch".

cd /Users/mariano/code/comp   # must be the MAIN clone, not another worktree
git fetch origin main
git worktree add .worktrees/<short-slug> -b <branch-name> origin/main

# Spin up a new worktree (does env + DB + install + migrate + generate automatically)
git worktree add .worktrees/<slug> -b mariano/<branch-name> origin/main

# Start dev — ONLY in the worktree you're actively iterating on
cd .worktrees/<slug>
bun run dev

# Start dev in a background worktree (no trigger dev, custom port via .env.local)
echo "PORT=3001" >> apps/app/.env.local
bun run --filter '@trycompai/app' dev:no-trigger

# Clean up when branch is done
# (use the stale-worktree-cleanup skill)

© trycompai, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/new-feature-setup of trycompai/comp.

Open the folder on GitHubat commit 1bf4d52