cleanexpo/pi-dev-ops/new-feature
Claude Code and agent skill by cleanexpo/pi-dev-ops
- community
Checking that the SKILL.md file is still in the repository.
Start a new task in an isolated Git worktree branched from origin/main so multiple agents can work on the same repo in parallel without conflicts. Use at the beginning of every new feature, fix, or task — before writing any code.
Install
npx vskill@latest install cleanexpo/pi-dev-ops/new-featureSKILL.md
The same SKILL.md was published earlier as michaelshimeles/skills/new-feature.
New Feature
Every task gets its own worktree and branch, created from the latest origin/main. Never build on main, and never reuse another agent's worktree or branch.
Harness deltas — read first
- Claude Code: the harness creates and manages worktrees itself (under
.claude/worktrees/<name>). Skip steps 3–4 below (no manual git worktree add / remove), and keep the harness-assigned branch name. Steps 1–2 and 5 still apply.
- Cursor-managed worktrees (branches named
worktree-*): same idea —
keep the assigned branch and worktree, apply steps 2 and 5.
- Any other harness: follow all steps.
Steps
- Sync:
git fetch origin.
- Scope check: run
gh pr listand skim the open PRs' changed files
(gh pr diff <n> --name-only). If your task needs files another open PR is editing, stop and ask for direction instead of proceeding. Also check for uncommitted work in the checkout — another agent may be mid-task.
- Name the task: lowercase-with-hyphens plus a short unique suffix,
e.g. user-auth-0816a. If git worktree add fails because the name exists, pick a different name — never force or reuse.
- Create the worktree from the repo root:
``bash git worktree add <worktrees-dir>/<task-name> \ -b <branch-prefix>/<task-name> origin/main ``
Use a gitignored directory for worktrees (e.g. .claude/worktrees/ or .worktrees/) so they can never be committed by accident, and a consistent branch prefix (e.g. agent/). Follow the repo's conventions if it defines them.
- Enter and verify:
``bash cd <worktrees-dir>/<task-name> git branch --show-current # must print your new branch, not main ``
Then install dependencies fresh inside the worktree (worktrees don't share node_modules/virtualenvs) and confirm the runtime version the repo requires before running anything.
Remember
- Worktrees do not isolate shared resources: dev-server ports, shared
databases, and dependency lockfiles are global. Confirm a port answers your process (lsof -i :<port>) before trusting what it serves, and resolve lockfile conflicts by regenerating, never by hand-merging.
- Keep the worktree until the PR is merged or closed. Cleanup after merge:
``bash git worktree remove <worktrees-dir>/<task-name> git branch -D <branch-prefix>/<task-name> ``
-D is expected: after a squash- or rebase-merge, -d refuses even though the work is merged.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills-library/skills/new-feature/SKILL.md
Popularity
- Repository stars
- 1
- 7-day trend score
- 8
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/cleanexpo/pi-dev-ops/new-feature)