Fastapi New Worktree
Use when the user wants a new git worktree created for a task. Picks a kebab-case branch name with a fix/feat/chore/docs/refactor prefix, runs `git worktree add` from the configured base branch, and reports the new path.
Install
$ agentstack add skill-steph-dove-klaussy-agents-fastapi-new-worktree ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-steph-dove-klaussy-agents-fastapi-new-worktree) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Create a new git worktree for the task the user described.
- Read CLAUDE.md to understand the project structure and branching conventions.
- Create a short, descriptive branch name based on the task (e.g.
fix/login-redirect,feat/add-search). - Run
git worktree add ../$(basename $PWD)- -b masterto create the worktree from the configured base branch (the trailing start-point keeps the new branch from inheriting whatever branch the user is currently checked out on). - Confirm the worktree was created successfully with
git worktree list. - Tell the user the full path to the new worktree so they can open it.
Rules:
- Always branch from master unless told otherwise.
- Use lowercase kebab-case for branch names.
- Prefix with
fix/,feat/,chore/,docs/, orrefactor/as appropriate. - Do not start work in the worktree — just create it and report the path.
When NOT to use
- The user just wants a new branch in the current working tree (
git checkout -b) — worktrees are for parallel checkouts, not branch creation alone. - A worktree for the same branch already exists — surface the existing path; don't create a duplicate.
- The user is on a non-worktree-friendly hosting setup (some submodule-heavy repos break with worktrees) — flag the risk before creating.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: steph-dove
- Source: steph-dove/klaussy-agents
- License: MIT
- Homepage: https://klaussy.com
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.