Stats
Actions
Tags
From github-workflow
Runs ./init.sh after git worktree creation if present in project root, extending using-git-worktrees. Auto-activates on init.sh detection.
How this skill is triggered — by the user, by Claude, or both
Slash command
/github-workflow:worktree-init-scriptThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Extends `superpowers:using-git-worktrees` -- after creating a worktree, runs `./init.sh` if the script exists in the project root.
Extends superpowers:using-git-worktrees -- after creating a worktree, runs ./init.sh if the script exists in the project root.
Core principle: Project-specific initialization via a single script replaces auto-detect heuristics.
Automatically activates when:
using-git-worktrees is invokedinit.shModifies step "Run Project Setup":
Instead of auto-detecting by package.json/Cargo.toml:
Check for init.sh:
[ -x ./init.sh ] && echo "init.sh found"
If init.sh exists and is executable -- run it:
./init.sh
If init.sh does not exist -- fall back to standard using-git-worktrees logic
| Situation | Action |
|---|---|
init.sh exists and executable | Run ./init.sh |
init.sh does not exist | Standard setup (npm/cargo/etc) |
init.sh fails | Report error, ask whether to continue |
A ready-made template is available at templates/init.sh in this plugin (mise, submodules, envrc, direnv).
npx claudepluginhub dapi/claude-code-marketplace --plugin github-workflowGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.