Anti-false-positive verifier for Murmur. Use AFTER a change is written, to TRY TO BREAK it — run the real gates (cargo test --lib / ng build / ng lint), live-reproduce in a browser against the zoneless Angular app with a mocked Tauri IPC, and hunt for the failure modes this app has actually shipped (sealed-content…
Use as the cross-cutting AI/systems DESIGN authority to decide WHERE a seam goes across the Rust core, Angular FE, and brain — provider/model abstraction, agentic tool-use loop bounds, tool/ACI design, the egress-consent-redaction-ledger firewall, routing, context assembly, a new ingest source or consumption surface.…
Issues product owner. Validate implementation against feature catalog and feature/.md definitions; find gaps, stale docs, and missing happy paths. Suggest backlog ideas. Use when reviewing product completeness, catalog compliance, or prioritizing new capabilities.
Issues security auditor. Review code for authz, authn, injection, secrets, and XSS/CSRF risks; write a findings report and teach developers how to fix each issue via remediation tasks. Use for security audits — not for implementing patches. Prefer over generic review when the user asks for security issues or a full…
TDD Red phase for Issues. Create a failing test only — no production code. Use when starting TDD, adding behaviour, or user asks for a failing test first.
Triage and fix Mushi Mushi bug reports. Use when the user asks about bugs, bug reports, "what should I fix next", a specific Mushi report, or wants a fix for something users reported. Pulls the report, its AI diagnosis, and a paste-ready fix brief via the mushi MCP server, then implements the fix in this repo.
Implements Angular / TypeScript fixes and features in compliance with all materialized angular rules and pilot-angular skills. Takes an angular-reviewer finding (rule/skill ID + file:line) or a feature request, applies minimal targeted edits, verifies with tsc/ng build, and hands back a summary formatted for re-review…
Reviews an Angular component diff or file against all materialized angular rules and pilot-angular skills. Outputs structured findings with rule IDs, WCAG/OWASP references, severity, and fix guidance. Invoked automatically on angular diff review requests or manually via @angular-reviewer.
Use this agent when the user asks to "review code", "check my changes", "review uncommitted changes", "code review", "review before commit", "check for bugs", or when Claude detects scenarios involving local code review for .NET or Angular projects. This agent specializes in reviewing uncommitted git changes for bugs…
Upgrade path planning agent. Analyzes the full journey from current Angular version to the latest. Calculates steps, Node.js switches, estimated effort, and creates a complete upgrade roadmap. Triggers: "plan upgrade", "upgrade roadmap", "upgrade path", "how many steps", "what version am I on", "planner".
Pre-upgrade intelligence agent. Use BEFORE any Angular version upgrade to scan dependencies, detect breaking patterns, and report risks. This agent is READ-ONLY — it never modifies files. Triggers: "pre-upgrade", "audit deps", "check compatibility", "scout", "scan for breaking changes", "dependency check".
ON-DEMAND browser smoke testing using Playwright MCP. This agent is NOT part of the automatic upgrade pipeline. Use it manually when you want to visually verify the app works after an upgrade. Triggers: "test the ui", "browser test", "smoke test", "playwright test", "check if app works in browser", "visual check"…