Creates an isolated git worktree for task execution. Activates when starting work on a planned issue — sets up a new branch with Linear issue ID, runs project setup, and verifies a clean test baseline before coding begins.
Creates isolated git worktrees for development tasks, sets up the project, and verifies a clean test baseline before coding begins.
/plugin marketplace add brite-nites/brite-claude-plugins/plugin install workflows@brite-claude-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
You are setting up an isolated workspace for a development task. Worktrees prevent work-in-progress from polluting the main working directory and enable easy cleanup or abandonment.
1. Confirm git repo: `git rev-parse --is-inside-work-tree`
2. Confirm clean state: `git status --porcelain` (should be empty)
3. Fetch latest: `git fetch origin`
4. Identify base branch: usually `main` or `master`
If working directory is dirty, ask the developer how to proceed (stash, commit, or abort).
Use the EnterWorktree tool to create an isolated worktree. Name it after the Linear issue:
Branch naming convention: [issue-id]/[short-description]
BRI-1617/writing-plans-skillBRI-42/fix-auth-redirectValidate the issue ID before using it in shell commands — it must match ^[A-Z]+-[0-9]+$. Reject any ID containing spaces, semicolons, pipes, or other shell metacharacters.
If the EnterWorktree tool is not available, fall back to manual git commands (always quote variables).
Derive DESCRIPTION from the issue title: lowercase, replace non-alphanumeric characters with hyphens, collapse consecutive hyphens, strip leading/trailing hyphens, truncate to 50 chars. Validate it matches ^[a-z0-9][a-z0-9-]*[a-z0-9]$ (or ^[a-z0-9]$ for single-char). If validation fails, ask the developer for a safe branch description.
# ISSUE_ID = Linear issue ID (e.g. BRI-42)
# DESCRIPTION = slugified short summary (e.g. fix-auth-redirect)
git worktree add ".claude/worktrees/${ISSUE_ID}" -b "${ISSUE_ID}/${DESCRIPTION}" origin/main
In the new worktree, run project setup:
Install dependencies — Check for and run:
package.json → npm install or yarn install or pnpm installpyproject.toml → pip install -e . or poetry installGemfile → bundle installEnvironment setup — Check for:
.env.example → Copy to .env if .env doesn't exist, warn developer to fill in valuesBefore any changes are made, verify the project is in a known-good state:
package.json)Record the baseline results. If tests fail before you've changed anything, flag it:
"Baseline tests are failing on main. [N] test(s) fail. Proceeding, but these failures are pre-existing — not caused by our changes."
Report to the developer:
## Worktree Ready
**Branch**: [branch-name]
**Path**: [worktree-path]
**Base**: origin/main @ [commit-hash]
**Baseline**:
- Tests: [pass/fail count]
- Build: [clean/errors]
- Lint: [clean/warnings]
Ready to execute the plan.
Worktree cleanup happens during the ship command:
git worktree remove [path] and git branch -D [branch-name]origin/main (or default branch).claude/worktrees/ to avoid cluttering the project rootCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.