argos

Visualize a Notion AI Meeting Notes page as an argos argument graph. Use this when the user wants to extract Issues/Claims/Arguments from a Notion meeting page and view it as a graph, typing patterns like "/argos <URL>" or "visualize this notion meeting" with a notion.so URL.

Review code changes (staged diff or recent commit) for architectural drift in argos. Use after significant changes or before merging to detect: (1) module boundary violations beyond what tests/architecture catches mechanically, (2) inappropriate responsibility crossing, (3) naming convention deviations, (4) emerging anti-patterns. Trigger phrases include "/architecture-review", "アーキテクチャレビュー", "境界違反していないか確認", "設計的に大丈夫か".

Review code changes (staged diff or recent commit) for implementation-level concerns — logic correctness, edge cases, test gaps, security risks, performance hot spots — that biome/tsc/architecture-test cannot catch. Use as the last Inferential Feedback gate before merge. Trigger phrases include "/code-review", "コードレビュー", "ロジック確認", "PR レビュー".

Run all argos quality sensors in fast-fail order (TypeScript → Biome → Vitest → Playwright) and report a concise summary. Use this before committing, after non-trivial edits, or when verifying that recent changes haven't regressed. Trigger phrases include "/quality-check", "全体チェック", "regression 確認", "前のコミット前にチェック".