Submit Your Own Plugin To The WordPress Repository

Click Here To Submit Your Plugin

Copy and paste the prompt in Cursor, ChatGPT or Claude and include your plugin Zip file

You are an expert WordPress Core developer and a reviewer for the official WordPress Plugin Repository.

Review my entire WordPress plugin and prepare it for submission to the official WordPress Plugin Repository.

Follow ALL official requirements, recommendations and best practices described here:

https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/

and also use the rest of the official WordPress Plugin Developer documentation whenever relevant:

https://developer.wordpress.org/plugins/

Your goal is to make this plugin fully compliant with the latest WordPress.org requirements while preserving its existing functionality.

Perform a complete review of the entire codebase.

Check and improve at least the following:

## Security

- Sanitize all user input.
- Validate all data.
- Escape all output.
- Verify all URLs.
- Use nonces where required.
- Check user capabilities before performing privileged actions.
- Prevent direct access to PHP files.
- Remove any potential security risks.

## WordPress Coding Standards

- Follow WordPress Coding Standards.
- Use unique prefixes or namespaces to avoid conflicts.
- Use proper hooks, filters and actions.
- Follow WordPress naming conventions.
- Remove dead or duplicate code.
- Improve readability without unnecessarily increasing complexity.

## Plugin Structure

Verify that all required files exist when appropriate, including:

- Main plugin file
- readme.txt
- uninstall.php
- languages folder (if needed)

Create missing files if they improve compliance.

## Plugin Header

Verify that the plugin header is complete and correct, including:

- Plugin Name
- Description
- Version
- Author
- License
- Text Domain
- Domain Path
- Requires at least
- Requires PHP
- Tested up to

## Settings

Review all settings pages and ensure they use WordPress best practices.

Verify:

- Settings API
- Capability checks
- Nonces
- Sanitization
- Validation
- Escaping

## Performance

Look for:

- unnecessary database queries
- duplicate code
- unnecessary assets
- CSS/JS that loads when not needed
- opportunities to lazy-load functionality

Improve performance where appropriate.

## Internationalization

Prepare the plugin for translation.

Use the correct WordPress internationalization functions where needed.

## Privacy

Review the plugin for privacy compliance.

Ensure no unnecessary personal information is stored or transmitted.

## Uninstall

Verify that uninstall.php correctly removes plugin data if appropriate.

If users may prefer to keep their settings after uninstalling, suggest a better implementation.

## Readme

Generate or improve a complete readme.txt that follows the official WordPress.org readme specification.

Include:

- Description
- Installation
- Frequently Asked Questions
- Screenshots
- Changelog
- Upgrade Notice

## Repository Assets

Suggest everything I should create before publishing, including:

- Plugin Icon (256x256)
- High-resolution Icon (512x512)
- Banner (1544x500)
- Small Banner (772x250)
- Screenshots
- Short Description
- Long Description

## Final Report

After completing the review, provide:

1. A summary of all issues you found.
2. Every file you modified.
3. Why each modification was necessary.
4. Any recommendations that are optional but would improve the plugin.
5. Confirmation whether the plugin is ready for submission to the WordPress Plugin Repository.

Do not remove existing functionality unless it violates the official guidelines.

If there are multiple ways to solve a problem, choose the solution that follows WordPress best practices and keeps the plugin as simple as possible.