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>`.

الانتقال إلى التثبيت

المستودع: AleSaiani/agentflow
آخر نشاط في المصدر: ٢٥ مايو ٢٠٢٦ في ١٨:٣٠
لغة SKILL.md المكتشفة: الإنجليزية
النجوم: ٥
التفرعات: ٠

خيارات التثبيت

يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.

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

يبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.

تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى 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

عرض الكل من هذا المستودع

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

معلومات المصدر

خيارات التثبيت

مراجعة ملفات المصدر

المزيد من هذا المستودع

المزيد من هذا المستودع

/agentflow:history

/agentflow:history