Six read-only agents that explain a change and give it a second opinion. They are dispatched by impl-gh-issue at step 5b (and add-engine at step 13) before a change becomes a PR, and by review-gh-pr against a PR that already exists: af-reviewer and af-security-reviewer always run; the stack specialists run when their…
Frontend/e2e code specialist reviewer for an AccessFlow change. Reads the frontend/ and e2e/ portion of a branch cold and checks it against the frontend non-negotiables and the frontend-page / frontend-form / e2e-spec pattern checklists — strict types, t() i18n, TanStack Query, token handling, selector drift, test…
Backend/engine code specialist reviewer for an AccessFlow change. Reads the backend/ and engines/ portion of a branch cold and checks it against CLAUDE.md's backend rules and the backend/engine pattern checklists — Modulith boundaries, Java idioms, Flyway, scheduled jobs, the Security Rules, test parity. Returns…
Explains what an AccessFlow change actually does. Reads a branch or PR diff cold and returns a structured briefing — the one-paragraph what, the why, a per-area breakdown of the real changes, the interface surface it moves (endpoints, enums, migrations, config knobs, events), and where a reviewer should look hardest.…
Adversarial reviewer for an AccessFlow change. Reads a branch or diff cold and checks it against the .claude/patterns/ acceptance checklists, the fan-out completeness tables, CLAUDE.md's non-negotiables, and the "same commit set" drift rules — returning Blockers / Concerns / Nits with file:line evidence and a verdict.…
Security specialist reviewer for an AccessFlow change. Reads a branch or PR diff cold through a security lens only — proxy bypass, row-security failing open, self-approval and tenant scoping, credential handling, the auth surface, SSRF, audit tamper-evidence, plugin supply chain — and returns Blockers / Concerns /…
Runs AccessFlow's real quality gates against a working tree or branch and reports exactly what passed, what failed, and what was not checked. Maps the set of touched paths onto the gates that actually apply, so a docs-only change does not pay for a full Maven verify. Deliberately has no Edit or Write tool — it can…
Runs before the agent uses a tool for Write, Edit and Bash tool calls, executing flyway-guard.sh, backend-conventions.sh, frontend-conventions.sh, website-drift.sh, mvn-guard.sh and pre-commit-check.sh (6 commands). From bablsoft/accessflow.
4 yesterdayA
tokens not measured
originalApache-2.0
Add a new AccessFlow engine plugin under engines/ / — scaffold the Maven project and QueryEngine SPI implementation, pin the shaded JAR in connectors/ /connector.json, wire DbType + migration + credential gates + i18n + frontend registration + docs/website, and open a PR. Trigger when the user says "add a engine"…
Split a large AccessFlow working tree into a sequence of logical, individually-reviewable commits — proposing the groups, confirming each with the user, then staging and committing. Knows which file sets must never be split apart (an engine version bump and its connector pin, a DTO constraint and its form rule).…
Bring up, inspect, or tear down an AccessFlow local stack — the infra-only dev loop, the zero-config demo stack, one of the three e2e stacks, or the website. Handles the port collisions, tells you the seeded credentials, and never tears down a stack you did not name. Trigger when the user says "start the app", "run it…
Implement an AccessFlow GitHub issue end-to-end — fetch with gh, plan against docs/, follow CLAUDE.md conventions, update tests and docs, then open a PR. Trigger when the user says "implement issue.
Fan N genuinely independent AccessFlow jobs out to N sub-agents in one message, then consolidate. Use for work that repeats the same edit across disjoint files — the nine engine row-security appliers, one i18n key across seven locale files, a pattern file per area. Trigger when the user says "in parallel", "fan out"…
Prepare an AccessFlow release — verify every roadmap item is closed and documented, regenerate website screenshots, mark the milestone released in docs/website/README, then open a chore PR. Refuses to proceed when anything is missing. Trigger when the user says "prepare release vX.Y", "release prep for X.Y", or passes…
Review an existing AccessFlow pull request — check the head out into an isolated worktree, fan out the read-only agents (change summary, conventions, security, frontend, cross-cutting drift), explain what the PR actually does, then merge the findings into one numbered list and let you pick which ones to keep. Never…