agentsclimarketplace

Fastapi new worktree

Skill steph-dove/klaussy-agents/examples/fastapi/.cursor/skills/fastapi-new-worktree

A multi-agent context, rules, and hooks boilerplate generator. With a single command, it scaffolds conventions, namespaced skills, stack-appropriate settings, and interactive guardrails for seven major AI coding environments, matching each agent's native file formats and capability profiles.

Install
npx -y skills add steph-dove/klaussy-agents --skill fastapi-new-worktree

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 11 stars11 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

1.8 KB, as published. Nobody here has run it

Create a new git worktree for the task the user described.

  1. Read CLAUDE.md to understand the project structure and branching conventions.
  2. Create a short, descriptive branch name based on the task (e.g. fix/login-redirect, feat/add-search).
  3. Take the current repository's folder name (you already know the working directory — don't compute it with a shell substitution like $(basename $PWD), which isn't portable to Windows shells), then run git worktree add ../<repo-folder>-<branch-name> -b <branch-name> master to 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).
  4. Confirm the worktree was created successfully with git worktree list.
  5. 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/, or refactor/ 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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.