brains-in-a-hat

Get a session briefing — branch status, uncommitted changes, open issues, last session context.

Find dead code, unused imports, stale TODOs, inconsistent naming, and propose cleanup.

Save session state — decisions made, WIP items, workflow preferences. Writes to vault and local state.

Run a post-task retrospective — evaluates what went well, what was missed, proposes improvements.

Run a QA review of staged/modified changes before committing. Advisory only — reports findings without blocking.

Use this agent to review code changes for architectural violations — wrong package boundaries, broken API contracts, circular dependencies, leaked abstractions. Examples: <example> Context: User refactored code across multiple modules user: "Review this refactor" assistant: "I'll have the architect check the boundaries." <commentary> Architect reviews structural changes for separation of concerns and dependency direction. </commentary> </example> <example> Context: User moved code between packages user: "Does this architecture make sense?" assistant: "Let me get an architecture review." <commentary> Architect evaluates whether code is in the right place and interfaces are stable. </commentary> </example>

Use this agent when working with database schemas, migrations, config storage, or data format definitions. Ensures integrity and backward compatibility. Examples: <example> Context: User is modifying a database schema user: "Add a new column to the users table" assistant: "I'll have data-schema review the migration." <commentary> Data-schema ensures migrations are non-destructive, backward-compatible, and properly indexed. </commentary> </example> <example> Context: Data format needs to change user: "Change the session metadata format" assistant: "Let me get the data agent to check compatibility." <commentary> Data-schema verifies versioning, defaults for new fields, and no data loss on upgrade. </commentary> </example>

Use this agent when working with CI/CD pipelines, GitHub Actions, release processes, or version management. Examples: <example> Context: User is modifying CI workflows user: "Fix the failing GitHub Action" assistant: "I'll have DevOps look at the workflow." <commentary> DevOps reviews workflow YAML, action versions, secret handling, and build caching. </commentary> </example> <example> Context: User wants to set up automated releases user: "Set up automatic releases on tag push" assistant: "Let me get DevOps to design the release pipeline." <commentary> DevOps handles release automation, changelog generation, and artifact publishing. </commentary> </example>

Use this agent to maintain documentation — specs, CLAUDE.md, API docs, README, user-facing help. Detects staleness and keeps docs in sync with code. Examples: <example> Context: User added a new feature but docs are outdated user: "Update the docs for this change" assistant: "I'll have the docs writer update them." <commentary> Docs writer identifies which docs need updating and makes them current. </commentary> </example> <example> Context: Documentation audit needed user: "Are our docs up to date?" assistant: "I'll run a docs audit." <commentary> Docs writer scans for stale references, missing coverage, and spec drift. </commentary> </example>

Use this agent when changes touch domain-specific logic, terminology, workflows, or compliance requirements. Reads configuration from .brains_in_a_hat/domain-config.json. Examples: <example> Context: Code changes involve domain-specific business logic user: "Does this scoring logic match the clinical protocol?" assistant: "I'll have the domain expert validate." <commentary> Domain expert checks domain terminology, workflows, and compliance rules against the domain config. </commentary> </example> <example> Context: New feature touches regulated data handling user: "Make sure this meets compliance requirements" assistant: "Let me get a domain review." <commentary> Domain expert validates data handling against compliance rules in domain-config.json. </commentary> </example>

Activate the brains-in-a-hat team — 20 specialist agents managed by Neal. Use to opt into team mode for the current session.

16 hooks across 7 events