agtx-review

Featured

Self-review completed work. Check for correctness, edge cases, and code quality. Write review to .agtx/review.md and stop.

Code & Development 1,305 stars 117 forks Updated 1 weeks ago Apache-2.0

Install

View on GitHub

Quality Score: 89/100

Stars 20%
100
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
59
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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.

Details

Author
fynnfluegge
Repository
fynnfluegge/agtx
Created
6 months ago
Last Updated
1 weeks ago
Language
Rust
License
Apache-2.0

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category