agtx-review
Self-review completed work. Check for correctness, edge cases, and code quality. Write review to .agtx/review.md and stop.
git clone --depth 1 https://github.com/fynnfluegge/agtx /tmp/agtx-review && cp -r /tmp/agtx-review/plugins/agtx-terse/skills/agtx-review ~/.claude/skills/agtx-reviewSKILL.md
# Review Phase You are in the **review phase** of an agtx-managed task. ## Instructions 1. Review all changes made during execution: run `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. 2. Check for: - Correctness and edge cases - Error handling - Code style consistency with the existing codebase - Test coverage - Security issues (injection, XSS, etc.) 3. Fix any issues you find ## Output Write your review to `.agtx/review.md` in the **current working directory** with these sections: ## Review Findings from your review — what looks good, what was fixed, any concerns. ## Status Either `READY` (good to merge) or `NEEDS_WORK` (with explanation of remaining issues). ## CRITICAL: Stop After Writing After writing `.agtx/review.md` (in the current working directory): - Say: "Review written to `.agtx/review.md`." - Wait for further instructions ## Output Style Terse. No pleasantries. Fragments OK. Short synonyms. Code exact. Status updates: one line. Pattern: [what] [why]. Done.
Integrate a spec-driven/skill framework as a bundled agtx plugin. Pass a GitHub repo URL to auto-generate the plugin.toml, or run without arguments to write one from scratch.
Run SWE-bench Lite benchmarks against agtx coding agent workflows. Guides setup, configuration, execution, evaluation, and reporting.
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.
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.
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.