forge-dev

Senior architecture reviewer — evaluates system designs, architectural decisions, scalability, integration, and evolution paths. USE WHEN reviewing an ADR, assessing a proposed architecture change, evaluating service boundaries, or challenging a technology choice.

Senior code reviewer covering correctness, security, performance, maintainability, and test quality across TypeScript, Python, Rust, Go, and SQL. USE WHEN reviewing a diff, before merging a PR/MR, assessing code quality, or surfacing security and performance risks in recent changes.

Senior error and log forensic analyst — correlates distributed failures, uncovers root causes, and maps cascades. USE WHEN diagnosing a production incident, correlating errors across services, analyzing cascading failures, or mining log patterns for hidden root causes.

Senior refactoring specialist — transforms complex code into maintainable systems while preserving behavior. USE WHEN refactoring legacy code, reducing complexity, breaking apart god classes, extracting methods, or planning a safe multi-step refactor.

Defensive programming principles for robust systems — input validation, error boundaries, fail-safe defaults, invariant checking. USE WHEN writing production code, designing APIs, handling external input, or reviewing error handling.

Decide how to integrate completed work — merge, PR, or cleanup — once implementation is done and tests pass. USE WHEN implementation is complete and tests pass, deciding merge strategy, or cleaning up a feature branch.

Inspect failing GitHub Actions checks via gh, pull logs, summarize root cause, and propose a fix plan. USE WHEN a GitHub PR has failing CI checks, debugging GitHub Actions failures, or triaging CI breakage before merging.

Fix issues end-to-end — triage, diagnose, branch, fix, PR/MR, close. Supports GitHub (gh) and GitLab (glab) with cross-repo fixes and submodule bumps. USE WHEN fix issue, github issue, gitlab issue, bug report, fix bug, resolve issue, triage issue, gh issue, fix

Run tests and systematically fix all failing tests using smart error grouping. USE WHEN tests are failing, user asks to fix failing tests, CI reports test failures, or a test suite run leaves failures.