Borda

Adapter over `codemap-py integrate` — audit, plan, source-wire, locally sync, and demonstrate the codemap-py integration with its supported consumers. Trigger with `/codemap-py:integration check|plan|apply|sync|demo [--runtime {claude,codex,both}] ...`. Default (no args) is `check`. Skip for: running a structural query (use `/codemap-py:query-code`); explicit standalone index rebuild (use `/codemap-py:scan-codebase`).

Scan the Python codebase and build a structural JSON index (import graph + blast-radius metrics). TRIGGER when: user asks to build, refresh, or rebuild the codemap index; user mentions stale index, missing symbols, or re-indexing after significant project changes; phrases: "build codemap", "scan codebase", "refresh structural index", "rebuild import graph".

Read local codemap telemetry logs and produce a diagnostic/usage report. Supports date filtering, session filtering, and optional anonymization before sharing. Trigger with `$codemap-py:debrief-coding [--since <YYYY-MM-DD>] [--session <id>] [--anonymize] [--output <path>]` to analyse recent codemap usage, debug query patterns, investigate errors, or prepare a shareable anonymized report of how codemap skills and the CLI are being used.

Adapter over `codemap-py integrate` — audit, plan, source-wire, locally sync, and demonstrate the codemap-py integration with its supported consumers. Trigger with `$codemap-py:integration check|plan|apply|sync|demo [--runtime {claude,codex,both}] ...`. Default (no args) is `check`. Skip for: running a structural query (use `$codemap-py:query-code`); explicit standalone index rebuild (use `$codemap-py:scan-codebase`).

Query the codemap structural index — module deps/rdeps/central/coupled/path, symbol-level source extraction, function call graph (fn-deps, fn-rdeps, fn-central, fn-blast), plus quality/coverage queries. Trigger with `$codemap-py:query-code <subcommand> ...` for: "what depends on", "who calls", "imports of", "dependency graph", "blast radius of", "list central modules". Skip for: rename intent (use `$codemap-py:rename-refs`); simple grep suffices; non-Python repo. Missing/stale index auto-builds — no manual scan-codebase needed.

Atomic rename of Python symbols or modules via the structural index — static callers, import sites, `__all__` re-exports, Sphinx cross-refs; optional deprecated alias (`--deprecate`) or hard-delete (`--remove-if-no-callers`). Trigger with `$codemap-py:rename-refs symbol <old> <new> [flags]` or `$codemap-py:rename-refs module <old_path> <new_path> [--dry-run]` for: "rename X to Y" (function/class/method/ module), "move module X to Y", "update all references to X". Skip for: non-Python; index not built (run `$codemap-py:scan-codebase` first); local-variable rename; grep-only rename wanted; 1:N symbol splits; package directory rename (use `git mv` directly).

Scan the Python codebase and build a structural JSON index (import graph + blast-radius metrics + symbol table). Explicit invocation only via `$codemap-py:scan-codebase [--root <path>] [--incremental]` — never auto-trigger this from conversation reasoning. Use when the index is missing, stale, or after significant project changes.

Identify which tests need rerunning after a code change — traces static call graph (function-level) or import graph (module-level) to find affected test files, then emits a ready-to-run pytest command. Trigger with `$codemap-py:test-impact <module::symbol | module> [--no-mocks]` for: "which tests are affected", "what tests cover this", "test impact of", "what tests to rerun".

Run an offline Sentinel package doctor and separate local installation defects from host enablement or Roboflow sign-in problems. TRIGGER when: the user asks to check, verify, diagnose, or troubleshoot a Sentinel plugin installation; run the setup doctor; find missing skills, packaged files, or Roboflow tools; or confirm Sentinel installed correctly. SKIP when: Sentinel and Roboflow work and the user wants to count boxes or solve a CV task; the package is healthy but OAuth/sign-in alone failed (auth-setup); or the request is deployment economics/crossover only (estimate-economics).

Turn an independently evaluated CV model or pipeline into a verified delivery handoff without copying volatile platform recipes. TRIGGER when: user has a working model, Workflow, OCR pipeline, or tracker and asks to export it, run locally, integrate an app/camera/RTSP source, deploy, productionize, monitor drift, add active learning, or make a runnable package. SKIP when: user asks to build a detector/model from sample images, the capability is unsolved, or measured acceptance is absent (solve-cv-task or modality skill); the request is cost/crossover only (estimate-economics); it asks only for a current Roboflow API field, UI path, model ID, or platform how-to (official Roboflow resource); or it only post-processes existing masks/data.

Connect or troubleshoot Sentinel's URL-only Roboflow MCP sign-in. TRIGGER when: the user asks to connect Roboflow, sign in, authorize OAuth, configure the plugin, or diagnose unavailable/unauthorized Roboflow MCP tools; the user asks whether a Roboflow API key is required for plugin installation. SKIP when: Roboflow MCP tools already work; the task is purely local, such as discussing a labeling approach for raw footage, and needs no Roboflow operation; a generated standalone client needs credentials (delegate its exact auth shape to the current official Roboflow API/inference skill).

Produce one whole-image verdict: pass/fail, category, compliance, or anomaly. TRIGGER when: user asks whether an image is defective/compliant; to flag bad parts, classify product images, run image-level quality control, detect an anomaly, or build binary/multi-class classification. SKIP when: user asks how many boxes/pallets or for other object counts or per-person PPE (detect-and-analyze); masks/area (segment-and-analyze); identity across video (track-and-count); OCR/codes (read-text); to compare self-hosting vs managed or cost only (estimate-economics); or delivery/export of a working classifier (deliver-cv-project).

Generate a portable stakeholder decision report for a CV deployment decision. TRIGGER when: user explicitly asks for a decision report, manager report, or stakeholder doc after a cost crossover has been computed; phrases: "write me a decision report", "generate a report for my manager", "I need a stakeholder doc", "produce the decision doc", "decision-report skill", "report for my team". SKIP when: no cost crossover exists yet — estimate-economics must run first and deliver a crossover number; user is still in build work; user wants a one-paragraph summary (answer inline instead).

Decompose a complex vision-and-reasoning requirement into the cheapest measurable pipeline. TRIGGER when: user asks to monitor/alert, analyze footage over time, combine perception with aggregation/reporting, determine whether something is feasible to detect (including sensor limits or smoldering), or replace repeated vision-language calls with a cheaper system. SKIP when: the request is single-frame detection/counting (detect-and-analyze), whole-image classification (classify-or-flag), deployment cost only (estimate-economics), or the pipeline is already working and needs delivery (deliver-cv-project).

Detect instances and analyze boxes, counts, crops, regions, or metadata. TRIGGER when: user asks to count/detect objects, report the number of defects, build a model that counts trucks, tally boxes/pallets on a conveyor, find workers lacking PPE, crop detections, extract an ROI, estimate box-relative size, or report per-object confidence/zone metadata. SKIP when: user needs one whole-image verdict (classify-or-flag); identity/path/dwell/line crossing (track-and-count); masks/contours/calibrated area/crack width (segment-and-analyze); OCR/serials (read-text); to compare self-hosting vs managed or cost only (estimate-economics); active learning/export/delivery of a working model (deliver-cv-project).

Estimate CV annotation, training, deployment, and operations economics. TRIGGER when: user invokes `$estimate-economics` or `/sentinel:estimate-economics`, asks labeling/training cost, managed vs self-hosted, build-vs-buy, scale economics, deployment crossover, or selects managed-at-scale after a passing proof. SKIP when: user asks to build/test a detector/classifier/OCR/tracker/pose/mask, count objects, finish the PoC, or keep improving because the eval has not passed yet (solve-cv-task); asks only a current platform how-to; or lacks passing evidence unless explicitly accepting a rough estimate.