gap-analyzer

CLI Gap Analyzer

Produce a structured gap report comparing a CLI's documented API surface against its implemented commands.

Where this skill runs:

• /cli-anything-web:refine — mandatory first step. The refine command invokes this skill before reading or changing anything else; the gap report drives which endpoints get implemented.
• standards skill — optional pre-review scan (endpoint coverage there is otherwise handled by the traffic-fidelity-reviewer agent).
• Standalone coverage analysis on request.

Evidence rule: the captured-vs-implemented diff must cite its sources — each reported gap references the endpoint entry in <APP>.md (the documented surface) and, when available, traffic-capture/traffic-analysis.json (the analyzer's detected endpoint inventory), plus raw-traffic.json hit counts for priority. A gap with no citation in either file is a guess, not a finding.

---

Inputs

You need the path to an existing CLI's agent-harness directory:

• {APP_PATH}/agent-harness/ — the CLI root
• {app} — the app name (e.g., reddit, hackernews)

Evidence files (read all that exist):

• {APP_PATH}/agent-harness/{APP_UPPER}.md — documented API map (required)
• {APP_PATH}/traffic-capture/traffic-analysis.json — detected endpoints/protocol
• {APP_PATH}/traffic-capture/raw-traffic.json — hit counts for priority scoring

Step 0: Deterministic First Pass (devkit)

Run the mechanical layer diff first — it AST-parses the client and command modules and cross-references traffic-analysis.json, so you only spend judgment on what it can't decide:

cli-web-devkit gaps {app}     # or: PYTHONPATH=devkit python -m cli_web_devkit gaps {app}

The JSON report gives unimplemented_endpoints (captured but absent from client.py) and unexposed_methods (client methods no command calls). Treat these as candidate gaps to verify in Steps 1–3, not as final answers — the string-level endpoint matching is intentionally conservative.