Agent skill

Treetopia

by fmflurry in fmflurry/settings-opencode

Use ONLY when the user explicitly asks to create/use a worktree, isolated worktree, parallel feature branch, or avoid branch collision; immediately create an isolated OpenCode worktree for that task.

MITAuto-check passedDevelopment

Install Treetopia

skills CLI
$ npx skills add fmflurry/settings-opencode --skill treetopia -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install fmflurry/settings-opencode treetopia --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/fmflurry/settings-opencode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/treetopia .claude/skills/treetopia && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
treetopia
GitHub stars
171
Token cost
~1.1k tokens
SKILL.md length
534 words
Files
1
Skills in repo
20
Repo updated
First seen
Licence
MIT

At a glance

Use ONLY when the user explicitly asks to create/use a worktree, isolated worktree, parallel feature branch, or avoid branch collision; immediately create an isolated OpenCode worktree for that task.

  • Works in 4 steps: Derive a concise branch name from the… → Determine the base branch. → Immediately call worktree_create. → …
  • Explicitly asks to create/use a worktree
  • SKILL.md covers Trigger Rules, Purpose, Start Workflow and Development Guidance Inside…, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Treetopia is an agent skill from fmflurry/settings-opencode. Use ONLY when the user explicitly asks to create/use a worktree, isolated worktree, parallel feature branch, or avoid branch collision; immediately create an isolated OpenCode worktree for that task. Do not trigger for ordinary feature work.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Git worktrees. The repository describes itself as: Custom OpenCode settings. The licence is MIT.

When your agent uses it

  • Explicitly asks to create/use a worktree
  • Isolated worktree
  • Parallel feature branch
  • Avoid branch collision

Example prompts

  • “/treetopia”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Derive a concise branch name from the user's task.
  2. Determine the base branch.
  3. Immediately call worktree_create.
  4. Continue development inside the new worktree/session created by the tool.

What it can do on your machine

Read from SKILL.md and the folder at commit 0e6c33c. 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

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

    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

Treetopia loads about 1.1k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 534 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~63
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

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

Auto-check passed

The automated check found no risky patterns in SKILL.md.

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 fmflurry/settings-opencode at commit 0e6c33c, republished under its MIT licence (© fmflurry). 534 words, ~1,118 tokens.

