Use when reviewing Go code changes in remindb (modified or staged files in pkg/, cmd/, internal/, or any .go file in the diff) for adherence to the project's .claude/rules/go-concise.md. Catches project-specific style violations that generic Go reviewers miss — empty-struct-with-methods pattern, "failed to :" error…
Use when reviewing changes to remindb's public MCP surface — anything in pkg/mcp/, pkg/mcp/tools/, or pkg/mcp/server.go, especially new/renamed/removed Memory tools, changes to handler signatures, return shapes, locking decisions, or defer d.logCall(...) attrs. Validates against .claude/rules/mcp-tool-conventions.md…
Use when reviewing changes to remindb's SQL migrations — any new file under migrations/ matching 000N.sql, any edit to an already-committed migration file, or any change to pkg/store/queries.go that adds queries against columns/tables created by recent migrations. Checks IF NOT EXISTS coverage, append-only discipline…
Agent "2026-05-16-hermes-agent-self-evolution" from longbkit/clisbot, covering hermes agent self-evolution research, executive take, what is implemented vs planned, implemented in hermes-agent and implemented in hermes-agent-self-evolution.
Use this agent when reviewing code for Clean Architecture compliance. This includes evaluating dependency rules, layer separation, and architectural boundaries. Typically called as part of a code review process alongside other review agents.\n\nExamples:\n\n \nContext: User has just written or modified code in the…
Use this agent when you need to evaluate code changes against clean code principles and best practices. This agent analyzes code for readability, maintainability, and adherence to clean code standards across all categories including naming, functions, comments, formatting, error handling, and boundaries. It provides…
Use this agent when you need an opinionated, thorough code review of Rust code from a principal engineer perspective. This includes reviewing for design quality, functionality correctness, complexity management, test coverage, naming conventions, comments, style guide compliance, and overall code health. Particularly…
Combined analysis and planning agent for SIMPLE tasks. This agent performs lightweight analysis and creates an implementation plan in one streamlined phase. Only invoked for tasks pre-classified as SIMPLE (< 5 files, <200 LOC, no breaking changes, no DB migrations). Use this agent when you have a simple issue that…
Use this agent when you need to analyze and research issues, bugs, or enhancement requests. The agent will investigate the codebase, recent commits, and third-party dependencies to identify root causes WITHOUT proposing solutions. Ideal for initial issue triage, regression analysis, and documenting technical findings…
Use this agent when designing or implementing UI components for ccboard's web frontend (Leptos WASM). Specializes in Leptos reactive patterns, Rust-to-WASM UI, dark mode design, data visualization, and the ccboard design system. Examples: creating a new dashboard widget, implementing a chart component, designing a…
Use this agent when you need UX critique, information architecture analysis, or feature design validation for ccboard. Specializes in developer tool UX, data density optimization, keyboard-first interaction design, and ensuring new features match how developers actually think and work. Examples:\n\n \nContext: User…
Use this agent when designing or reviewing TUI (Terminal UI) components in ccboard using Ratatui. Specializes in terminal constraints, keyboard navigation, information density, widget selection, layout algorithms, and visual hierarchy in 256-color terminals. Examples: designing a new tab layout, choosing between…
Verbatim plan-to-beads converter using the bd CLI. Copies full implementation code, requirements, and exit criteria directly into each bead. Each bead is 100% self-contained - no plan back-references or external lookups needed.
Architectural Bug Investigation Agent. Deep investigation with line-by-line code analysis, produces fix plans with exact code changes, regression prevention, and verification criteria. Plans work with any executor (loop or swarm).