Nx is a tool for managing monorepos, which are repositories containing multiple related projects, across TypeScript and other languages. It helps development teams and AI agents run only affected tasks, cache build results, generate code, and coordinate continuous integration. The catalogue add-ons provide agent skills, commands, agents, instructions, and settings for working with Nx.
Borrowing it
Nothing to install: this file belongs to nrwl/nx. 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/nrwl/nx/master/.claude/skills/review-pending-pr-reviews/SKILL.mdgit clone --depth 1 https://github.com/nrwl/nxWrote 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/nrwl/nx/review-pending-pr-reviews)<a href="https://agentmods.dev/skills/nrwl/nx/review-pending-pr-reviews"><img src="https://agentmods.dev/badge/skills/nrwl/nx/review-pending-pr-reviews/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/nrwl/nx/review-pending-pr-reviews"><img src="https://agentmods.dev/badge/skills/nrwl/nx/review-pending-pr-reviews.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector pass
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.00093 | $0.04095 |
| Opus 5 | $0.00046 | $0.02048 |
| Sonnet 5 | $0.00019 | $0.00819 |
| Haiku 4.5 | $0.00009 | $0.00409 |
Grade A, and why
review-pending-pr-reviews 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 12d 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 — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Pending PR Reviews
The outbox for /review-pr. Nothing reaches GitHub until the maintainer approves it here.
This skill is where a human is guaranteed to be present. /review-pr runs headless most of the
time — review-prs drives it across tmux panes, and a cron runs it overnight — so its own Step 8.5
grill is skipped on the majority of reviews. This skill is therefore the real evaluation gate: it
grills the findings first (Step 3) and only then offers to post.
Configuration
TRIAGE_DIR— where drafts live. Default:~/.nx-pr-reviews, matching/review-pr's own default. Override with the same value if the maintainer has repointed it.
Do not read ~/.claude/triage/prs/. That is the store of the retired review-pr-deep pipeline.
Its drafts predate the current review criteria (pre-PIPELINE_VERSION tiers), so posting one would
publish findings the current calibrations would have dropped. If the maintainer wants those, they
must be re-reviewed by /review-pr, not posted from the old store.
Each draft has YAML frontmatter (pr, verdict, head_sha, pipeline_version, posted_at, ...)
and a ## Review draft section holding the body that will be posted.
A draft is pending iff posted_at: is empty. Once posted or discarded, posted_at is set and
the file is kept as the historical record — it feeds /review-pr's re-review dedup, so never delete
one.
1. Find pending drafts
ls $TRIAGE_DIR
Read each file's frontmatter; pending iff posted_at: is empty. Sort oldest-first by
last_reviewed_at so the longest-waiting review goes first.
For each, display: PR number and title, verdict, attempt, last_reviewed_at, URL, and the first
3 lines of ## Review draft.
2. Check for drift before presenting
gh pr view PR_NUMBER --repo nrwl/nx --json headRefOid,state,isDraft -q '{head: .headRefOid, state: .state, isDraft: .isDraft}'
IMPORTANT: every Bash command must be a single, standalone command. Do not chain with &&, ||, or
;, and do not append redirects or backgrounding — these break permission matching. Use separate
Bash calls.
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.
- 12d ago First seen · 330 lines · 93 tokens per session scan A 4db62b827672
review-pending-pr-reviews is a skill published in the GitHub repository nrwl/nx (29,320 stars, last pushed today), licensed MIT. It adds 93 tokens to every session and 4,095 once invoked, about $0.0005 per session on Opus 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-30.
Other skills, from other repositories
no-bare-casts
Writing as in TypeScript or TSX production code, modifying a file that contains a bare as cast, silencing a type error with a cast, encountering as unknown as, or reviewing a cast site.
compiler-verify
Use when you need to run all compiler checks (tests, lint, format) before committing. Detects whether TS or Rust code changed and runs the appropriate checks.
compiler-review
Review Rust port code for port fidelity, convention compliance, and error handling. Compares against the original TypeScript source.
typescript-react
Apply, review, and explain React conventions from the TypeScript Style Guide. Use automatically for TypeScript and TSX tasks involving prop-derived state, prop typing, component responsibilities, data flow, compound components, or client and server state.
typescript-style-guide
Apply, review, and explain the opinionated conventions in the TypeScript Style Guide. Use automatically only when TypeScript conventions are part of the requested task, including type modelling, discriminated unions, function APIs, variables and state, naming, source organization, React props, component APIs, state…
igniteui-react-components
This skill identifies the right Ignite UI for React components for any UI pattern and covers installing, importing, and using them — including JSX patterns, event handling, refs, forms, and TypeScript. Use this when choosing components, setting up a React project, writing component JSX, handling events, or integrating…