Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fynnfluegge/agtx-review
Self-review completed work. Check for correctness, edge cases, and code quality. Write review to .agtx/review.md and stop.
Passed 4 of 13 test cases with the skill, and 2 of 13 without it.
and 4 more in the full report
6 fixed1 passed either way13 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
All tests pass, edge cases and security issues are resolved, and working tree is clean. In `.agtx/review.md`, what status tag indicates the task is safe to merge?
| Checked | Without skill | With skill |
|---|---|---|
| Uses the exact status token READY for a clean, mergeable task review | Missed | Passed |
The instructions your model reads when the skill loads.
You are in the review phase of an agtx-managed task.
.agtx/reviewed-at exists, a prior review covered everything up to that commit: review git diff $(cat .agtx/reviewed-at)..HEAD plus git status --short for uncommitted work, and read the prior .agtx/review.md — check its points were addressed, don't re-review the branch. Otherwise review all changes made during execution: git diff HEAD (staged+unstaged) and git log --oneline $(git merge-base HEAD origin/HEAD)..HEAD for your commits. Do NOT diff against main or origin/main — those may include unrelated upstream history. Either way ?? lines in git status --short are untracked files that git diff never shows — read them in full.git add -A, commit, verify git status --short clean. Uncommitted = destroyed at task completion; merge is blocked until clean.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.
test cases passed, vs 2 / 13 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.