Download SKILL.mdSave it as .claude/skills/treetopia/SKILL.md (or your agent's skills folder).
name
treetopia
description
Use ONLY when the user explicitly asks to create/use a worktree, isolated worktree, parallel feature branch, or avoid branch collision; immediately create an isolated OpenCode worktree for that task. Do not trigger for ordinary feature work.

Treetopia

Create an isolated OpenCode worktree whenever the user explicitly wants branch isolation, parallel feature work, or protection from branch collisions.

Trigger Rules

Use this skill only when the user explicitly says one of these intents:

  • Create a worktree.
  • Use a worktree.
  • Use an isolated worktree.
  • Create a parallel feature branch.
  • Avoid branch collision.
  • Keep two agents or two features from sharing one branch.

Do not use this skill merely because the user asks for normal implementation, refactor, testing, or feature work. Ordinary feature work stays in the current checkout unless the user explicitly requests isolation.

Purpose

Prevent two primary agents or two active features from sharing the same branch and overwriting or colliding with each other's changes.

Start Workflow

When triggered:

  1. Derive a concise branch name from the user's task.
    • Use lowercase words separated by hyphens.
    • Prefer a short prefix such as feature/, fix/, or chore/ when obvious.
    • Keep the name specific enough to identify the task.
  2. Determine the base branch.
    • If the user names a base branch, use that branch.
    • Otherwise, default to the current branch.
  3. Immediately call worktree_create.
    • Pass the derived branch name.
    • Pass the base branch only when the user named one or the tool requires it.
  4. Continue development inside the new worktree/session created by the tool.

Example tool intent:

text
worktree_create(branch: "feature/customer-import", baseBranch: "main")

If no base branch was named:

text
worktree_create(branch: "fix/login-timeout")

Development Guidance Inside Worktree

  • Treat the worktree as the isolated task workspace.
  • Follow normal project instructions, architecture rules, and verification gates.
  • Do not assume the original checkout has your worktree changes.
  • Avoid cross-worktree edits unless the user explicitly asks.
  • Preserve the verification gate before proposing teardown, merge, or cleanup.

Tool-Use Guidance

  • Use worktree_create for worktree creation.
  • Use git-specialist for git-only operations when available, including merge, branch creation, branch deletion, status checks, and cleanup.
  • Ask before any destructive or shared-state action, including branch deletion, worktree deletion, force push, merge into shared branches, or overwriting files.
  • Do not auto-delete a worktree.
  • Do not auto-merge a branch.
  • Do not bypass hooks or verification.
Show full SKILL.md (200 more words)Show less

Teardown Workflow

When development in the worktree is finished:

  1. Run required verification first.
    • Build/typecheck/lint as appropriate for the project.
    • Run tests when behavior changed.
    • Fix failures caused by the worktree changes before offering teardown.
  2. Offer a cleanup/merge path.
    • Merge back into the original branch, or
    • Merge into another user-named target branch.
  3. If the user names a target branch that does not exist, offer to create it.
  4. Ask for explicit confirmation before performing merge, branch creation, branch deletion, or worktree deletion.
  5. After confirmation, use git-specialist for git-only operations when available.
  6. After merge or cleanup, report what changed and what remains.

Suggested teardown prompt:

text
Worktree verification passed. Merge/cleanup options:
1. Merge this branch back into the original branch.
2. Merge into another target branch. If it does not exist, I can create it first.
3. Keep worktree and branch for later.

Which path should I take?

Safety Rules

  • Never delete the worktree without explicit user confirmation.
  • Never merge without explicit user confirmation.
  • Never create a named target branch without explicit user confirmation.
  • Never force-push unless the user explicitly asks in the same turn.
  • Never skip verification before teardown unless the user explicitly waives it.
  • If a merge conflict occurs, stop and report the conflict status before resolving unless the user already authorized conflict resolution.

Activation Note

After this skill is installed and OpenCode is restarted, it becomes active. Running OpenCode sessions keep using the skills loaded at startup.

© fmflurry, MIT. 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 skills/treetopia of fmflurry/settings-opencode.

Open the folder on GitHubat commit 0e6c33c

Compare with similar skills

Treetopia next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Treetopia compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Treetopia this skillfmflurry/settings-opencode171—~1.1kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Migrate Core Code to Submodulestinyhumansai/openhuman42k—~2.6kAutomated safety check: PassGPL-3.0
Finishing A Development Branchfarm-fe/farm5.6k34 repos~1.8kAutomated safety check: PassMIT
Git Worktree Cleanuplobehub/lobehub83k—~2.8kAutomated safety check: PassCustom licence
Keep Codex Fastvibeforge1111/keep-codex-fast1.6k—~3.1kAutomated safety check: PassMIT

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Migrate Core Code to Submodules

    tinyhumansai/openhuman

    Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.

    42k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed
  • A skill your agent uses when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for…

    5.6k GitHub starsUsed in 34 repos~1.8k tokens
    DevelopmentAuto-check passed
  • Git Worktree Cleanup

    lobehub/lobehub

    Audits stale Git worktrees and branches with a bundled script, classifies each one, and deletes only after you approve the exact candidates.

    83k GitHub stars~2.8k tokensUpdated today
    DevelopmentAuto-check passed
  • Keep Codex Fast

    vibeforge1111/keep-codex-fast

    A skill your agent uses when Codex feels slow or bloated, when local sessions/logs/worktrees/config have grown over time, or when a user wants safe maintenance for Codex Desktop/CLI state.

    1.6k GitHub stars~3.1k tokensUpdated 5 mo ago
    DevelopmentAuto-check passed
  • Pre-Release PR Triage

    jamiepine/voicebox

    Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.

    57k GitHub stars~3.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from fmflurry/settings-opencode

All 20 skills in this repo
  • Show Your Work

    fmflurry/settings-opencode

    Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result).

    171 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed
  • Playwright E2E Authoring

    fmflurry/settings-opencode

    Scaffold and extend Playwright E2E tests for the gc.platform suite (tests/playwright), wiring every artifact to the real frontend (localhost:4200) + real .NET backend — never mocks.

    171 GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Why

    fmflurry/settings-opencode

    A skill your agent uses for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds.

    171 GitHub stars~2k tokensUpdated yesterday
    Auto-check passed
  • Angular Accessibility

    fmflurry/settings-opencode

    Audit and fix common accessibility issues in Angular templates and Angular Material components.

    171 GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed
  • Angular Clean Architecture

    fmflurry/settings-opencode

    Scaffolds and extends Angular standalone feature MODULES under src/app/modules/{name} using Clean Architecture layering (presentation/application/core/infrastructure), a self-registering module…

    171 GitHub stars~3.6k tokensUpdated yesterday
    Auto-check passed
  • Angular Cop

    fmflurry/settings-opencode

    Pre-merge code review for Angular + TypeScript pull requests.

    171 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Treetopia

What does Treetopia do?

Use ONLY when the user explicitly asks to create/use a worktree, isolated worktree, parallel feature branch, or avoid branch collision; immediately create an isolated OpenCode worktree for that task. Treetopia is an agent skill from fmflurry/settings-opencode. Use ONLY when the user explicitly asks to create/use a worktree, isolated worktree, parallel feature branch, or avoid branch collision; immediately create an isolated OpenCode worktree for that task.

When should I use Treetopia?

Treetopia fits situations like: explicitly asks to create/use a worktree; isolated worktree; parallel feature branch; avoid branch collision.

How do I install Treetopia in Claude Code?

Run `npx skills add fmflurry/settings-opencode --skill treetopia -a claude-code`. Or copy the skill folder (skills/treetopia in fmflurry/settings-opencode) into .claude/skills/treetopia in your project. Claude Code loads it when a task matches its description.

How do I install Treetopia in Codex?

Run `npx skills add fmflurry/settings-opencode --skill treetopia -a codex`. Or copy the skill folder (skills/treetopia in fmflurry/settings-opencode) into .agents/skills/treetopia in your project. Codex loads it when a task matches its description.

Can I use Treetopia in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add fmflurry/settings-opencode --skill treetopia -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/treetopia, .gemini/skills/treetopia, .github/skills/treetopia and .opencode/skills/treetopia in your project.

What does Treetopia need to run?

SKILL.md names no scripts, command-line tools or credentials: Treetopia is instructions for the agent only.

Does Treetopia access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Treetopia safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Treetopia use?

Treetopia is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Treetopia use?

About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Treetopia?

Skills that share tags, products or a category with Treetopia: Finishing a Development Branch (obra/superpowers, 296k stars), Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars), Finishing A Development Branch (farm-fe/farm, 5.6k stars) and Git Worktree Cleanup (lobehub/lobehub, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Treetopia?

fmflurry (a GitHub user) maintains it in fmflurry/settings-opencode, which has 171 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 7, 2026.

Source: fmflurry/settings-opencode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.