Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    WordPress Plugin PR Review Gate

    1

    **WordPress Plugin PR Review Gate** is a specialized AI agent skill that reviews **what changed in your WordPress plugin** and tells you whether the PR is ready to merge.

    $15

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    WordPress Plugin PR Review Gate

    WordPress Plugin PR Review Gate

    Example session with this skill installed

    Use the WordPress Plugin PR Review Gate skill to review the supplied PR diff for a plugin called Demo Portal.

    The PR changes a client-request REST API endpoint, updates a WordPress save-post callback, and modifies approval notification handling.

    The plugin must preserve these requirements:

    • Private client requests must only be accessible to authorized users.
    • WordPress save hooks must execute without PHP errors.
    • Approval notifications must only trigger after successful persistence.

    Please

    1. Identify confirmed regressions introduced by the PR.
    2. Provide severity, file locations, and supporting evidence.
    3. Explain the impact and recommend the smallest appropriate fix.
    4. Suggest regression tests for each issue.
    5. Give a final merge recommendation: BLOCK, CHANGES REQUESTED, PASS WITH NOTES, PASS, or INSUFFICIENT CONTEXT.

    Do not modify files or execute commands.

    • Read your context and instructions
    • Compiled the wordpress plugin pr

    Merge recommendation: BLOCK

    Review Summary

    Reviewed the supplied WordPress plugin PR against its base revision.

    3 confirmed regressions identified:

    • 2 High severity
    • 1 Medium severity

    The changes introduce a client-data exposure risk, a WordPress hook argument error, and an approval notification consistency issue.

    Findings

    SeverityLocationIssue
    🔴 Highincludes/api.phpPublic REST endpoint exposes private client requests
    🔴 Highincludes/hooks.phpIncorrect callback argument configuration causes PHP errors
    🟠 Mediumincludes/approval.phpApproval notification triggers before successful persistence

    PRG-01 — High: Private Client Data Exposure

    Evidence: The PR changes the REST route's permission_callback to __return_true and removes the client-specific database query restriction.

    Impact: Unauthenticated visitors may retrieve request information belonging to multiple clients.

    Recommended fix: Restore meaningful endpoint authorization and scope records using the authenticated user's server-derived client identity.

    Regression test: Create requests for Client A and Client B. Verify unauthenticated access is denied and each authenticated client only receives authorized records.

    PRG-02 — High: WordPress Hook Argument Error

    Evidence: The updated save callback requires two parameters, but its add_action() registration only passes one.

    Impact: Saving a request can trigger a PHP argument-count error, interrupting the operation.

    Recommended fix: Align the callback signature and hook registration using the correct accepted_args value.

    Regression test: Save a synthetic request through the actual WordPress hook and verify the callback completes successfully.

    PRG-03 — Medium: Premature Approval Notification

    Evidence: The notification action executes before the status persistence operation confirms success.

    Impact: A client may receive an approval notification even when the approval status was not saved.

    Recommended fix: Trigger the notification only after the required state changes have been persisted successfully.

    Regression test: Simulate a failed status update and verify no approval notification is triggered.


    Final Recommendation

    BLOCK — Do not merge this PR yet.

    All three confirmed regressions should be corrected before merging.

    After applying the fixes

    1. Add the suggested regression tests.
    2. Verify the affected WordPress hooks and REST permissions.
    3. Re-run the PR Review Gate on the updated diff.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    WordPress Plugin PR Review Gate

    Review smarter. Catch regressions before they become releases.

    A WordPress plugin pull request can look straightforward and still introduce a serious problem: an AJAX permission regression, a callback signature that causes a fatal error, a data migration that skips existing installations, or a status update that triggers incorrect notifications.

    WordPress Plugin PR Review Gate is a specialized AI agent skill that reviews what changed in your WordPress plugin and tells you whether the PR is ready to merge.

    Rather than dumping a generic security checklist, the skill traces affected code paths, compares behavior against the base revision, checks existing callers and tests, and reports only supported, actionable findings.


    What It Reviews

    🔍 Changes introduced by the PR

    • Changed PHP functions, helpers, classes and callbacks
    • Effects on existing callers and downstream behavior
    • Unexpected changes to plugin business logic
    • Regressions that are new or newly exposed by the PR
    • Accurate references to changed files and lines when available

    🔐 Security and WordPress permissions

    • REST API permission_callback and object-level access
    • AJAX and admin-post.php request authorization
    • Nonces versus real capabilities and ownership checks
    • Validation, escaping, redirects and sensitive data exposure
    • Private file and client-data access regressions

    ⚙️ WordPress-specific integration

    • add_action() / add_filter() callback signatures and accepted arguments
    • Custom post type hooks, save handlers and reentrancy
    • Plugin startup, activation and upgrade paths
    • WordPress cron jobs, caches and side effects
    • Compatible use of supported WordPress and PHP APIs

    🗃️ Data and backward compatibility

    • Modified options, post meta, user meta and custom tables
    • Missing migrations for existing plugin installations
    • Data-loss or duplication risks introduced by changed code
    • Public integration contracts, REST response shapes and hook consumers
    • Plugin versions and release metadata when relevant to the PR

    🧪 Testing gaps

    • Existing tests that no longer cover the changed behavior
    • Missing regression tests for confirmed issues
    • Focused Arrange / Act / Assert test suggestions
    • Accurate distinction between tests executed, inspected, and proposed

    A Clear PR Review Decision

    Every review concludes with one advisory recommendation:

    GateMeaning
    BLOCKA confirmed serious regression should be corrected before merging.
    CHANGES REQUESTEDA confirmed medium-impact defect needs a fix.
    PASS WITH NOTESNo confirmed blockers, but meaningful limitations or follow-ups remain.
    PASSNo confirmed defects found in adequately reviewed changed paths.
    INSUFFICIENT CONTEXTThe available diff or source is insufficient for a defensible review.

    Important: This is an AI review recommendation, not an automated GitHub status check, branch-protection rule or merge action.


    What You Receive

    For each confirmed issue, your agent provides:

    1. Severity and the affected changed location
    2. Code evidence showing why the behavior is wrong
    3. Preconditions and failure sequence that make the defect reachable
    4. Why this PR introduced it, rather than a generic pre-existing concern
    5. Smallest practical fix to preserve the PR's purpose
    6. Focused regression test to keep the defect from returning

    Potential concerns with missing evidence are labeled Needs verification, not presented as proven vulnerabilities.


    What's Included

    • Complete SKILL.md review workflow and merge gate rules
    • Differential review and call-chain tracing guide
    • WordPress-specific permission, hook and compatibility checks
    • Data integrity, schema and upgrade review guide
    • Severity calibration and regression test guidance
    • Copy-ready PR review report template
    • An explicitly fictional worked example

    No scripts, live website access or external services are required. The skill reviews source files and diffs read-only by default.


    Who It's For

    WordPress plugin developers reviewing their own feature branches and pull requests.

    Freelancers and agencies validating custom plugin work before a client release.

    Plugin maintainers checking compatibility with existing WordPress installations and integrations.

    AI-assisted developers who want a reliable, WordPress-focused PR review procedure instead of a generic “review this code” request.


    How to Use

    1. Load the skill in a compatible AI coding agent connected to your authorized repository, or provide the PR diff and relevant source files.
    2. Ask your agent to apply WordPress Plugin PR Review Gate to the change.
    3. Review the advisory merge decision and evidence-backed findings.
    4. Fix verified defects, add regression tests, and repeat the review.

    Example request:

    Review this WordPress plugin PR against its base revision. Check introduced security, data, callback, REST/AJAX, PHP compatibility and migration regressions. Give a merge recommendation and only actionable findings with changed-line evidence and targeted tests. Do not edit files or execute commands.


    Focused on PR Quality, Not Noise

    This skill is intentionally change-focused. It does not try to replace a full WordPress security audit, an approval workflow integrity audit, a release-readiness certification, or your CI pipeline.

    It does not automatically inspect inaccessible private repositories, execute test suites, post GitHub comments, approve pull requests, or merge code. The agent needs access to the relevant diff and authorized source files. Conclusions should be validated by a developer; no AI review guarantees the absence of defects.

    Make WordPress pull-request reviews more consistent, specific and useful—before the merge button gets clicked.


    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Code Quality & Review.

    Static, read-only PR review by default. Requires access to a real diff or base/head source plus relevant project context. Gate decisions are advisory and do not create GitHub status checks, enforce CI rules, comment on PRs, or merge branches. Tests are suggested rather than automatically executed. Reviews may miss issues or produce false positives; findings require developer validation. Optimized for WordPress plugins and changed-code regressions, not full security certification or general PHP code auditing.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 day ago

    Nothing to install. It runs in your AI agent.

    Optional
    GitHub

    Read repository/diff metadata: Optional, only if a connected read-only Git provider is available and authorized.

    Permissions

    Read Files
    Listed1 day ago

    What's inside

    Frequently Asked Questions

    No. The “gate” is a structured merge recommendation reported to the user. It does not configure branch protection, change PR status, or merge anything.

    Yes, with an Agensi-compatible agent that can load the skill and read your authorized WordPress plugin diff and files. The available file and Git tools depend on your agent setup.

    Yes, if the buyer's agent is already authorized to access the repository or the buyer supplies a relevant patch. This skill does not grant repository access by itself.

    No. It recommends fixes and regression tests. It does not edit files or execute tests by default.

    No. This skill reviews **PR-introduced issues** across code, compatibility, hooks, data and tests. A dedicated security audit can investigate the full plugin more deeply.

    No AI review guarantees that. The quality depends on the patch, surrounding source, documented behavior and agent capabilities. Treat the result as one input to a sound review and testing process.

    New in Code Quality & Review