history

Chronological history of Agent Flow runs in this workspace — every run across all primitives, most recent first, with status, agent count, and cost. The "what have I run, and when" log. Read-only, never mutates state. USE when the user asks "what did I run", "show history", "recent runs", "what flows have run", "did the X run earlier", "list past runs". For a live dashboard of what's *active* use `/agentflow:board`; for one run's details use `/agentflow:inspect show <id>`.

Jump to install

Repository: AleSaiani/agentflow
Last source activity: May 25, 2026 at 18:30
Detected SKILL.md language: English
Stars: 5
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

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

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

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

View all from this repository

name	history
user-invocable	false
description	Chronological history of Agent Flow runs in this workspace — every run across all primitives, most recent first, with status, agent count, and cost. The "what have I run, and when" log. Read-only, never mutates state. USE when the user asks "what did I run", "show history", "recent runs", "what flows have run", "did the X run earlier", "list past runs". For a live dashboard of what's active use `/agentflow:board`; for one run's details use `/agentflow:inspect show <id>`.
allowed-tools	Bash, Read
argument-hint	[--limit N] [--cmd enumerate\|foreach\|group\|iterate\|reduce\|pipe] [--json]
disable-model-invocation	false

/agentflow:history

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

A time-ordered log of every run on disk (newest first). The history is the run state — there's no separate logfile; each run records its own timestamps and budget.

node "${CLAUDE_PLUGIN_ROOT}/dist/inspect.js" history [--limit N] [--cmd <name>] [--json]

Columns: UPDATED_AT · CMD · RUN_ID · STATUS · AGENTS · USD$. Defaults to the 20 most recent; --limit 0 for all, --cmd to filter to one primitive, --json for structured output.

Related: /agentflow:board (active runs + blockers + suggested next action), /agentflow:inspect show <id> (one run's detail), /agentflow:inspect timeline <id> (a single run's event log).

history

Source facts

Install options

Review the source files

More from this repository

More from this repository

/agentflow:history

/agentflow:history