ruflo-adr

Reviewed at commit 13af5f1

Caution: Its skills pre-approve Bash and have Claude run the unpinned npm package @claude-flow/cli@latest through npx, so each new version runs without asking.

ADR lifecycle management — create, index, reconcile, supersede, check compliance, and link Architecture Decision Records to code via AgentDB hierarchical…

Made by
ruvnet
What we checked

Refuses Architecture Decision Record writes to ruflo memory that contain a key, token or password, and adds a local /adr-mod command (status, scan, format). Its skills create ADR files in docs/adr and run bundled scripts that read those files and store them in ruflo memory through the ruflo CLI. The hook itself makes no network calls and only writes a small status file in the project.

Review details

Static review of the source at the pinned commit; not run. Delta review of the changes since cd89db4; the rest carries over from the review at that commit. One module (hooks/register.ts) registers session.start (registers /adr-mod via $.command.register, writes .claude-flow/adr-mod/status.json in the project root with call and block counters via $.fs.write), tool.call (guard on by default through userConfig guard; only inspects memory_store into an adr* namespace, agentdb_hierarchical-store with an adr namespace or mem:ADR key, and agentdb_causal-edge between ADR ids; returns deny when the shared secret screen finds a secret shape or an input too large to screen, never rewrites) and command.run for /adr-mod (answered locally, no model call). No fetch, no $.process, no file reads in the hook. The skills adr-create, adr-index, adr-reindex, adr-review and adr-verify declare allowed-tools with unrestricted Bash, and three tell Claude to run node scripts import.mjs, verify.mjs and reindex.mjs. Those scripts read markdown under docs/adr and docs/adrs in the project (skipping node_modules, .git, .claude, .brain and similar) and spawn ruflo memory store, list and purge in the project directory. They first use an already built @claude-flow/cli next to the plugin or a ruflo or claude-flow executable on an absolute PATH entry (no shell, project-relative PATH entries skipped); only when none is found do they fall back to npx @claude-flow/cli@latest, which resolves the latest version from the npm registry, which is the normal case for a marketplace install. reindex.mjs hard-purges the adr-patterns and adr-edges namespaces before rebuilding them, as documented. The adr-architect agent prompt also suggests npx @claude-flow/cli@latest commands but pre-approves nothing. The @claude-flow/cli package and the ruflo-core MCP server the skills call were not reviewed. The .codex-plugin manifest, hooks/codex-hooks.json, codex.ts and the prebuilt codex-hook.cjs are only for OpenAI Codex and are not loaded by Claude Code; they were not reviewed in depth. Changed in this version: only plugin.json gained a repository URL field (github.com/ruvnet/ruflo); no code, skill or prompt changed. No other hosts, no eval, no obfuscation in the Claude Code parts.

What it uses
  • Reads your prompts: no
  • Sees tool calls: yes
  • Blocks or changes tool calls: yes
  • Reads or writes files: yes
  • Runs programs on your machine: yes
  • Calls the model (uses tokens): no
  • Sends data over the network: no
  • Stores data: yes
  • Shows something on screen: yes
Hooked events

ADR lifecycle management — create, index, reconcile, supersede, check compliance, and link Architecture Decision Records to code via AgentDB hierarchical store + causal edges (supersedes/amends/depends-on/related)

Made this mod? Add a badge to your README

modsforClaude badge for ruflo-adr

Paste this into your README. The badge says reviewed once the current version has been reviewed, and links readers to this page.

[![Listed on modsforClaude](https://modsforclaude.com/badge/ruflo-adr.svg)](https://modsforclaude.com/mods/ruflo-adr/)

← All mods