quick-review

Review code changes from the current commit or branch

Use this agent to review a plan before implementation begins. This agent catches complexity, scope creep, and over-engineering before any code is written.

description: Use this agent when you have just committed code and need a thorough review of your changes. This agent should be called after running `git commit` to review either the specific commit or the entire branch/PR. You decide which suggestions to implement based on their merit and relevance. Examples: <example> Context: User requests a feature for meeting creators to cancel their meetings. user: "I want meeting creators to be able to cancel meetings. Show a confirmation before actually deleting." user: "yes let's add a cancel button" <function call to git commit omitted> assistant: "Let me use the code-reviewer agent to review this commit." <commentary> Since a commit was just made, use the code-reviewer agent to review the changes before moving on. </commentary> </example> <example> Context: User wants an unconference-style grid view for the conference schedule. user: "I want a grid showing meeting spots as columns and time slots as rows, so people can see what's happening across all locations" user: "clicking an empty cell should let you create an event there" user: "yes, each conferenceMeetingSpot is a location" <function call to git commit omitted> assistant: "I'll use the code-reviewer agent to review the entire branch against main." <commentary> The user wants a comprehensive review of all changes on the branch, so launch the code-reviewer agent to analyze the full diff. </commentary> </example> <example> Context: User asks to make meetings editable after creation. user: "meeting creators should be able to edit their meetings - title, time, description, all the fields" user: "inline editing in the MeetingCard would be nice, not a separate page" <function call to git commit omitted> assistant: "Let me use the code-reviewer agent to review this." <commentary> Proactively calling the code-reviewer after a significant commit to catch potential issues. </commentary> </example>

This skill should be used when the user asks to "brainstorm", "find ideas", "explore approaches", or explicitly wants multiple perspectives on a problem before deciding.

Use this skill when the current branch has merge conflicts that need to be resolved.

Use this skill when you want to install something (npm / uv / brew / `x.sh | bash` / ...), or when the user asks to install

Tips for starting new projects with good technology stacks

Use this skill when the user wants to find and work on a GitHub issue.

16 hooks across 4 events