ワンクリックで
diagram-review
Run Triage-Saurus diagram review (screenshots, threat-model smells, and before/after report).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Run Triage-Saurus diagram review (screenshots, threat-model smells, and before/after report).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Trace a public endpoint through App Gateway, APIM, and AKS using harvested subscription data.
On-demand Playwright audit of a subscription's rendered React Flow diagrams - verifies the UI matches harvested Azure reality using screenshots, DOM checks, interaction tests, and diagram-to-asset comparison.
Promote validated learnings from a completed experiment — create detection rules, update strategy JSON, and update agent instructions for future experiments.
Validate generated architecture diagrams for hierarchy issues, missing internet ingress, network segmentation gaps, and missing components.
Generate per-resource-type cloud summaries (Key Vault, Storage Account, AKS, etc.) and persist them to the DB for the web app after triage completes.
Run two-phase repo context discovery — automated baseline (Phase 1) then intelligent code analysis (Phase 2) — to build architecture diagrams and inform scan scope.
| name | diagram-review |
| description | Run Triage-Saurus diagram review (screenshots, threat-model smells, and before/after report). |
Run the Triage-Saurus diagram review workflow for this repository.
Before running, verify:
curl -sf http://127.0.0.1:9000 > /dev/null || echo "Server not running"python3 -m playwright install chromiumIf the server is not running, instruct the user to start it (e.g. bash Scripts/start_web.sh) before proceeding.
Use the orchestrator script with sensible defaults:
python3 Scripts/Validate/review_generated_diagrams.py --base-url http://127.0.0.1:9000
| Flag | Purpose |
|---|---|
--repos <name...> | Limit to specific repo names |
--repo-at-a-time | Strict mode: retry each repo before continuing |
--skip-after-pass | Baseline-only run (no rule-apply + re-scan cycle) |
--only-unscanned | Target repos with no prior scan history |
--concurrency <N> | Parallel scan workers (default: 6) |
--scan-complete-timeout-sec <N> | Per-repo scan timeout in seconds (default: 600) |
--opengrep-timeout-sec <N> | OpenGrep validation timeout (default: 120) |
--audit-root <path> | Override output root (default: Output/Audit/) |
--headed | Show browser window (useful for debugging Playwright) |
For larger diagrams that exceed viewport size, the tool automatically:
This ensures that even complex, multi-panel diagrams with dozens of resources are fully captured and can be reviewed element-by-element.
The diagram review skill automatically detects and validates diagrams for multiple cloud and infrastructure providers:
For each provider, the review validates hierarchy, icon availability, and icon mappings to ensure diagrams render correctly with appropriate visual identity.
All artifacts are written under:
Output/Audit/DiagramReviewSkill_<timestamp>/
diagram_review_report.md ← main before/after report
baseline/ ← baseline pass summaries + multi-view screenshots
screenshots/ ← full set of panned/scrolled viewport captures
after/ ← after pass summaries + screenshots (unless --skip-after-pass)
screenshots/ ← full set of panned/scrolled viewport captures
After the run, report:
diagram_review_report.mddetection_rule_validation_failed > 0)The diagram review includes comprehensive validation for:
>, <, &br;, , etc.
These can cause rendering issues and are typically unintended encoding in diagram elements.<br> tags and other inline HTML that may not render properlyFor the element-level rationale, icon validation, hierarchy expectations, security posture checks,
and investigation checklist, follow the full guidance in Agents/DiagramReviewSkill.md.