ce

Create a well-formatted git commit for current changes

Audit and upgrade project dependencies

Execute an implementation plan from the plans folder

Explain code in detail with examples

Fix a GitHub issue by number

Expert at comprehensive code review for merge requests and pull requests from technical, product, and DX perspectives. Use this agent when the user has completed work on a feature branch and needs review before merging. Analyzes all changes between branches, evaluates user impact, assesses developer experience, enforces project standards, and provides structured feedback organized by severity.

Use this agent when you want someone to poke holes in a plan, design, or idea before committing. Examples: <example> Context: User has a plan they want validated user: "Here's my plan for the new caching layer. What's wrong with it?" assistant: "I'll look for real flaws, risks, and unstated assumptions." <commentary> User wants rigorous critique. This agent looks harder for problems than a typical reviewer, but only raises genuine issues. </commentary> </example> <example> Context: User is considering a major decision user: "We're thinking of switching to DuckDB. Play devil's advocate." assistant: "I'll examine this critically and surface any real concerns." <commentary> User wants thorough scrutiny before committing. The goal is catching genuine issues, not arguing against the decision. </commentary> </example> <example> Context: User wants to find gaps in a spec user: "Review this spec and tell me what I'm missing" assistant: "I'll identify gaps, edge cases, and unstated assumptions." <commentary> Finding what's missing requires assuming something IS missing and looking for it. </commentary> </example>

Lightweight Haiku agent for delegated tasks. Receives detailed instructions from commands like /ce:commit, /ce:test, and /ce:pr. Not typically invoked directly by users.

Specialist at efficiently reading and analyzing large log files using targeted search and filtering. Optimized to avoid loading entire logs into context by using grep-style workflows, time and severity filters, and iterative refinement across arbitrary log formats.

Guides clean, scalable system architecture during the build phase. Use when designing modules, defining boundaries, structuring projects, managing dependencies, or preventing tight coupling and brittleness as systems grow.

Fixes flaky tests by replacing arbitrary timeouts with condition polling. Use when tests fail intermittently, have setTimeout delays, or involve async operations that need proper wait conditions.

Best practices for writing Claude Code skills, rules, and CLAUDE.md instructions. Use when creating SKILL.md files, authoring .claude/rules, writing CLAUDE.md project or user instructions, or configuring Claude behavior for a project or team.

Enforces precise, minimal design for dashboards and admin interfaces. Use when building SaaS UIs, data-heavy interfaces, or any product needing Jony Ive-level craft.

Create or improve documentation by routing to the right approach. Handles code comments (inline audit/cleanup), system docs (READMEs, API docs, architecture), and templates. Use when writing, auditing, or improving any form of documentation.

2 hooks across 2 events