/agtx-review
Self-review completed work. Check for correctness, edge cases, and code quality. Write review to .agtx/review.md and stop.
$ npx -y skills add fynnfluegge/agtx --skill agtx-review --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/agtx-review
Context preview
The summary Claude sees to decide when to auto-load this skill.
Self-review completed work. Check for correctness, edge cases, and code quality. Write review to .agtx/review.md and stop.
SKILL.md
agtx-review.SKILL.mdname: agtx-review description: Self-review completed work. Check for correctness, edge cases, and code quality. Write review to .agtx/review.md and stop.
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.
The blackboard for coding agents - Add tasks. Press one key. An orchestrator agent picks it up, plans, and delegates to multiple coding agents running in parallel. Come back to changes ready to merge.
Other skills on agtx.
- /benchmark
Run SWE-bench Lite benchmarks against agtx coding agent workflows. Guides setup, configuration, execution, evaluation, and reporting.
Open skill - /agtx-execute
Execute an approved implementation plan. Implement the changes, then write a summary to .agtx/execute.md and stop.
Open skill - /agtx-plan
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.
Open skill - /agtx-research
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.
Open skill - /brainstorm
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.
Open skill - /sweep
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.
Open skill