CLI Reference

Current — this is the living version. Historical snapshots are linked from Index-Releases.

CLI Reference

Deterministic tools used by okf-graph-eng skills and the GraphEngineer agent.

scripts/okf-graph.py

Fallback when okf / okfcli is not installed. Operates on an OKF bundle directory (e.g. sample-okf, .okf).

python3 scripts/okf-graph.py impact <bundle> <concept>
python3 scripts/okf-graph.py backlinks <bundle> <concept>
python3 scripts/okf-graph.py subgraph <bundle> <concept> [--hops N]
python3 scripts/okf-graph.py pack <bundle> <concept> [--hops 2] [--max-nodes 20] [--undirected]
python3 scripts/okf-graph.py edges <bundle> [--from PATH] [--rel REL]
python3 scripts/okf-graph.py graph <bundle> [--format mermaid|json|html] [--focus PATH] [--hops 2]
python3 scripts/okf-graph.py validate <bundle> [--strict]
python3 scripts/okf-graph.py orphans <bundle>

Command	Output
impact	Inbound/outbound closures, typed direct_edges, suggested update order (JSON)
backlinks	Concepts linking to the target, with their rels (JSON)
subgraph	Undirected N-hop neighborhood: nodes + edges (JSON)
pack	Progressive disclosure pack; JSON includes ready-to-paste markdown. Outbound-only by default — --undirected also walks inbound edges, which can flood via hub indexes
edges	Edge list; filter by --rel routes_to etc.
graph	Whole bundle or --focus neighborhood. --format json prints JSON; mermaid (default) and html print the artifact itself
validate	Conformance + broken links + links pointing outside the bundle + unverified high-impact (JSON). --strict also exits non-zero on warnings — used by CI
orphans	Concepts with no inbound or outbound edges (JSON)

The html view is fully self-contained: Mermaid source plus concept/edge tables, no CDN or network fetches.

python3 scripts/okf-graph.py graph sample-okf --focus agents/graph-engineer.md --hops 1
python3 scripts/okf-graph.py graph sample-okf --format html > docs/okf-graph.html

Typed edges come from Markdown links plus optional frontmatter links[].rel.

Resolving a concept argument

Every command taking a <concept> resolves it in tiers, most specific first:

1. Exact bundle-relative path (agents/graph-engineer.md)
2. File stem or frontmatter title (graph-engineer)
3. Path suffix (graph-engineer.md)

A tier matching more than one concept is ambiguous: the command prints every candidate and exits 1 rather than picking one.

$ python3 scripts/okf-graph.py impact sample-okf index
{"error": "ambiguous concept: index", "candidates": ["agents/index.md", "decisions/index.md", "index.md", ...]}

Full paths — what the skills pass — are never ambiguous. Shorthand that used to resolve by iteration order now errors instead, so pass the full path when a stem is shared across directories.

scripts/okf-ticket-link.py

Emit OKF TicketLink concepts from WikiTicket worklog items.

bin/worklog fold | python3 scripts/okf-ticket-link.py emit --bundle <bundle> --open-only
python3 scripts/okf-ticket-link.py emit --bundle <bundle> --id <ULID> --title "..." --github-issue N
python3 scripts/okf-ticket-link.py emit --bundle <bundle> --dry-run   # preview paths

Default GitHub project: SpillwaveSolutions/okf-plugin.

scripts/okf-curate.sh

Post-edit hook helper, wired to Write|Edit|MultiEdit in hooks/hooks.json. Takes a file path as $1, or reads the PostToolUse payload as JSON on stdin (.tool_input.file_path) — which is how Claude Code actually delivers it.

A Markdown extension (.md/.markdown) is the only pre-check; bundle membership decides the rest. It walks up from the edited file for the nearest ancestor holding an index.md containing okf_version, or a .okf/ directory with an index.md. That root is what gets curated, so a bundle rooted anywhere — not just .okf/, knowledge/ or sample-okf/ — is covered.

Finding no bundle root is a silent no-op: there is no fallback to the repo's own .okf/ or sample-okf/, so editing an unrelated Markdown file neither curates the wrong bundle nor prints anything.

Inside a bundle it runs okf validate (plus okf lint if available), okfcli validate, or — with no external CLI — okf-graph.py validate from this repo. Never fails the edit: every branch exits 0.

scripts/okf-curate.sh sample-okf/knowledge/tool-okf-graph-py.md

scripts/substack_okf.py

Maintainer-only integration harness, not part of the plugin's user-facing surface. It pulls a Substack archive, classifies posts, emits an OKF bundle into the gitignored integration/ tree, and verifies it with okf-graph.py. Useful for exercising the engine against a real corpus instead of sample-okf; nothing in the installed plugin calls it. python3 scripts/substack_okf.py --help for the subcommands.

Tests

python3 tests/test_okf_graph.py -q      # graph engine — 24 cases
bash tests/test_okf_curate.sh           # post-edit hook — 5 checks

Both are plain asserts: no test framework, no dependencies. They run in CI (alongside validate sample-okf --strict) and as a guarded pre-commit check.

test_okf_graph.py covers the engine and includes tripwires on sample-okf's concept and edge counts and on version consistency across the four manifests, so bumping a version in one place fails here.

test_okf_curate.sh covers the hook: a bundle rooted outside every legacy path fragment is still curated, a file in no bundle is silently skipped, the PostToolUse JSON payload on stdin works, malformed stdin is a no-op, and non-Markdown is rejected. Silent on success, loud and non-zero on failure.

bin/worklog (WikiTicket SDD)

Repo project management (not OKF-specific):

bin/worklog list
bin/worklog add "Title" --level task --kind feature --body "what and why"
bin/worklog update <ulid> --status in_progress
bin/worklog close <ulid> --status done --resolution "..."
bin/worklog roadmap-render
bin/worklog ia-index
bin/worklog sync          # needs WORKLOG_TICKET_* / adapters/github

See Worklog-Spec and upstream wiki_ticket_sdd.

Prefer official OKF CLI when present

okf validate <bundle>
okf graph <bundle>
# okfcli variants if installed as okfcli