Integrate Plugin Check Namer as standard AI Name Check#1390
Draft
ishitaj34 wants to merge 1 commit into
Draft
Conversation
Member
|
Hello! Thanks for the contribution. Please resolve the conflicts, so we can review this PR. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
Closes #1370
Migrates the standalone Plugin Check Namer tool directly into the main audit suite as a standard static check. It deprecates and removes the separate Namer submenu page and its custom JS/HTML frontend assets.
Why?
wp plugin check <slug> --aiwithout custom CLI handling.How?
AI_Name_Check.phpimplementingStatic_Check. It parses the name and author from plugin headers viaget_plugin_data()and runs AI queries if the active runner has enabled AI. Guideline violations are mapped directly to standard check Errors and Warnings.Default_Check_Repository.phpso it is included in the default check set.should_use_ai()public and addedget_ai_model_preference()to allow checks to access the current AI configuration.Plugin_Main.phpand removing unused files.Testing Instructions
Via Admin Screen:
Via CLI:
Run Unit Tests:
AI_Name_Check_Testsexecutes and passes:AI Usage Disclosure
If AI tools were used, please describe how they were used:
Used Gemini coding assistant to plan the refactoring path, draft unit test suite, and compile the deprecation cleanup list.