accessflow: Skill for Claude Code

Implement a GitHub issue for AccessFlow

You are implementing a GitHub issue in the AccessFlow repo. CLAUDE.md is the authoritative rulebook — re-read it before writing code. This skill only adds a workflow on top.

Inputs

The user passes one of:

• An issue number: 42, AF-58, FE-10
• A full URL: https://github.com/bablsoft/accessflow/issues/42

Resolve the numeric issue with gh issue view <n> --json number,title,body,labels,assignees,url,state.

Project map

• Docs (authoritative design):
  • docs/01-overview.md — product scope, goals, non-goals
  • docs/02-architecture.md — system architecture and request flow
  • docs/03-data-model.md — entities, columns, enums, indexes
  • docs/04-api-spec.md — REST + WebSocket spec (update before adding endpoints)
  • docs/05-backend.md — proxy engine, workflow state machine, AI analyzer, scheduled jobs
  • docs/06-frontend.md — directory layout, routing, state management
  • docs/07-security.md — auth, authorization matrix, encryption rules
  • docs/08-notifications.md — event types, channel configs, signed payloads
  • docs/09-deployment.md — Docker Compose, Helm, env-var reference
  • docs/11-development.md — coding standards, testing strategy, Git workflow
  • docs/12-roadmap.md — milestone scope
  • docs/13-mcp.md — MCP server, @Tool callbacks, user API keys
  • docs/14-connectors.md — connector catalog, manifests, SHA-256 pins
  • docs/15-engine-sdk.md — host↔plugin contract, add-an-engine checklist
  • docs/16-iac.md — Terraform/OpenTofu provider, CI templates, composite Actions
  • docs/17-api-governance.md — API access governance (apigov)
  • docs/18-deployment-governance.md — deployment approval governance (deploygov)
  • docs/19-sql-review.md — deterministic SQL review rules (sqlreview)
  • docs/20-schema-change-governance.md — schema change governance (schemachange)
  • docs/21-aggregate-disclosure.md — aggregate disclosure guard (design, #943)
  • docs/22-service-accounts.md — service accounts / non-human identities (serviceaccounts, epic #867)
• Backend at backend/ — Java 25, Spring Boot 4, Spring Modulith. Modules under com.bablsoft.accessflow.{core,proxy,workflow,ai,security,notifications,audit}. Build: mvn verify (run from backend/ — there is no Maven wrapper).
• Frontend at frontend/ — React 19 + Vite + TS + Ant Design 6 + TanStack Query + Zustand. Build: npm run lint && npm run typecheck && npm run test:coverage && npm run build.
• End-to-end at e2e/ — Playwright suite with its own docker-compose.e2e.yml that builds backend + frontend from the working tree and seeds a deterministic admin via the bootstrap module. Owns auth and (over time) all critical user flows. Run: cd e2e && npm ci && npx playwright install --with-deps chromium && npm run stack:up && npm test.
• Website at website/ — public marketing site, static HTML/CSS/JS, no build step. Edits land directly in HTML.
  • website/index.html — landing page (pitch, supported databases, AI providers, auth methods, feature list, roadmap, quick-start commands, tech stack, docs chapter list, top-level URLs).
  • website/docs/index.html — public user documentation page (deployment instructions, configuration entities — Review Plans, AI configs, datasources, OAuth, SAML, SMTP, notification channels, user creation — RBAC role matrix, operator-facing env vars).
  • website/README.md — content-source map describing which app/docs/ sections each website section is derived from; keep in sync when adding new website sections.
• README at the repo root — public-facing project overview and quick start. Keep in sync when changes affect setup, tech stack, features, project structure, or top-level documentation.