How do I install the Self Review skill?

Run npx skillmds@latest add wordpress/self-review-3 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 Self Review 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 Self Review?

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 Self Review free to use?

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

Who published Self Review?

WordPress (@wordpress) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Self Review by wordpress — Agent Skill

Name: Self Review
Author: WordPress

Self Review

Review the current branch against this repo's architecture, security, performance, cross-platform and test-coverage rules before opening a PR. Use when the user asks to self-review, review my changes, check my branch before a PR, or says they are about to open a PR.

WordPress Updated Sep 21, 2026

File contents

Self-review

Run the repo's review standard against the working branch, before the PR exists.

Nothing runs this in CI. It is the only review a change gets before a human reads it, which is why it happens now rather than after: a finding fixed here costs one message, the same finding on the PR costs a review cycle.

Procedure

Read .github/instructions/code-review.instructions.md and follow it. It is the specification for this task, not background reading — it carries the procedure (establish the diff, run npm run lint and npm test, then the five dimensions) as well as the invariants and the reporting bar. Do not restate it here; run it.

That file is the single copy of the standard. It lives under .github/instructions/ so Copilot code review picks it up natively; every other agent, this one included, reaches it from here. Changes to how reviews work go there, not into this wrapper.

Two things this skill adds on top, both agent-neutral — apply whichever your agent can:

Run the judgement pass in a fresh context. The diff and the deterministic layer (npm run lint, npm test) run inline. The five dimensions should be reviewed by a context that did not write the change — a subagent, or a separate pass given only the diff and the instructions file. If the session that wrote the code also grades it, it reviews its own reasoning and finds it sound.

Report, don't apply. Surface findings in the chat. No GitHub comments, no files written — the PR does not exist yet. Then offer; the author decides what is a real finding.

Notes

This is the same skill as .claude/skills/self-review/, placed here because agents built on the Agent Skills open standard (Command Code and others) discover skills under .agents/skills/ rather than .claude/skills/. Both are thin wrappers over the one instructions file — neither is a second copy of the standard.
The repo-specific knowledge this adds over a generic review: Electron's bundled Node, the bundled Git binary, electron-store, loopback binding, the Windows spawn shims.
If a finding reveals a rule the instructions file does not yet cover, say so. It is meant to accumulate what the project learns.

---name: self-review-3description: Review the current branch against this repo's architecture, security, performance, cross-platform and test-coverage rules before opening a PR. Use when the user asks to self-review, review my changes, check my branch before a PR, or says they are about to open a PR.---# Self-reviewRun the repo's review standard against the working branch, **before** the PR exists.Nothing runs this in CI. It is the only review a change gets before a human reads it, which is why it happens now rather than after: a finding fixed here costs one message, the same finding on the PR costs a review cycle.## Procedure**Read [`.github/instructions/code-review.instructions.md`](../../../.github/instructions/code-review.instructions.md) and follow it.** It is the specification for this task, not background reading — it carries the procedure (establish the diff, run `npm run lint` and `npm test`, then the five dimensions) as well as the invariants and the reporting bar. Do not restate it here; run it.That file is the single copy of the standard. It lives under `.github/instructions/` so Copilot code review picks it up natively; every other agent, this one included, reaches it from here. Changes to how reviews work go there, not into this wrapper.Two things this skill adds on top, both agent-neutral — apply whichever your agent can:**Run the judgement pass in a fresh context.** The diff and the deterministic layer (`npm run lint`, `npm test`) run inline. The five dimensions should be reviewed by a context that did not write the change — a subagent, or a separate pass given only the diff and the instructions file. If the session that wrote the code also grades it, it reviews its own reasoning and finds it sound.**Report, don't apply.** Surface findings in the chat. No GitHub comments, no files written — the PR does not exist yet. Then offer; the author decides what is a real finding.## Notes- This is the same skill as [`.claude/skills/self-review/`](../../../.claude/skills/self-review/), placed here because agents built on the Agent Skills open standard (Command Code and others) discover skills under `.agents/skills/` rather than `.claude/skills/`. Both are thin wrappers over the one instructions file — neither is a second copy of the standard.- The repo-specific knowledge this adds over a generic review: Electron's bundled Node, the bundled Git binary, `electron-store`, loopback binding, the Windows spawn shims.- If a finding reveals a rule the instructions file does not yet cover, say so. It is meant to accumulate what the project learns.

Frequently asked questions