WordPress / WordPress/plugin-check

Integrate Plugin Check Namer into Plugin Check AI Analysis

Open
#1,370 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
362
Forks
126
Avg merge
1d 23h
Merged PRs (30d)
22

Description

It would be useful to move the functionality from Plugin Check Namer into Plugin Check directly, as an additional checkbox under the existing AI Analysis options.

The new option could check the plugin name using information already available from the plugin itself, without requiring the user to provide any extra input.

Proposed change

Add a checkbox to AI Analysis, for example:

  • Check plugin name

When enabled, Plugin Check would analyze the plugin name and provide feedback on whether it is appropriate, clear, and aligned with WordPress.org plugin directory expectations.

Benefits

  • Simplifies the interface by avoiding a separate tool/workflow.
  • Keeps related AI-powered checks in one place.
  • Requires no special user input because the plugin name can be read from the plugin headers.
  • Makes the name check easier to discover and run alongside the rest of Plugin Check.

Notes

This could replace or absorb the current Plugin Check Namer workflow, while keeping the user experience focused inside Plugin Check.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the existing AI Analysis options in Plugin Check and the current Plugin Check Namer workflow. Confirm how the plugin name is read from plugin headers and how AI feedback is presented. Done means a new “Check plugin name” option runs alongside the existing checks without extra user input and provides the proposed name feedback.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.