Skip to content

xiduzo/wtf / skills/wtf.setup

wtf.setup

Verified

This skill should be used when a user wants to set up WTF in a repository or check that the environment is ready for it — for example "set up wtf", "is wtf ready", "install wtf templates", or "a new dev joined, set them up". Verifies the GitHub CLI and its auth, installs the required gh extensions and the issue and PR templates, configures issue classification, planning, feature scope, and delivery mode, and registers the hooks. Run once per repo when onboarding, or when a contributor joins the project.

shared-references/issue-template-loading.md

View on GitHub
# Issue Template Loading

Shared procedure for any wtf skill that creates a GitHub issue from a template (`wtf.write-epic`, `wtf.write-feature`, `wtf.write-trace`, `wtf.report-bug`) or a PR from a template (`wtf.create-pr`).

## Templates by skill

| Skill | Template path |
|---|---|
| `wtf.write-epic` | `.github/ISSUE_TEMPLATE/EPIC.md` |
| `wtf.write-feature` | `.github/ISSUE_TEMPLATE/FEATURE.md` |
| `wtf.write-trace` | `.github/ISSUE_TEMPLATE/TRACE.md` |
| `wtf.report-bug` | `.github/ISSUE_TEMPLATE/BUG.md` |
| `wtf.create-pr` | `.github/pull_request_template.md` |

Old repos may still hold `.github/ISSUE_TEMPLATE/TASK.md`. Leave it alone. No skill loads it.

## 1. Verify the template exists

Before drafting, use the Read tool to verify the relevant template path exists.

## 2. Halt or run setup if missing

If the template is missing, apply `./questioning-style.md` and ask "`<TEMPLATE_PATH>` is missing. How would you like to proceed?" — header `Template missing`:

- **Run `/wtf.setup`** → invoke `wtf.setup` to scaffold all templates, then halt this skill so the user can re-invoke it
- **Cancel** → halt without scaffolding

Both branches halt the current skill. Do not fall back to drafting without the template. Section names and structure are the contract that downstream skills consume.

## 3. Read the template body

Use only the markdown body **below the second `---` delimiter**. Ignore the YAML frontmatter at the top. It is GitHub issue-form metadata. It is not part of the body the user sees in the rendered issue.

## 4. Fill placeholders

Replace every `[PLACEHOLDER]` (or any section the template treats as fillable) with the gathered context. Preserve every section heading and structural element exactly. Downstream skills parse these by name.

## 5. Write the body to a temp file, then create via the gh body helper

Multi-line bodies must go through a temp file (never an inline `--body`). Every create must go through the **gh body helper** so UTF-8 content survives on Windows. See `./gh-body-helper.md`.

1. Use the Write tool to write the filled body to a temp file `$BODY` (any path under the OS temp dir).
2. Create through the helper:

   ```bash
   # Issue:
   python3 .wtf/gh-body.py create --title "<emoji> <Type>: <title>" --body-file "$BODY" --label "<label>"

   # PR (add --pr and a base branch):
   python3 .wtf/gh-body.py create --pr --title "<title>" --body-file "$BODY" --base "<base_branch>"
   ```

If `.wtf/gh-body.py` is absent, use the raw-`gh` fallback in `./gh-body-helper.md`. That means the repo has not run `wtf.setup` since the guard shipped. That fallback works on macOS/Linux. It is unguarded on Windows.

The exact title prefix (`🎯 Epic:`, `🚀 Feature:`, `☄️ Trace:`, `🐞 Bug:`) and label name are skill-specific. See each skill's create step. The Read → Write-temp → helper pattern is universal.
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: 471kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall