dash-audit ยท diff
git:20260308.40d253c to git:20260512.e9ef1cf
18 added, 4 removed. Audit A to A.
---
name: dash-audit
description: Audit Dash apps for callback hazards, state flow risks, layout and accessibility issues, and Dash-specific UX regressions. Use when the user asks for a Dash callback review, Dash UI audit, Dash web-interface audit, or a read-first remediation plan for a Dash app. Do not use for generic React or Next.js UI review.
---
# Dash Audit
Use this skill for read-first Dash audits. It owns Dash callback review, Dash UI/state review, and prioritized remediation guidance.
## Workflow
1. Read the repo `AGENTS.md`.
2. Run `/home/bjorn/.codex/skill-support/bin/ui-audit-preflight dash-callback-map --cwd <repo> --out <json>`.
- 3. Read only the Dash references you need:
+ 3. When machine-readable evidence is useful, adapt the callback map into the
+ shared contract:
+ `python3 <skill_root>/scripts/dash_ui_audit_adapter.py --input <json> --pretty`.
+ 4. Read only the Dash references you need:
- `references/dash-callbacks.md` for callback graph and state hazards.
- `references/dash-ui.md` for layout, responsiveness, accessibility, and interaction review.
- 4. Inspect only the files surfaced by the preflight plus any directly implicated layout, component, or callback modules.
- 5. Report grouped findings with the highest-risk callback and regression issues first.
- 6. If the user asks for fixes, keep remediation scoped and verify the affected path with repo-native commands.
+ 5. Inspect only the files surfaced by the preflight plus any directly implicated layout, component, or callback modules.
+ 6. Report grouped findings with the highest-risk callback and regression issues first.
+ 7. If the user asks for fixes, keep remediation scoped and verify the affected path with repo-native commands.
## Use When
- The task is a Dash callback audit.
- The task is a Dash web UI, state, or layout review.
- The user wants a read-first remediation plan for a Dash app.
## Do Not Use When
- The task is a general web or Next.js UI audit.
- The task is platform architecture with no Dash review need.
- The task is only backend, dependency, or docs work.
## Outputs
- executive summary
- grouped findings by category and file
- prioritized fixes
- callback graph or regression-risk notes when useful
- scorecard or risk summary when useful
+
+ ## UI Audit Contract
+
+ Use `ui_audit.v1` for structured Dash findings. The adapter treats callback map
+ rows as `observations` and emits actionable `findings` only when the preflight
+ evidence indicates a likely callback registration issue, such as a callback
+ decorator with no detected `Output`.
+
+ Keep absolute repository roots redacted as `<scan-root>` in shared evidence.
+ Use the full JSON locally; paste only the specific redacted findings needed for
+ review comments or issue updates.