Borrowing it
Nothing to install: this file belongs to erraggy/oastools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/erraggy/oastools/main/.claude/skills/prereview/SKILL.mdgit clone --depth 1 https://github.com/erraggy/oastoolsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/erraggy/oastools/prereview)<a href="https://agentmods.dev/skills/erraggy/oastools/prereview"><img src="https://agentmods.dev/badge/skills/erraggy/oastools/prereview/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/erraggy/oastools/prereview"><img src="https://agentmods.dev/badge/skills/erraggy/oastools/prereview.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00054 | $0.01136 |
| Opus 5.5 | $0.00022 | $0.00454 |
| Sonnet 5.5 | $0.00011 | $0.00227 |
| Haiku 4.5 | $0.00005 | $0.00114 |
Grade A, and why
prereview scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
prereview
Review unpushed commits before pushing, using the same comprehensive analysis as PR reviews.
You are performing a pre-push code review. The user has commits ready to push but wants them reviewed first.
Step 0: Check for Uncommitted Changes
Before checking for unpushed commits, check if there are uncommitted changes that should be committed first:
# Check for staged or unstaged changes
git status --porcelain
If there are NO unpushed commits BUT there ARE uncommitted changes:
Use the AskUserQuestion tool to ask:
Question: "No unpushed commits found, but you have uncommitted changes. Would you like to commit them first?"
Options:
- Commit all changes - Stage all changes and create a commit (will prompt for message)
- Commit staged only - Commit just what's currently staged
- Cancel - Exit without reviewing
If the user chooses to commit:
- For "Commit all changes": Run
git add -Afirst - Use the Skill tool to invoke
commit-commands:committo create a proper conventional commit - After the commit succeeds, continue to Step 1
If there are NO unpushed commits AND NO uncommitted changes:
- Inform the user: "Nothing to review - no unpushed commits and no uncommitted changes."
- Exit the skill
Step 1: Identify Unpushed Changes
First, determine what needs to be reviewed:
# Get the current branch
git branch --show-current
# Check if there's an upstream tracking branch
git rev-parse --abbrev-ref @{upstream} 2>/dev/null || echo "NO_UPSTREAM"
# Show unpushed commits (if upstream exists)
git log @{upstream}..HEAD --oneline 2>/dev/null || git log origin/main..HEAD --oneline 2>/dev/null || git log origin/master..HEAD --oneline 2>/dev/null
Step 2: Get the Full Diff
Get the complete diff of all unpushed changes:
# Diff against upstream, falling back to origin/main or origin/master
git diff @{upstream}..HEAD 2>/dev/null || git diff origin/main..HEAD 2>/dev/null || git diff origin/master..HEAD 2>/dev/null
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 121 lines · 54 tokens per session scan A fababe35c22d
prereview is a skill published in the GitHub repository erraggy/oastools (6 stars, last pushed 9d ago), licensed MIT. It adds 54 tokens to every session and 1,136 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
critty
Review code changes or a document with Critty's terminal UI and address the reviewer's inline comments round by round. Use when the user or an approval workflow selects Critty; a generic review request does not count.
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
hero-diff-highlight
A dark code editor reveals a red deletion then a green addition with a soft pulse. Function: PR / code-change explainer.