メニュー
Run the e22-plugins verification gates and report a per-gate pass/fail summary, with the single re-run command for any failure. Repo-local dev helper; a thin wrapper over the existing mise tasks — no new validation.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Scaffold an autonomous loop for a managed repo — a scheduled GitHub Actions workflow that wakes on its own, triages work (CI failures, open issues, drift) via /steer:audit + /steer:next, drafts fixes in isolated worktrees reviewed by steer-reviewer, and opens draft PRs. Wired to stop at every human gate (rule 53): it delivers up to the PR, it never merges/deploys. Instantiates templates/github/workflows/steer-loop.yml and lands it via the normal autonomous branch-push + PR (Commit autonomy — the merge review is the gate).
Adopt an existing repo that never went through bootstrap (a "vibe-coded" app) into the standards — reverse-engineer the /spec from the code, triage productionization (Keep/Refactor/Rewrite/Reject per area), and sync the plugin's bundled scaffolding without clobbering working code.
Guided flow for a non-technical product owner — idea → interview → approved spec → working local app → handoff for dev review, with Claude driving all tooling.
One-time setup for a new managed repo — bootstrap the /spec spine + repo scaffolding from the plugin's bundled scaffold (the plugin replaces the old static repository-template as the bootstrap source), or resolve placeholders in a legacy template fork. In both cases pin the toolchain and leave the repo working spec-first.
Absorb a PO-supplied spec/roadmap document (docx/pptx/xlsx/pdf) into the /spec spine — version-stamp and commit the binary plus a normalized Markdown extraction under spec/sources/ — relocating the dropped file into that canonical home so it does not linger where it was uploaded — git-diff it against the prior version, and surface a structured what-changed report. Then route the real changes into intent/contract/vision/roadmap and the tracker via the relevant skills, never clobbering human-authored prose (conflicts become Open questions). Idempotent on an unchanged document. In clarify mode, absorbs a client clarification document instead: it segments the extraction, maps each unit against open questions and the feature list, and sorts them into a three-bucket worklist — answers routed to /steer:questions, new scope to the reconcile rows, unmatched surfaced for the human.
Make GitHub branch protection — the real gate against direct-push-to-main — reliable on a managed repo: read policy/branch-protection.yml, diff it against the repo's live protection, and on explicit confirmation apply the missing settings via gh api (branch protection, secret scanning, Dependabot alerts). Verify by default; configures the GitHub-side gate only — steer is advisory in the local session (rule 95) and cannot block local pushes.
| name | preflight |
| description | Run the e22-plugins verification gates and report a per-gate pass/fail summary, with the single re-run command for any failure. Repo-local dev helper; a thin wrapper over the existing mise tasks — no new validation. |
| allowed-tools | ["Bash(mise run *)","Bash(mise tasks*)","Bash(uv run python scripts/*)","Bash(sh plugins/steer/hooks/tests/run.sh)"] |
A thin convenience wrapper over the existing mise tasks. It adds no
validation logic; it just runs the gates and summarizes them. See
AUTHORING.md → "What I touched → what to run".
Pick the depth:
mise run ci (full: lint, plugin-check,
actions, fixtures, test, shell, hooktests, version-scan).--fast or before a local commit → mise run check (lint, plugin-check,
actions only).Run it and capture output.
Report a per-gate summary — one line per gate with ✅/❌. For any failure, give the single command to reproduce just that gate:
| Failed gate | Re-run |
|---|---|
| lint | uv run ruff check . && uv run ruff format --check . |
| plugin-check | uv run python scripts/check_plugin.py (then check_standards.py, check_changelog.py) |
| fixtures | uv run python scripts/check_fixtures.py |
| test | uv run pytest |
| shell | shellcheck plugins/steer/hooks/*.sh plugins/steer/hooks/lib/*.sh ... |
| hooktests | sh plugins/steer/hooks/tests/run.sh |
| actions | actionlint |
| version-scan | sh plugins/steer/scripts/scan-version-pins.sh . |
If everything passed, say so plainly and state which gate level ran
(check vs ci). Do not claim ci-level confidence after only running
check.