Skills from clawhub.ai/zlc000190

Use when you have a spec or requirements for a multi-step task, before touching code

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Use when executing implementation plans with independent tasks in the current session

This skill guides finishing a development branch and presents four options to merge, create a PR, keep, or discard. It includes explicit shell commands (e.g., `git checkout`, `git merge`, `git branch -D`, `git worktree remove <worktree-path>`) and network actions (`git push`, `gh pr create`) that the agent would execute.

This skill automates creating isolated git worktrees, selecting directories like `.worktrees` or `~/.config/superpowers/worktrees/<project-name>/`, verifying `.gitignore`, and running project setup and tests. It contains explicit shell commands such as `git worktree add "$path" -b "$BRANCH_NAME"`, `npm install`, and `pytest`, so it enables shell execution (purpose-aligned).

This skill bundle documents how to write and test agent skills and includes runnable utilities and examples. It contains instructions to execute shell commands (e.g., `./render-graphs.js`) and to call external endpoints (e.g., `api.example.com/v2/messages`), enabling code execution and network access.

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

This skill provides templates and instructions to request a code review and run a code-reviewer subagent. It includes fixed shell examples like `BASE_SHA=$(git rev-parse HEAD~1)`, `HEAD_SHA=$(git rev-parse HEAD)`, and `git diff --stat {BASE_SHA}..{HEAD_SHA}`, which are purpose-aligned and low-risk.