Borrowing it
Nothing to install: this file belongs to wghglory/ngx-lift-workspace. 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/wghglory/ngx-lift-workspace/main/.cursor/skills/pr-review/SKILL.mdgit clone --depth 1 https://github.com/wghglory/ngx-lift-workspaceWrote 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/wghglory/ngx-lift-workspace/pr-review)<a href="https://agentmods.dev/skills/wghglory/ngx-lift-workspace/pr-review"><img src="https://agentmods.dev/badge/skills/wghglory/ngx-lift-workspace/pr-review/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/wghglory/ngx-lift-workspace/pr-review"><img src="https://agentmods.dev/badge/skills/wghglory/ngx-lift-workspace/pr-review.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.00056 | $0.00394 |
| Opus 5.5 | $0.00022 | $0.00158 |
| Sonnet 5.5 | $0.00011 | $0.00079 |
| Haiku 4.5 | $0.00006 | $0.00039 |
Grade A, and why
pr-review 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 16d 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.
What it actually says
Pre-PR Code Review
Reviews local changes or branch commits against workspace standards using the adversarial reviewer mindset.
Parameters
diff-target(optional): Git diff range to review (e.g.origin/main...HEAD). If omitted, defaults to all uncommitted and staged changes (HEAD).
Steps
1 — Fetch Changes
- If
diff-targetis provided:git diff <diff-target>andgit log <diff-target> --oneline - If omitted:
git status --porcelainandgit diff HEAD(Read full content of any untracked files with the Read tool).
2 — Adversarial Review
Activate the review-adversarial skill. Examine every changed line for:
- Signal reactive context violations and memory leaks
- Public API contract changes or broken TypeScript generics
- Untested code paths or shallow test assertions
- Modern Angular best practices (OnPush, modern control flow, signal inputs/outputs)
- Clarity Design System tokens and accessibility (
clr-lift)
Classify every finding:
- 🔴 Major: Bugs, memory leaks, broken contracts, missing critical tests, runtime crashes.
- 🟡 Minor: Non-blocking improvements, minor style consistency.
3 — Present Findings & Route Next Steps
- Present findings structured by file.
- If Major issues exist, recommend activating
pr-address-commentsto resolve them. - If no Major issues exist, recommend proceeding to
pr-create.
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.
- 16d ago First seen · 47 lines · 56 tokens per session scan A f949e9fe1c3e
pr-review is a skill published in the GitHub repository wghglory/ngx-lift-workspace (7 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 394 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-10-02.
Other skills, from other repositories
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.
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…