Menú
Submit a workflow chain headlessly, where each workflow is gated on the previous workflow's merge gate.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional 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.
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?").
| name | workflow-chain-submit |
| description | Submit a workflow chain headlessly, where each workflow is gated on the previous workflow's merge gate. |
Submit a workflow chain headlessly, where each workflow is gated on the previous workflow's merge gate.
scripts/submit-workflow-chain.shworkflow1.yaml (full first workflow plan)workflow2.template.yaml (template with placeholder)workflow3.template.yaml ... workflowN.template.yamlEach template after the first must contain:
externalDependencies:
- workflowId: "__UPSTREAM_WORKFLOW_ID__"
taskId: "__merge__"
requiredStatus: completed
gatePolicy: completed
./scripts/submit-workflow-chain.sh <workflow1.yaml> <workflow2.template.yaml> [workflow3.template.yaml ...]
./scripts/submit-workflow-chain.sh --gate-policy review_ready <workflow1.yaml> <workflow2.template.yaml> [workflow3.template.yaml ...]
The script prints:
WF1=<workflow-id> ... WFN=<workflow-id> (persisted IDs in chain order)RENDERED_PLAN=<temp-yaml-path> for each rendered template--no-track so submissions return without waiting for full execution.name to avoid transient ID races.--gate-policy completed|review_ready controls cross-workflow merge-gate readiness:
completed (default): downstream waits for upstream merge gate completed.review_ready: downstream can start once upstream merge gate is review_ready, awaiting_approval, or completed.mergify stack push once the branch commits are ready. If the target repo is something else (for example EdbertChan/test-playground), keep normal PR flow unless that repo independently uses Mergify Stacks.