Use this agent when the user wants to triage, investigate, or diagnose a bug report, crash, or error — typically referenced via a Bugsnag link, stack trace, error message, or user-reported issue. The agent traces the error through the codebase to identify root causes and suggest fixes.\n\nExamples:\n\n- user: "/triage…
Use this agent when bumping a dependency or evaluating the impact of a library update. It traces which modules depend on the library, checks for breaking API changes, identifies affected code paths, and suggests targeted test runs. Examples: user: "what's the impact of bumping compose to 1.12?" assistant: "I'll…
Use this agent when the user wants to create a new feature module, shared module, or library module in the project. The agent generates the full skeleton: build.gradle.kts, package structure, entry-point files, navigation registration, and settings.gradle.kts inclusion. Examples: user: "create a new feature module for…
Use this agent to review a pull request for code quality, architectural consistency, and potential issues. It understands the project's patterns (CompositionLocal injection, MVI/MVVM, convention plugins, proto model boundaries) and flags anti-patterns. Examples: user: "review this PR" or "review #123" assistant: "I'll…
Use this agent after fetching updated protobuf definitions (e.g., after /fetch-protos) to trace the impact of proto changes through the codebase: generated code → API wrappers → services → repositories → controllers → features. Examples: user: "what changed in the protos and what needs updating?" assistant: "I'll…
Use this agent to identify untested code and generate test stubs. Given a changed file, feature module, or area of the codebase, it finds what lacks test coverage and scaffolds tests following the project's established patterns. Examples: user: "what's untested in the cash feature?" assistant: "I'll analyze the cash…