How do I install the Pp Pr Review skill?

Run npx skillmds@latest add polypoint/pp-pr-review 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 Pp Pr Review safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pp Pr 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 Pp Pr Review free to use?

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

Who published Pp Pr Review?

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

Pp Pr Review by polypoint — Agent Skill

Name: Pp Pr Review
Author: POLYPOINT

Pp Pr Review

Use when reviewing an Azure DevOps pull request through the complete POLYPOINT workflow: repository verification, JIRA PII redaction, parallel specialist reviews, developer-led triage, cross-cutting analysis, comment drafting, and explicitly approved posting. Trigger when the user supplies or refers to an Azure DevOps PR URL and asks for a PR or code review.

POLYPOINT Updated Sep 21, 2026

File contents

POLYPOINT PR review

Run the complete gated PR-review workflow. Treat the developer's decisions and the files under ./.pr-review/ as the authoritative run state.

Load the workflow

Read the shared orchestration workflow completely before starting. It is the authoritative sequence for both Claude Code and Codex. Follow every gate, artifact contract, triage rule, and token handling restriction in that file.

Apply these Codex mappings while following it:

Treat the PR URL in the user's prompt as the workflow's $1 argument. Ask for it only when none was supplied.
Use PLUGIN_ROOT for plugin-relative scripts. Codex also supplies CLAUDE_PLUGIN_ROOT for compatibility, so commands in the shared workflow can run unchanged.
Treat references to Claude's Agent tool or a general-purpose agent as instructions to delegate to a Codex sub-agent.
Explicitly name the required bundled skill in every delegated task and list its input and output files.
Launch the seven step-5 review agents concurrently when capacity permits. If fewer slots are available, keep the main conversation focused on orchestration and launch the remaining reviews as slots become available.
Do not perform specialist analysis in the main conversation merely because delegation is temporarily unavailable. Preserve the workflow boundary.
Use normal Codex user interaction for every STOP and approval gate. Never infer approval from earlier messages.

Posting safety

The bundled PreToolUse hook checks attempts to execute post-to-azure.sh. Codex requires the developer to review and trust the hook before it runs. Do not treat an untrusted, disabled, or unavailable hook as permission to weaken the workflow gate.

Run approve-post.sh only after the developer answers the final posting prompt with an unambiguous yes. The posting script consumes the approval marker before making Azure DevOps requests, so one approval authorizes one posting attempt.

Never call Azure DevOps posting endpoints directly or reproduce the posting script with raw shell commands.

---name: pp-pr-reviewdescription: Use when reviewing an Azure DevOps pull request through the complete POLYPOINT workflow: repository verification, JIRA PII redaction, parallel specialist reviews, developer-led triage, cross-cutting analysis, comment drafting, and explicitly approved posting. Trigger when the user supplies or refers to an Azure DevOps PR URL and asks for a PR or code review.---# POLYPOINT PR reviewRun the complete gated PR-review workflow. Treat the developer's decisions andthe files under `./.pr-review/` as the authoritative run state.## Load the workflowRead [the shared orchestration workflow](../../commands/pp-pr-review.md)completely before starting. It is the authoritative sequence for both ClaudeCode and Codex. Follow every gate, artifact contract, triage rule, and tokenhandling restriction in that file.Apply these Codex mappings while following it:- Treat the PR URL in the user's prompt as the workflow's `$1` argument. Ask for it only when none was supplied.- Use `PLUGIN_ROOT` for plugin-relative scripts. Codex also supplies `CLAUDE_PLUGIN_ROOT` for compatibility, so commands in the shared workflow can run unchanged.- Treat references to Claude's `Agent` tool or a `general-purpose` agent as instructions to delegate to a Codex sub-agent.- Explicitly name the required bundled skill in every delegated task and list its input and output files.- Launch the seven step-5 review agents concurrently when capacity permits. If fewer slots are available, keep the main conversation focused on orchestration and launch the remaining reviews as slots become available.- Do not perform specialist analysis in the main conversation merely because delegation is temporarily unavailable. Preserve the workflow boundary.- Use normal Codex user interaction for every `STOP` and approval gate. Never infer approval from earlier messages.## Posting safetyThe bundled `PreToolUse` hook checks attempts to execute`post-to-azure.sh`. Codex requires the developer to review and trust the hookbefore it runs. Do not treat an untrusted, disabled, or unavailable hook aspermission to weaken the workflow gate.Run `approve-post.sh` only after the developer answers the final posting promptwith an unambiguous yes. The posting script consumes the approval marker beforemaking Azure DevOps requests, so one approval authorizes one posting attempt.Never call Azure DevOps posting endpoints directly or reproduce the postingscript with raw shell commands.

Frequently asked questions