workflows

List the reusable workflows authored in this workspace — every `workflows/<name>/` folder, with its format (WORKFLOW.md / workflow.json), stage count, declared params, and description (read from either format). The "what workflows do I have to run" catalog. Read-only, never mutates state. USE when the user asks "what workflows do I have", "list my workflows", "which flows can I run", "show available workflows", or before running one and they don't remember the name/params. To run one use `/agentflow:run-workflow <path>`; to author a new one use `/agentflow:create-workflow`.

설치로 이동

저장소: AleSaiani/agentflow
최근 소스 활동: 2026년 5월 26일 07:58
감지된 SKILL.md 언어: 영어
스타: 5
포크: 0

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.

npx skills add https://github.com/AleSaiani/agentflow --skill workflows

명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.

로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md

소스 지침 · 읽기 전용 미리보기

검색으로 돌아가기 설치로 돌아가기

foreach

Apply ONE operation to EVERY item of a list — the **map** (N→N). The operation is a prompt; items come from a JSON list, a markdown checklist, or another run's output. Runs in parallel subagents or inline in the main thread, with persistent state and cross-turn auto-continue. USE on any "do the same thing to each of these" intent — formal OR casual: "for each X…", "per ogni…", "go through these one by one", "do every item in TODO.md", "review each of these files", "handle all of them", a glob, a folder. Trigger on the INTENT, then judge by count (the count gate, Step 2.5): - 1–2 items → just do it inline, no machinery; - a borderline handful (~3–10) → ask whether to use the durable/parallel mechanism or handle inline; - genuinely many, or heavy/independent items → use foreach. DON'T use when the list must first be generated from a spec (→ /agentflow:enumerate, then foreach), or you need one combined output (→ /agentflow:reduce). For the prebuilt "review every file → digest", use /agentflow:audit. Explicit

2026-05-27

run-workflow

Run a declarative workflow-file end to end: init a `/agentflow:pipe` from a JSON `WorkflowSpec`, then drive it to completion — auto-running every bash/json/deterministic stage and dispatching agents only where genuinely needed. Use `--dry-run` to preview the resolved plan without executing anything. The one-command way to execute a reusable, versioned workflow. USE when the user points at a workflow file ("run this workflow", "run workflows/audit/WORKFLOW.md", "run my pipeline") or wants to run a saved `WorkflowSpec`. Workflows are normally self-contained folders (`workflows/<name>/WORKFLOW.md` + sibling scripts), but a bare `.json` path also works.

2026-05-27

audit

Deep code-audit recipe: discover files in a target → review each (LLM, cached) → partition by component → executive digest with hotspots and recurring patterns. A layer-3 recipe over /agentflow:pipe (the 6-stage pipeline and caching are detailed in the body). USE when the user asks to "review / audit / find bugs across" a folder, repo, or glob and wants a persisted, structured report — and the target is large enough (≥ ~10 files) that per-file parallelism plus a digest beats reading inline. DON'T use for a few named files (read them inline), exploratory questions ("what does this do?"), or generic per-item work that isn't a code review (→ /agentflow:foreach). Not a `/`-menu command — it's the shipped `workflows/audit/` recipe: reach it by asking ("audit src for bugs"), or run it directly with `/agentflow:run-workflow workflows/audit/WORKFLOW.md`.

2026-05-26

이 저장소의 모든 Skills 보기

name	workflows
description	List the reusable workflows authored in this workspace — every `workflows/<name>/` folder, with its format (WORKFLOW.md / workflow.json), stage count, declared params, and description (read from either format). The "what workflows do I have to run" catalog. Read-only, never mutates state. USE when the user asks "what workflows do I have", "list my workflows", "which flows can I run", "show available workflows", or before running one and they don't remember the name/params. To run one use `/agentflow:run-workflow <path>`; to author a new one use `/agentflow:create-workflow`.
allowed-tools	Bash, Read
argument-hint	["--json"]
disable-model-invocation	false

/agentflow:workflows

Make it visible: this is read-only; just run it and surface the list.

Lists every workflow under <workspace>/workflows/ — a folder with a WORKFLOW.md (human-authored) and/or a workflow.json (compiled spec), or a bare workflows/<name>.json.

node "${CLAUDE_PLUGIN_ROOT}/dist/inspect.js" workflows [--json]

For each: name, format, stage count, declared params, the path, and a one-line description — read from WORKFLOW.md or workflow.json alike. Use it to find the right workflow + its params, then run it:

/agentflow:run-workflow workflows/<name>/WORKFLOW.md --param <name>=<value> …

Related: /agentflow:create-workflow (author a new workflow), /agentflow:run-workflow (execute one), /agentflow:board (active runs).

workflows

소스 정보

설치 방법

소스 파일 검토

이 저장소의 다른 Skills

이 저장소의 다른 Skills

/agentflow:workflows

/agentflow:workflows