Review local code changes for bugs, regressions, missing tests, and pragmatic improvements. Use when the user asks to review the current changes from `git status`, or to review a specific backlog task by id such as `task-65` or `TASK-65`. Also trigger when the user says things like "review", "review current changes", "check my changes", "look over the diff", or "review task-42".
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Review the current local changes or the implementation tied to a backlog task id and report concrete findings, not a changelog. Treat this as a code review unless the user explicitly asks for edits.
Resolve the review target.
If the prompt includes a backlog task id, locate the task markdown in backlog/tasks/ first, then backlog/completed/ if needed. Read the description, acceptance criteria, and referenced files. If no task id is given, start from git status --short and review the current local changes directly.
Build review scope from local context.
Check git status --short, inspect the diff for files related to the task, and read surrounding code where behavior is affected. Prefer rg and targeted git diff -- <path> over broad scans.
Review for defects and regressions. Prioritize:
Report findings first, ordered by severity. For each finding:
After findings, include:
If no findings are discovered, say that explicitly and mention residual risk or missing coverage.
Interpret prompts like review, review current changes, or review the changes from git status as a request to review the current working tree. Interpret prompts like task-56, review task-56, or review task-56 and report any issues/bugs or possible improvements as a review of the local changes associated with that task.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
The English summary is being prepared. Showing the original description.
Commit all changes, push to remote, and open a pull request in one go. Use when the user says "commit push pr", "ship it", "open a pr", or invokes /git-commit-push-pr.
The English summary is being prepared. Showing the original description.
Release a new version of the DevoxxGenie IntelliJ plugin — prompt for the target version, bump it in the build files, write a curated CHANGELOG.md entry and plugin.xml change-notes from the git/PR history since the last tag, build to verify, then commit, tag, and publish a matching GitHub release. Use this whenever the user wants to cut, ship, publish, or tag a new plugin release, bump the version for a release, or asks to "release vX.Y.Z" / "do a release" / "make a new version".
The English summary is being prepared. Showing the original description.
Create a feature branch for a backlog task, switch to it, and start implementation. Use when the user says "start task-123", "work on task-123", "implement task-123", or invokes /start-task with a task ID.
The English summary is being prepared. Showing the original description.