jabrena/plinth / skills/004-commands-installation
004-commands-installation
VerifiedUse when you need to install the embedded project commands into command directories (.github/commands, .claude/commands, .cursor/command, .codex/commands), selecting the destination interactively and copying the embedded command definitions from project assets. This should trigger for requests such as Install embedded commands; Bootstrap .cursor/command; Bootstrap .claude/commands; Copy project commands; Install project command suite. Part of Plinth Toolkit
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.9 KB |
| assets/commands/benchmark.md | markdown | 2.0 KB |
| assets/commands/close-spec.md | markdown | 1.7 KB |
| assets/commands/create-acceptance-criteria.md | markdown | 6.2 KB |
| assets/commands/create-adr.md | markdown | 1.3 KB |
| assets/commands/create-diagram.md | markdown | 1.4 KB |
| assets/commands/create-feature-branch.md | markdown | 3.0 KB |
| assets/commands/create-spec.md | markdown | 3.5 KB |
| assets/commands/create-worktree.md | markdown | 3.1 KB |
| assets/commands/explore-design.md | markdown | 4.6 KB |
| assets/commands/explore-problem.md | markdown | 6.7 KB |
| assets/commands/implement-spec.md | markdown | 11.6 KB |
| assets/commands/onboarding.md | markdown | 5.9 KB |
| assets/commands/profile.md | markdown | 1.9 KB |
| assets/commands/update-issue.md | markdown | 1.8 KB |
| references/004-commands-installation.md | markdown | 3.5 KB |
assets/commands/create-worktree.md
View on GitHub---
description: 'Create an isolated Git worktree on a new conventionally named branch.'
argument-hint: '[issue-or-change|type description] [target-path] [base-reference]'
model: 'inherit'
agent: 'plinth-tech-lead'
tools:
- 'Read'
- 'Bash'
metadata:
author: 'Juan Antonio Breña Moral'
version: '0.19.0'
---
# create-worktree
Always create a new branch and linked Git worktree for isolated or parallel work without changing the current checkout.
## Usage
```text
/create-worktree <issue-or-change|type description> [<target-path>] [<base-reference>]
```
## Accepted Inputs
- An issue/change identifier, or an explicit branch type and description
- Optional preferred target path
- Optional base reference
- Supported branch types: `feat`, `fix`, `docs`, `refactor`, and `chore`
- Preferred branch format: `<type>/<issue-or-change>-<kebab-case-description>` when an issue or OpenSpec change is available, otherwise `<type>/<kebab-case-description>`
- Fresh-name rule: if the preferred branch name or target path already exists, derive the next unused suffix such as `-2`, `-3`, and continue with the fresh branch/worktree
## Owning Agent
`@plinth-tech-lead`
## Associated Capabilities
- Git branch naming and validation
- Git linked worktrees
- Parallel OpenSpec child-change coordination
## Workflow
1. Resolve the preferred branch name from the issue/change identifier or explicit branch details.
2. Resolve an absolute preferred target path and the base reference.
3. Resolve the repository default branch and the current branch.
4. Verify the current checkout is `main` or the repository default branch before creating the worktree branch.
5. If the current branch is not `main` or the default branch, stop and ask whether to switch to the default branch, choose a different base, or continue explicitly from the current branch.
6. Verify the repository and selected base reference are valid before creating anything.
7. Derive a fresh branch name and fresh target path when the preferred branch exists, is checked out in another worktree, or the preferred target path exists.
8. Verify the final branch name does not exist, is not checked out in another worktree, and the final target path does not exist.
9. Run the equivalent of `git worktree add -b <branch> <target-path> <base-reference>`.
10. Report the created branch, absolute worktree path, base reference, and cleanup command.
## Output
- Created local branch
- Created linked worktree
- Exact branch name, absolute path, and base reference
- Cleanup command: `git worktree remove <absolute-worktree-path>`
## Safeguards
- Never reuse the current checkout or an existing worktree for the requested work.
- When the preferred branch or path conflicts with existing state, choose a fresh unused branch name and target path instead of reusing or overwriting existing state.
- Stop and ask when the current branch is not `main` or the repository default branch.
- Stop if the base reference is invalid.
- Leave existing branches, worktrees, directories, and files unchanged on conflict.
- Do not commit, push, remove worktrees, delete branches, or use force.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |