luiseiman/dotforge
7 subagents
Subagent
architectDelegate for architecture decisions, design tradeoff analysis, dependency evaluation, and pattern validation. Use before implementation when the approach isn't clear or when touching system boundariescode-reviewerPROACTIVELY use after code changes to review for security, performance, correctness, and maintainability. Reads diffs, analyzes patterns, reports issues by severity. Does not modify code.implementerDelegate to this agent for focused code implementation tasks. Use after research/architecture phases are complete. Handles writing code, running tests, fixing lint errors, and verifying changes compilresearcherPROACTIVELY delegate to this agent for any task requiring exploration, reading multiple files, searching logs, or gathering context before implementation. Use when the main thread would fill with verbsecurity-auditorDelegate for security-focused analysis: scanning for secrets, vulnerabilities, auth gaps, dependency risks, and compliance issues. Use before any deployment or when touching auth/crypto/data-handling session-reviewerAnalyze conversation patterns to detect recurring frustrations, corrections, and problematic tool usage. Feeds findings into practices/inbox/ or CLAUDE_ERRORS.md. Use after long sessions or when /forgtest-runnerDelegate for writing new tests, running test suites, analyzing failures, and reporting coverage. Use after implementation to validate changes or when investigating test failures.