원클릭으로
new-exec-type
Add a new executable type to the flow runner (a new kind of automation block users can define in .flow files).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Add a new executable type to the flow runner (a new kind of automation block users can define in .flow files).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
This project uses flow for automation. When asked to build, test, run, deploy, lint, generate, or perform any dev task, check for a flow executable before falling back to raw shell commands.
Scaffold a new Cobra CLI command following the project's patterns.
Run a pre-PR readiness check and report READY or NOT READY.
Run flow validate and fix any failures. Invoke after completing a feature or bug fix to confirm the codebase is clean before committing.
| name | new-exec-type |
| description | Add a new executable type to the flow runner (a new kind of automation block users can define in .flow files). |
| disable-model-invocation | true |
| argument-hint | <type-name> — description of what this executable type does |
| allowed-tools | Bash(flow generate:*) Bash(flow validate:*) Bash(flow build:*) Bash(go test:*) Read |
Add a new executable type to the flow runner for: $ARGUMENTS
An "executable type" is a new automation block users can declare in .flow files (like exec, serial, parallel, render). Follow these steps in order:
Schema first — add the new type's fields to types/executable/schema.yaml.
Read the existing schema to match the structure. Run flow generate to regenerate types/executable/generated.go.
Runner handler — create internal/runner/<type>.go implementing the runner interface.
Read internal/runner/exec.go or internal/runner/serial.go as reference for the exact interface and pattern.
Register the type — wire the new handler into internal/runner/runner.go (the dispatch table).
Parser support — update internal/fileparser/ if needed to recognize and validate the new type during YAML parsing.
Tests — add unit tests in internal/runner/<type>_test.go using Ginkgo.
Use Describe/It/Entry — never FDescribe/FIt. Cover happy path and error cases.
Validate — run flow validate to confirm generate, lint, and tests all pass.
Do not skip the schema step — editing generated files directly will cause CI to fail.