agentlogbooks

Hotspot-first, multi-pass code review for pull requests, branches, pasted diffs, and work-in- progress changes. Models behavior changes, selects risky hotspots, acquires minimal local context, generates candidate findings and questions, runs a skeptic pass and dedup, then surfaces at most 5 high-signal outputs. Persists a per-run JSONL trace and per-PR SQLite ledger under ./.logbooks/code-review/.

Validates test quality beyond coverage: uses Claude subagents to generate intelligent mutations for source code, runs them via the project's native test runner (pytest, jest, vitest, mocha, go test), prints a structured summary, generates mutation-todos.md with per-mutant rationale, persists every run to a per-project SQLite ledger and JSONL trace under ./.logbooks/mutation-testing/, and warns whe

Use when the user needs ideas or a name — brainstorming, naming, developing an idea further, hybridizing ideas, stress-testing candidates, reframing a problem, or picking a final direction. Ideas persist in a per-topic logbook across sessions.

Design and create a logbook — a shared, queryable, schema-stable working surface that agents and humans append to, annotate, and query across sessions. Invoke when the user explicitly wants to track structured entries across multiple sessions or multiple contributors (e.g. "I want to track X across sessions", "I need a draft layer before committing to Jira", "let me review what the agent found bef