mit einem Klick
agtx-review
// Self-review completed work. Check for correctness, edge cases, and code quality. Write review to .agtx/review.md and stop.
// Self-review completed work. Check for correctness, edge cases, and code quality. Write review to .agtx/review.md and stop.
Execute an approved implementation plan. Implement the changes, then write a summary to .agtx/execute.md and stop.
Plan a task implementation. Analyze the codebase, create a detailed plan, write it to .agtx/plan.md, then stop and wait for user approval before making any changes.
Explore the codebase to understand a task before planning. Write findings to .agtx/research.md and stop. This is a read-only exploration — do not modify any files.
Sweep this conversation into agtx tasks and push them to the kanban board. Use when the user wants to capture, decompose, or hand off conversation results to the agtx board.
Enter brainstorm mode to explore a feature or enhancement idea. Stays in discussion mode only — no planning, no implementation. Use /agtx:sweep when ready to push outcomes to the board.
| name | agtx-review |
| description | Self-review completed work. Check for correctness, edge cases, and code quality. Write review to .agtx/review.md and stop. |
You are in the review phase of an agtx-managed task.
git diff HEAD (staged+unstaged) and git log --oneline $(git merge-base HEAD origin/HEAD)..HEAD to see only your commits. Do NOT diff against main or origin/main — those may include unrelated upstream history.Write your review to .agtx/review.md in the current working directory with these sections:
Findings from your review — what looks good, what was fixed, any concerns.
Either READY (good to merge) or NEEDS_WORK (with explanation of remaining issues).
After writing .agtx/review.md (in the current working directory):
.agtx/review.md."Terse. No pleasantries. Fragments OK. Short synonyms. Code exact. Status updates: one line. Pattern: [what] [why]. Done.