- Home
- Skills
- Code Quality & Review
- WordPress Approval Workflow Integrity Audit
Works with the AI Agents you already use
WordPress Approval Workflow Integrity Audit
Find broken approval transitions, overwritten decision history, stale-response races, revision mismatches, and misleading notifications in WordPress client workflows. Evidence-led code review with specific fixes and regression tests.
$19
WordPress Approval Workflow Integrity Audit
Example session with this skill installed
Apply WordPress Approval Workflow Integrity Audit to the synthetic approval functions in
examples/synthetic-case.md. The contract requires append-only client decision history and notifications only after successful persistence. Review a reopen-and-resubmit cycle and status-write failure. Do not run code or change files.
- Read your context and instructions
- Compiled the wordpress approval workflow
Scope: Two synthetic helper functions from the packaged example. Static source inspection, no WordPress runtime or tests executed.
Contract: Open request → decision (approved / rejected / blocked / changes requested); staff may reopen; each accepted decision appends a history entry; notices follow successful persistence.
Findings: 2 confirmed.
| Severity | Issue | Evidence | Impact |
|---|---|---|---|
| High | Decision history overwritten | _example_history replaced with a one-element array in example_record_response() | Earlier approvals disappear after reopen and resubmit |
| Medium | Notification sent before persistence | do_action('example_decision_notification', ...) runs before update_post_meta() | Email/hook may announce a decision that failed to save |
WI-01 — History loss: First, a client approves. Staff reopens the request. The client next requests changes. Instead of preserving both decisions, the handler stores only the latest one.
Fix: Append a durable history event rather than replacing the history array.
Regression: Approve → reopen → changes requested; assert two intact response records with correct actors and notes.
WI-02 — Premature notification: A status write fails but the notification hook has already fired.
Fix: Dispatch after a successful state/history persistence boundary; use durable dispatch if stronger guarantees are required.
Regression: Mock failed status persistence and assert no notification is requested.
Verification limits: This is a synthetic code example. It does not demonstrate a vulnerability or bug in an actual WordPress plugin. No integration tests or email deliveries were performed.
Connects securely to your tools. The creator never sees your data.
About this skill
WordPress Approval Workflow Integrity Audit
Stop lost approvals, broken status changes, and misleading activity histories before they reach your clients.
A client clicks Approve. The status changes. But did the plugin actually preserve what was approved, by whom, and when?
An approval plugin can pass a basic security review and still lose earlier decisions, accept stale forms, mismatch document revisions, or send a notification about an action that never saved.
WordPress Approval Workflow Integrity Audit is a focused AI agent skill for auditing the business correctness and historical evidence of WordPress client sign-off and approval workflows.
It gives your coding assistant a repeatable method for tracing actual state transitions, persisted data, event history, and side effects. Findings are tied to the relevant code—not vague assumptions about how approvals should work.
What it reviews
Approval lifecycle and transitions
- Allowed and blocked status changes
- Approve, reject, request changes, and blocked outcomes where implemented
- Staff reopen and override paths
- Duplicate submissions and no-op saves
- Conflicting or stale forms and concurrent decisions
- Correct state after partial persistence failures
Immutable decision history
- Historical response records versus the latest-response summary
- Responder identity, decision time, notes, and correct request association
- Append-only history across reopen-and-resubmit cycles
- Legacy records and migrations without invented historical details
- Misleading history after reassignment or cleanup
Document and revision evidence
- Which revision or material was linked at decision time
- Stale approvals after staff change review materials
- Snapshot preservation when current files change or disappear
- Correct handling of unavailable files and client uploads when supported
- Explicit distinction between a descriptive record and permanently archived binary proof
Deadlines, notifications, and side effects
- Due-soon and overdue rules in the WordPress site timezone
- Notifications only for actions that actually persisted
- Repeated hooks, retries, and accidental duplicate mail
- State and history consistency when a write or mail attempt fails
What you receive
The AI agent produces an evidence-based integrity report with:
- A reconstructed state transition map based on your plugin's actual rules.
- Prioritized confirmed findings with file/function/line evidence when available.
- A realistic sequence of actions showing how each issue occurs.
- Expected versus actual state, history, and side effects.
- A targeted smallest-fix recommendation.
- Regression tests in Arrange / Act / Assert form.
- A separate Needs verification section where source review alone is insufficient.
If no supported defects are found, the skill says so rather than inventing issues.
What's included
- Main
SKILL.mdworkflow - State-machine and concurrency review reference
- History, file revision, and evidence provenance guide
- Deadline, email, callback, and failure-ordering guide
- Regression-test case library
- Structured report template
- Clearly labeled fictional worked example
No scripts or external services are required. The skill works as a read-only source review and reports in chat.
Designed for WordPress developers and agencies
Use it before releasing a client portal plugin, while debugging inconsistent approvals, after changing the response handler, or when refactoring a workflow with multiple staff/client entry points.
Example request:
Audit our WordPress approval handler, response history, and staff reopen behavior. Check stale form rejection, versioned review material, notification timing, and all relevant write paths. Report confirmed issues with reproducible scenarios and regression tests. Do not edit files or run commands.
Important limits
This is an AI-guided static code audit, not a WordPress installation, automated integration-test runner, or security certification. It does not send email, execute requests, validate a live production workflow, or guarantee the detection of every defect. Buyers should verify findings with appropriate local/staging tests.
Why two complementary audits? Your authorization audit answers who is allowed to respond. This skill answers whether the response produces a trustworthy result.
Protect the decision—not just the button.
Static, evidence-based source review only. Not live penetration testing, a substitute for running integration tests, or a guarantee that every workflow defect is found. Findings require developer validation. Strongly depends on available source code, real state-transition rules and representative tests. Status vocabularies and history/notification requirements differ between plugins. Does not modify code, execute scripts, or verify actual email delivery.
How to use
- 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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
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 2 days ago