MCP PR Review Pipeline
Developer Official v1.0.16Multi-agent pull request review via GitHub MCP — security, quality, and style agents with a human gate before posting
by skrptiq
Sign in to import this skrpt into your workspace.
Sign inWhat's included 13 nodes
MCP PR Review Pipeline
Multi-agent PR review: fetch via MCP, three parallel review agents, human gate, post via MCP
PR Data Fetch
Retrieves pull request metadata, diff, and changed files from GitHub via MCP
Quality Review
Evaluates code quality — logic, architecture, testing, error handling, and maintainability
Review Gate
Human gate — pauses for you to review findings before posting to GitHub
Review Posting
Posts the approved review to GitHub via MCP — summary comment, inline comments, and verdict
Security Review
Scans changed files for security vulnerabilities, credential exposure, and unsafe patterns
Style Review
Checks code style, naming conventions, formatting, and project-specific patterns
Fetch PR Data
Retrieves and structures pull request data from GitHub via MCP
Post Review
Formats and posts the approved review to GitHub via MCP
Quality Analysis
Evaluates code quality — logic, architecture, testing, and maintainability
Review Gate Summary
Synthesises findings from all review agents into a human-readable gate summary
Security Analysis
Analyses PR diff for security vulnerabilities and credential exposure
Style Analysis
Checks code style, naming, formatting, and project-specific conventions
Requirements 2 services, 1 permission, 1 data type
- LLM Service
- GitHub (MCP)
- network:github.com
- source code
Security Passed
Detected
- Services: github-mcp, llm-service
- Permissions:
- Data Handling:
Version history 14 releases
GH#844 — migrate the gate step from node-meta (`metadata.gate: true` in the skill) to the canonical execution-entry `gate: true` on the workflow step. Single source of truth; the engine + app read the execution entry. No behaviour change — `IsGate` is identical.
GH#833 — drop the embedded `github-mcp` service node; dep-reference the canonical `_shared/github-mcp@1.0.0`. This bundle was the source of the canonical content (current API). contents.services 1→0.
GH#745 — declare per-step `output: {name, type}` on every execution step (pr_data/text, security_review/text, quality_review/text, style_review/text, gate_decision/decision, posted_review/text). Lights up the #744 rich flow-map. Content-only; no bindings or logic changes.
Fix-forward after Row 3b v1.0.12 publish failure. The v1.0.12 per-skrpt CI's "Register version with Hub API" step failed because the consumer's source `manifest.id` (9de9f1f1…) did not match the D1 catalogue row's id (946666b0…) — a legacy drift from before Action 6 (`0bcc5ae0`) made publish-skrpt.mjs Step 2 INSERT use `manifest.id` for the D1 id column. v1.0.13 reconciles the source `manifest.id` to the catalogue authoritative value (Row-5-equivalent for consumers) and republishes. Per Adj-1: no re-tag of v1.0.12; the orphaned GitHub release artefact stays inert (no D1 versions row, no consumer pinned it).
Wave 2: re-signed with canonical engine signing pipeline.
Signature fix — RELEASE_NOTES.md now included in integrity checksum.
Initial catalogue release with full structural and content-quality validation. All scanner checks pass.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
More from Developer
View all →Customer Support Flow
Classifies customer intent and drafts appropriate responses
Onboarding Setup Pipeline
Generates personalized onboarding materials and interview questions
Webapp Testing Pipeline
Plan test cases, write and execute tests, report failures, and fix issues in an automated cycle