Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From ce
Reviews git changes or branch diffs with code-reviewer agent, creates issue checklists on failures, and fixes them interactively if requested.
npx claudepluginhub rileyhilliard/claude-essentials --plugin ceHow this command is triggered — by the user, by Claude, or both
Slash command
/ce:review [instructions]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
Invoke the ce:code-reviewer agent to perform a comprehensive code review.
**If `$ARGUMENTS` is provided:**
- Use the instructions from the user.
**If `$ARGUMENTS` is empty:**
Steps:
1. Check git status to see if there are uncommitted changes
2. Check current branch name
3. Determine what to review:
- If uncommitted changes exist: Review uncommitted changes
- If no uncommitted changes exist:
- Check if on a feature branch (not main/master/develop)
- Suggest reviewing all changes in current branch against main (or upstream branch)
- Check the changed files via `git d.../reviewPerforms on-demand code review of uncommitted changes, git diff ranges, files, or branches, producing a report on spec compliance and code quality.
/reviewReviews staged changes or recent commits across five axes—correctness, readability, architecture, security, performance—producing categorized findings with file:line references and fixes.
/reviewRuns Codex code review on local git state (working tree or vs base branch). Supports --wait/--background, --base <ref>, --scope auto|working-tree|branch.
/reviewPerforms an enhanced multi-LLM code review using multiple providers (Codex, Gemini, Claude) and posts inline PR comments. Designed as escalation path beyond standard /review.
/reviewReviews HTML file for design anti-patterns, principles violations, and accessibility issues. Generates markdown report with status tables and recommendations.
/reviewReviews specified code scope via four specialists (quality, security, performance, architecture), producing summary, detailed findings, refactoring suggestions, prioritized action plan.
Share bugs, ideas, or general feedback.
Invoke the ce:code-reviewer agent to perform a comprehensive code review.
If $ARGUMENTS is provided:
If $ARGUMENTS is empty:
Steps:
git diff --name-only $([ "$(git rev-parse --abbrev-ref HEAD)" = "main" ] && echo "HEAD^" || echo "main...HEAD")After the code-reviewer agent completes:
If APPROVE: Report the review summary. Done.
If REQUEST CHANGES:
a. Extract all Critical and Important issues into a checklist:
Review Findings - [branch/scope]:
- [ ] [CRITICAL] file.ts:123 - Description
- [ ] [IMPORTANT] file.ts:456 - Description
b. Ask the user how to proceed using AskUserQuestion:
c. If fixing: work through the checklist, marking items complete as resolved. After all targeted items are fixed, re-run the code-reviewer agent to verify the fixes don't introduce new issues.