Menu

Individual skill

agentflow

File logs, Git evidence and optional development. Triggered by godev/devlog/ag/agentflow/fast-lane/skip-ag.

skills/agentflow/SKILL.md

Read pinned source

Source commit 0bda4312bf3e781d22468923ce35e9d119378b6f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
180
Repository last updated
Oct 23, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Agentflow v8.4.15

Agentflow keeps owner conversation and live recovery in a configured notebook; advanced rules load only on demand.

`stream(branch/worktree)` is an owner/session feature workspace, usually a branch/worktree with adjacent notebook and configuration. Non-code notebook-only requests may use a stream file and root pointer without branching, even with Git. Ordinary notebooks support no-Git folders; `new-feature:` requires Git. External workers use disposable no-remote clones; internal/host work uses actual tools and recorded ownership.

For releases, update version and heading together: major/minor/patch for breaking changes/features/fixes. This file supplies the release version. Follow repository release instructions; task commits are not releases. For a correction to an already-published release, first fetch and inspect the public branch and treat its current version and files as authoritative; never infer them from a private development checkout. A same-version public correction must preserve newer public files and verify the exact remote commit after pushing.

Incident citations explain failures. Approved redesigns may replace obsolete remedies; preserve hazard checks and history.

## Start here

Already-launched looper workers follow their supplied plan directly, not this host startup/closeout protocol.