← ClaudeAtlas

api-flow-maplisted

Map API request flows and review what a branch or PR changes. Scans API repositories (Spring MVC/WebFlux, JAX-RS, Express/Koa/Fastify/NestJS/Next.js, Flask/FastAPI/Django REST, Go net-http/gin/echo/chi/gorilla, ASP.NET Core, OpenAPI specs, serverless.yml/SAM) and produces per-endpoint flows in plain English (validation, auth, DB reads/writes, outbound HTTP, queue publishes, conditions, status codes), then diffs them against a base branch with risk scoring and a self-contained HTML review view plus a Markdown PR comment. Use whenever someone asks what an API does, wants endpoint documentation or a flow diagram, needs to review an API pull request or branch, asks what changed in an API between branches or commits, wants a CI gate for risky API changes, or wants to check OpenAPI spec vs implementation drift.
Soulful-Iris/api-flow-map · ★ 0 · API & Backend · score 65
Install: claude install-skill Soulful-Iris/api-flow-map
# api-flow-map Turns an API codebase into endpoint flows a reviewer can read in a minute, and turns a branch into a change review: which endpoints changed, what steps were added/removed/modified, which conditions or status codes moved, and how risky that is. Deterministic Python (stdlib only, PyYAML optional), no network, no build required, read-only on the repo. ## Quick start The tooling is bundled with this skill: `scripts/apiflow.py` sits next to this SKILL.md (in a Claude Code plugin install that is `${CLAUDE_PLUGIN_ROOT}/skills/api-flow-map/scripts`). ```bash S=<directory containing this SKILL.md>/scripts python3 $S/apiflow.py doctor <repo> # what will be detected python3 $S/apiflow.py scan <repo> -o <out> # flow-map.html / .md / .json python3 $S/apiflow.py diff <repo> --base origin/main -o <out> # flow-diff.html / .md / .json (PR review) python3 $S/apiflow.py explain <out>/flow-diff.json --changed-only # outline with step ids, for annotations python3 $S/apiflow.py render <out>/flow-diff.json --annotations ann.json -o <out> ``` Write outputs under the user's workspace (e.g. `apiflow-out/` inside the repo, or the outputs folder); the HTML is a single file with no external assets — attach it to the PR or open it locally. ## Workflow A — review a PR / branch (primary use) 1. **Diff.** Run `apiflow.py diff <repo> --base <base>`. The base defaults to `origin/HEAD`, then `main`/`master`/`develop`.