notify

Send a notification — a webhook POST (Slack/Discord-compatible) and/or a best-effort OS desktop notification — so the user is pinged when a long-running flow finishes or hits a milestone, even if they've stepped away from the terminal. Zero-dep; never fails the run. USE when the user asks to "notify me / ping me / let me know when this is done", or when wiring a completion ping into a long `/agentflow:run-workflow`, `/agentflow:foreach`, or `/agentflow:audit`.

Aller à l'installation

Dépôt: AleSaiani/agentflow
Dernière activité de la source: 25 mai 2026 à 18:30
Langue détectée de SKILL.md: anglais
Étoiles: 5
Forks: 0

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.

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

La commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.

Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

SKILL.md

Instructions source · Aperçu en lecture seule

Retour à la recherche Retour à l’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

Tout voir dans ce dépôt

name	notify
user-invocable	false
description	Send a notification — a webhook POST (Slack/Discord-compatible) and/or a best-effort OS desktop notification — so the user is pinged when a long-running flow finishes or hits a milestone, even if they've stepped away from the terminal. Zero-dep; never fails the run. USE when the user asks to "notify me / ping me / let me know when this is done", or when wiring a completion ping into a long `/agentflow:run-workflow`, `/agentflow:foreach`, or `/agentflow:audit`.
allowed-tools	Bash
argument-hint	--message "<text>" [--title "<title>"] [--webhook <url>] [--no-desktop]

/agentflow:notify

Make it visible: say in one line that you're sending a notification.

node "${CLAUDE_PLUGIN_ROOT}/dist/notify.js" --message "<text>" [--title "<title>"] [--webhook <url>] [--no-desktop]

Webhook (best for headless/away): pass --webhook <url> or set $AGENTFLOW_NOTIFY_WEBHOOK. POSTs { "text": "<title>: <message>" } — works with Slack/Discord incoming webhooks.
Desktop: a best-effort OS notification (Windows toast / macOS osascript / Linux notify-send); pass --no-desktop to skip.
Always prints {title, message, sent:[...]} so you can confirm which channels fired (and surface it).

On-demand pattern. When the user says "ping me when the audit is done", run the flow as usual, then at completion call this with a short summary, e.g.:

node "${CLAUDE_PLUGIN_ROOT}/dist/notify.js" --message "audit done — 8 files, 2 critical; digest at ./audit-3f2a-audit.md"

It sends and returns regardless of whether any channel is configured — it never blocks or fails the run.

notify

Informations de source

Options d'installation

Vérifiez les fichiers source

Plus depuis ce dépôt

Plus depuis ce dépôt

/agentflow:notify

/agentflow:notify