Skip to content

Conversation

westonruter
Copy link
Member

@westonruter westonruter commented Sep 28, 2025

This adds an AGENTS.md as was recently done for Gutenberg: WordPress/gutenberg#71796

It also updates the CONTRIBUTING.md and PULL_REQUEST_TEMPLATE.md to provide guidance on how AI tools should be used and how their use should be disclosed.

I incorporated parts of my .gemini/styleguide.md from my wp-plugin-template repo.

An initial draft of AGENTS.md was created via Gemini CLI creating a GEMINI.md via /init.

Copy link

github-actions bot commented Sep 28, 2025

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 props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: westonruter <[email protected]>
Co-authored-by: mukeshpanchal27 <[email protected]>
Co-authored-by: aialvi <[email protected]>
Co-authored-by: mindctrl <[email protected]>
Co-authored-by: felixarntz <[email protected]>
Co-authored-by: adamsilverstein <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@westonruter westonruter added [Type] Documentation Documentation to be added or enhanced no milestone PRs that do not have a defined milestone for release skip changelog PRs that should not be mentioned in changelogs labels Sep 28, 2025
@westonruter westonruter changed the title Add AGENTS.md and AI guidance Add AGENTS.md and AI guidance Sep 28, 2025
@westonruter westonruter changed the title Add AGENTS.md and AI guidance Add AGENTS.md and AI contribution guidance Sep 28, 2025
Copy link

@aialvi aialvi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link

@mindctrl mindctrl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Left a couple small comments.

Copy link
Member

@felixarntz felixarntz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@westonruter Happy to see this, thanks for setting it up!

Copy link
Member

@felixarntz felixarntz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two high-level suggestions:

  • Add a section to cover some key architectural concerns (e.g. no OOP, follow WordPress Core procedural programming patterns) and directory overview (how things in different places tie together, e.g. "each plugins/* folder is a separate WordPress plugin" etc).
  • Use more examples instead of long explanations for things like code style, using functions to print scripts, etc.


## Use of AI Tools

<!-- Please disclose whether AI tooling was used to author the code in the pull request. To what extent was AI used? Was it used as a code reviewer, or was it used to "vibe code" everything? It is your responsibility to review and take responsibility for what AI generates. For more, see CONTRIBUTING.md which includes instructions for how to provide instructions to AI agents. -->
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in 1fa61f5

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe this was a misunderstanding - the copy here is still the old one, it needs to be aligned with what's in CONTRIBUTING.md.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Humm. I seemed to have missed making the change I imagined myself making! Now addressed in 688a21c

@westonruter westonruter requested a review from felixarntz October 1, 2025 00:20
Copy link
Member

@felixarntz felixarntz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great. A few more points of feedback.


## Use of AI Tools

<!-- Please disclose whether AI tooling was used to author the code in the pull request. To what extent was AI used? Was it used as a code reviewer, or was it used to "vibe code" everything? It is your responsibility to review and take responsibility for what AI generates. For more, see CONTRIBUTING.md which includes instructions for how to provide instructions to AI agents. -->
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe this was a misunderstanding - the copy here is still the old one, it needs to be aligned with what's in CONTRIBUTING.md.

westonruter and others added 5 commits October 2, 2025 11:18
@westonruter westonruter requested a review from felixarntz October 2, 2025 18:28
@westonruter
Copy link
Member Author

westonruter commented Oct 6, 2025

This looks great. A few more points of feedback.

Anything more for this initial version?

Copy link
Member

@felixarntz felixarntz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's start with this and iterate as we identify areas to improve :)

@mukeshpanchal27 mukeshpanchal27 merged commit 026d3b7 into trunk Oct 7, 2025
11 of 12 checks passed
@mukeshpanchal27 mukeshpanchal27 deleted the add/ai-guidance branch October 7, 2025 03:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no milestone PRs that do not have a defined milestone for release skip changelog PRs that should not be mentioned in changelogs [Type] Documentation Documentation to be added or enhanced
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants