How do I install the Cr Node skill?

Run npx skillmds@latest add tomevault-io/cr-node in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Cr Node safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cr Node?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cr Node free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cr Node?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cr Node by tomevault-io — Agent Skill

Name: Cr Node
Author: tomevault-io

Cr Node

Run a 7-pass Node.js code review scoped to the current PR diff. Use when reviewing pull requests for Node.js/Express/Fastify backends, checking code before merge, or when the user asks for a Node.js code review. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

CR-Node — Diff-Scoped Node.js Review

Review scope: PR diff + directly affected files only.

Follow the review criteria defined in rules/node.md.

Step 1 — Detect project context

Read package.json and check for:

express dependency → enable Express-specific middleware checks
fastify → enable Fastify plugin checks
koa → enable Koa middleware checks
typescript or tsconfig.json → skip checks covered by TS compiler
prisma, @prisma/client → enable Prisma-specific query checks
sequelize → enable Sequelize raw query checks
typeorm → enable TypeORM query builder checks
mongoose → enable Mongoose-specific checks

Step 2 — Get PR context

Run these commands sequentially (no nested substitution):

gh pr view --json number,title,body,baseRefName,headRefName,url — store the baseRefName value
git diff <baseRefName>...HEAD — using the baseRefName from step 1
git diff --name-only <baseRefName>...HEAD — changed files list

Step 3 — Expand affected scope

For each changed file, identify direct consumers (files that import/require from it) to catch breakage from interface changes. Only expand one level deep — do not crawl the entire dependency graph.

Step 4 — Run review passes

Apply all 7 review passes and filtering rules from the criteria file against the diff and affected files.

Step 5 — Output findings

Collect all findings with this format per issue:

### [SEVERITY] Pass N — file:line

**Issue:** one-line description
**Why:** reason you're confident this is a real issue
**Fix:** suggested code change

If no issues found: "✅ No issues found — all 7 review passes came back clean."

Show the user the findings.

Step 6 — Autofix

Follow the autofix workflow defined in rules/autofix.md.

Local mode: present the three options (create findings file as cr-node-findings.md, fix step by step, fix all)
CI mode: post findings as PR comments with /fix and /fix-all reply instructions
Do not flag issues that are clearly intentional based on git blame context.
Run everything autonomously without asking to confirm each step (except the autofix choice in local mode).

Source: enpitech/ai-tools — distributed by TomeVault.

---name: cr-nodedescription: Run a 7-pass Node.js code review scoped to the current PR diff. Use when reviewing pull requests for Node.js/Express/Fastify backends, checking code before merge, or when the user asks for a Node.js code review. Use when this capability is needed.---# CR-Node — Diff-Scoped Node.js ReviewReview scope: **PR diff + directly affected files only.**Follow the review criteria defined in `rules/node.md`.## Step 1 — Detect project contextRead `package.json` and check for:- `express` dependency → enable Express-specific middleware checks- `fastify` → enable Fastify plugin checks- `koa` → enable Koa middleware checks- `typescript` or `tsconfig.json` → skip checks covered by TS compiler- `prisma`, `@prisma/client` → enable Prisma-specific query checks- `sequelize` → enable Sequelize raw query checks- `typeorm` → enable TypeORM query builder checks- `mongoose` → enable Mongoose-specific checks## Step 2 — Get PR contextRun these commands sequentially (no nested substitution):1. `gh pr view --json number,title,body,baseRefName,headRefName,url` — store the `baseRefName` value2. `git diff <baseRefName>...HEAD` — using the baseRefName from step 13. `git diff --name-only <baseRefName>...HEAD` — changed files list## Step 3 — Expand affected scopeFor each changed file, identify direct consumers (files that import/require from it) to catch breakage from interface changes. Only expand one level deep — do not crawl the entire dependency graph.## Step 4 — Run review passesApply all 7 review passes and filtering rules from the criteria file against the diff and affected files.## Step 5 — Output findingsCollect all findings with this format per issue:```### [SEVERITY] Pass N — file:line**Issue:** one-line description**Why:** reason you're confident this is a real issue**Fix:** suggested code change```If no issues found: "✅ No issues found — all 7 review passes came back clean."Show the user the findings.## Step 6 — AutofixFollow the autofix workflow defined in `rules/autofix.md`.- **Local mode**: present the three options (create findings file as `cr-node-findings.md`, fix step by step, fix all)- **CI mode**: post findings as PR comments with `/fix` and `/fix-all` reply instructions- Do not flag issues that are clearly intentional based on git blame context.- Run everything autonomously without asking to confirm each step (except the autofix choice in local mode).---> Source: [enpitech/ai-tools](https://github.com/enpitech/ai-tools) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions