Repository navigation
Conversation
|
Hello! Thanks for the contribution. Please resolve the conflicts, so we can review this PR. |
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
I'd suggest to add the option for Plugin Name in AI Settings: Name Check. To differentiate with AI Analysis. |
|
I've closed this PR due to inactivity. |
|
Hey @davidperezgar |
|
Hello, I've already made that enhancement and merged to the trunk. Thanks. |
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 <plugin-slug> --aiwithout custom CLI handling.How?
AI_Name_Check, a newStatic_Checkimplementation that reads the plugin name and author from the plugin headers usingget_plugin_data(), performs AI-based name analysis, and reports guideline violations as standard Plugin Check errors and warnings.ai_namecheck inDefault_Check_Repository.phpso it runs as part of the default check set.should_use_ai()public and addedget_ai_model_preference()to allow checks to access the current AI configuration.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.