メニュー
Get a new machine "good to go" for Invoker and optionally wire up the Slack integration. Trigger when asked to set up Invoker, run the setup/tutorial, check the environment, fix missing tools, or configure the Slack bot ("set up slack", "/setup", "am I good to go?").
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Generate a reusable loop instruction doc, loop driver script, and Invoker workflow from an interview. Trigger: "loop generator", "generate a loop", "invoker-loop-generator", "/invoker-loop-generator", or requests to build a reusable babysit/watch/retry loop. For benchmark/direct-output prompts with "Required output path", write the requested artifact directly to that literal path, do not ask clarifying questions, and do not validate, review-gate, or submit.
Convert a plan into an Invoker YAML plan file. Trigger: "convert to invoker", "submit to invoker", "create invoker plan", "invoker-plan-to-invoker", "/invoker-plan-to-invoker", "/plan-to-invoker", or turning a plan file into Invoker tasks. For benchmark/direct-output prompts with "Required output path", write a complete YAML document directly to that literal path; it must start with top-level name, onFinish, mergeMode, repoUrl, and tasks, never version or metadata wrappers, and must not scan, validate, submit, or discover env vars.
Create or update a pull request in this repo using the preferred PR schema, upstream-first branch workflow, and repo-specific publication rules. Trigger when asked to make a PR, update a PR body, prepare PR text, publish a stacked PR branch, or whenever a branch/PR change means the GitHub PR metadata may now be stale.
Shape code changes, workflow plans, and PR stacks so each diff is easy to review: one local claim, one safety invariant, clear architectural effect, and an explicit reason for the slice.
Land (queue/merge) a Mergify-managed PR stack safely. Trigger when asked to land, merge, ship, or queue a PR or PR stack with Mergify. Enforces that you act only on SHA-verified PR numbers — never a PR found by branch name.
Push the current branch and verify it against the CI-equivalent test surface on an available SSH remote target, including selecting a target not currently used by Invoker, creating a temporary remote worktree, and running `pnpm run test:all` with CI-style setup. Use when you need pre-merge confidence that mirrors `.github/workflows/ci.yml` more closely than local-only tests.
| name | invoker-setup |
| description | Get a new machine "good to go" for Invoker and optionally wire up the Slack integration. Trigger when asked to set up Invoker, run the setup/tutorial, check the environment, fix missing tools, or configure the Slack bot ("set up slack", "/setup", "am I good to go?"). |
Agent-driven onboarding. It validates the environment, then — only if the user wants it — walks them through the Slack integration. Slack is optional; never push it on a user who declines.
invoker-cli doctor --json
Read the JSON checks. Each has status (ok | warn | error), detail, and remediation.
The desktop System Setup panel shows the same config-aware readiness report as doctor: the
canonical tool set (git, pnpm, gh, docker, ssh, codex, claude, cursor, omp),
the config check, planning tools, and the default preset check.
error blocks "good to go" — surface the remediation verbatim.warn is advisory (an optional tool / preset not installed) — mention it, don't block.default-preset and planning-tools checks are config-aware: an error there means the
configured defaultSlackHarnessPreset points at a CLI that is not installed. This is the most
common Slack failure ("spawn cursor ENOENT") — fix it before going further.Offer to auto-install missing installable tools:
invoker-cli doctor --fix
--fix covers git, pnpm, gh, docker, ssh, codex, claude. cursor and omp are installed manually
(report their remediation).
Ask plainly: "Do you want to set up the Slack integration now?" If no, stop — report that they are
good to go for CLI and UI workflows and that invoker-cli setup slack can add Slack later.
Run the wizard, which writes a ready-to-paste app manifest to ~/.invoker/slack-app-manifest.json
and prompts for the tokens:
invoker-cli setup slack
If you are doing it on the user's behalf (you cannot click api.slack.com), drive it manually:
app_mentions:read, chat:write, files:write, channels:history, channels:read, groups:write, groups:history, users:read,
enables Socket Mode, and subscribes to the app_mention event.xoxb-…).connections:write → copy (xapp-…).C).Adding scopes after install does not update the existing token. The user MUST click Reinstall to Workspace or the bot keeps the old (insufficient) scopes. If the scope check fails, tell them to add the scope and reinstall.
After the user provides the four values, write them to ~/.invoker/.env (the wizard does this) and
confirm against the live Slack API:
invoker-cli setup slack --check
This runs auth.test (bot token + scopes via the x-oauth-scopes header),
apps.connections.open (app token / Socket Mode), and conversations.info (the lobby channel).
Surface each failing check's remediation.
Tell the user to restart Invoker (or that the next launch picks up ~/.invoker/.env). On launch the
app logs a one-line prerequisites summary, and the desktop System Setup panel reports the same
canonical tools, config, planning-tools, and default-preset readiness as invoker-cli doctor; if the
default preset's tool is missing, the readiness check reports an error while startup still continues,
and if Slack env is incomplete it logs exactly which variable is missing and to run invoker-cli setup slack.
~/.invoker/.env (the wizard writes it 0600). Never echo full
tokens back to the user or into logs.