Resolve WordPress Support Ticket

A reusable Codex Skill for investigating, reproducing, fixing, and verifying WordPress plugin support tickets.

This skill provides a standardized workflow for resolving customer-reported issues while protecting production environments. It guides Codex through production investigation, local development, root cause analysis, implementation, verification, and technical reporting.

The skill is designed for WordPress plugin development teams and is particularly useful for repositories containing multiple plugins or products.

Features

• 🔍 Investigates customer-reported issues using WordPress Admin access.
• 🤖 Uses Agent Browser for browser automation and UI verification.
• 🔒 Enforces a read-only investigation workflow on production sites.
• 🧩 Automatically identifies the affected plugin(s) by matching the Plugin Name from the support ticket with the plugin's WordPress header.
• 🌿 Creates a new Git branch from upstream/development.
• 🛠 Reproduces issues locally before implementing fixes.
• ✅ Verifies the fix and checks for regressions.
• 🔀 Creates a pull request targeting upstream/development after the ticket is resolved.
• 📝 Produces a structured technical investigation report.
• 🎯 Encourages minimal, focused code changes.

---

Prerequisites

Before using this skill, ensure you have:

• Codex with support for custom skills
• Git
• A local checkout of your WordPress plugins repository
• Agent Browser installed for browser automation

Installing Agent Browser

Install the Agent Browser CLI:

npm install -g agent-browser

Install the required browser binaries:

agent-browser install

On Linux, you may also need to install browser dependencies:

agent-browser install --with-deps

Verify the installation:

agent-browser --version

For the latest installation instructions, visit:

https://github.com/vercel-labs/agent-browser

---

Installing the Skill

Global Installation

To make the skill available in every project:

mkdir -p ~/.codex/skills
cd ~/.codex/skills

git clone https://github.com/<your-username>/resolve-support-ticket.git

Restart Codex after installation.

---

Repository Structure

resolve-wp-support-ticket/
├── SKILL.md
├── example.md
└── readme.md

---

Usage

Once the skill is installed, simply ask Codex to use it and provide the support ticket.

Example:

Use the Resolve WordPress Support Ticket skill.

# Support Ticket

## Plugin Name

Directorist - WooCommerce Pricing Plans

## Customer Message

Hello,

Every time I update a listing, the request enters an infinite loop and eventually returns a 500 timeout error.

When the WooCommerce Pricing Plans addon is disabled, updating listings works correctly.

Please investigate.

## Site Access

WordPress Admin URL:
https://example.com/wp-admin

Username:
admin

Password:
password

The skill will automatically:

1. Identify the affected plugin(s) by matching the Plugin Name from the support ticket with the plugin's WordPress header.
2. Investigate the issue on the production site using the provided credentials.
3. Use Agent Browser to reproduce and inspect the issue when appropriate.
4. Gather diagnostic information without modifying the production site.
5. Fetch the latest upstream changes.
6. Create a new branch from upstream/development.
7. Reproduce the issue locally.
8. Identify the confirmed root cause.
9. Implement a minimal and safe fix.
10. Verify the fix and perform regression testing.
11. Commit and push the verified fix.
12. Create a pull request targeting upstream/development with a description covering why the PR is needed, what was done, and reviewer-facing acceptance criteria.
13. Produce a structured technical report summarizing the investigation and implementation.

---

Expected Output

After completing the investigation, the skill produces a report containing:

• Products identified
• Investigation summary
• Reproduction steps
• Root cause analysis
• Solution summary
• Files modified
• Verification results
• Regression testing
• Remaining risks (if any)
• Suggested Git branch name
• Suggested commit message
• Pull request title
• Pull request URL
• Pull request description with why it is needed, what was done, and acceptance criteria that explain how a reviewer can verify the PR

---

Best Practices

For the best results:

• Provide the complete support ticket.
• Include WordPress Admin credentials when production investigation is required.
• Keep your local repository up to date.
• Ensure all related plugins are available in the repository.
• Allow the skill to validate the customer's findings instead of assuming they are correct.
• Verify fixes before submitting a pull request.

---

License

This project is licensed under the MIT License.