Gptme review
Claude Code skills for gptme — /gptme:run, /gptme:review, /gptme:context
npx -y skills add gptme/gptme-cc-plugin --skill gptme-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Run a multi-lens code review via gptme on the current git diff or a specific file. Use when the user invokes /gptme:review or asks for a gptme-style parallel code review. Do NOT use when a simple in-session review suffices.
SKILL.md
2.0 KB, 462 tokens by cl100k_base, as published. Nobody here has run it
gptme:review
Delegate code review to gptme, which runs independent correctness, security, and test-coverage passes on your current changes.
When to Use
- User invokes
/gptme:review - User wants a second opinion or multi-lens review on the current diff
- Current changes are non-trivial and a systematic bug-finding pass adds value
When Not to Use
- Diff is tiny/mechanical (config change, typo fix)
- User just wants a quick summary, not a structured review
gptmenot in PATH
Procedure
# Review current staged+unstaged diff
DIFF=$(git diff HEAD)
if [ -z "$DIFF" ]; then
DIFF=$(git diff --cached)
fi
if [ -z "$DIFF" ]; then
echo "No changes to review (git diff HEAD is empty)"
exit 0
fi
gptme --non-interactive \
"Review the following code changes. Run three passes: (1) correctness — logic bugs, broken invariants; (2) security — unsafe input handling, secret leakage; (3) test coverage — missing regression tests, unverified edge cases. For each finding include: file, line, severity (high/medium/low), and a concrete fix hint. Output findings as a markdown list ordered by severity." \
- \
"$DIFF"
Review a specific file
gptme --non-interactive \
"Review this file for bugs, security issues, and missing test coverage. Output findings as a markdown list ordered by severity." \
- \
"$(cat path/to/file.py)"
Tips
- The
--non-interactiveflag is required for non-blocking execution - For large diffs, consider reviewing one file at a time
- gptme's review is independent of this Claude Code session — it won't share your prior context
Related
- gptme docs
/gptme:run— delegate arbitrary tasks to gptme/gptme:context— inject gptme lessons into this session
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.