repo-gardening: Update AI prompt for labelling

[inaikem]

Following further tests, I updated the OpenAI prompt to ensure the 'Product,' 'Platform', and 'Type' labels are added.

Fixes #

Proposed changes:

Other information:

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

Does this pull request change what data or activity we track or use?

Testing instructions:

• Go to '..'

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Team Review, ...).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• 🔴 Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.

---

🔴 Action required: Please add missing changelog entries for the following projects: projects/github-actions/repo-gardening

Use the Jetpack CLI tool to generate changelog entries by running the following command: jetpack changelog add.
Guidelines: /docs/writing-a-good-changelog-entry.md

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Choose a review path based on your changes:
   • A. Team Review: add the "[Status] Needs Team Review" label
     • For most changes, including minor cross-team impacts.
     • Example: Updating a team-specific component or a small change to a shared library.
   • B. Crew Review: add the "[Status] Needs Review" label
     • For significant changes to core functionality.
     • Example: Major updates to a shared library or complex features.
   • C. Both: Start with Team, then request Crew
     • For complex changes or when you need extra confidence.
     • Example: Refactor affecting multiple systems.
3. Get at least one approval before merging.

Still unsure? Reach out in #jetpack-developers for guidance!

[inaikem]

@anomiex 👋 This is my first time submitting a PR, and any help/guidance is appreciated. This change updates only the prompt used to generate issue labels.

[anomiex]

Since you asked for feedback 🙂 regarding the formatting of the PR itself,

• I adjusted the title for you to be more descriptive.
• You should fill in the template in the description. What you added at the top is decent for the "Proposed changes" section, but "Testing instructions" would be helpful.

You'll need to add a change entry. If you haven't done a pnpm install in your local copy of the monorepo yet, do that. Then you should be able to run pnpm jetpack changelog add to generate one.

As for the PR itself, I'm not terribly familiar with LLM prompt engineering but I left a bunch of inline comments about stuff that would confuse me if trying to follow the instructions. 😅

[anomiex]

Is the AI supposed to ignore this line because it looks like a comment?

[anomiex]

This seems like it will confuse the AI, since no "Product" labels are included in the list above and the AI was instructed to only use labels from the list above.

[anomiex]

Same here, neither "Platform" nor "Type" are included in the list above.

[anomiex]

Also, I wonder whether the AI will have any clue about what either of the platforms are and when they might apply.

[anomiex]

This changed instruction does not match the example response format below.

[anomiex]

More comments the AI is supposed to figure out to ignore?

[inaikem]

@anomiex, thanks for the feedback! I submitted the changes far, far sooner than I should have.

For some context, the addition of the "Product", "Platform" and "Type" label prompts was WPcom specific. Removing them negates the need for this PR, so I'm tempted to go ahead and close it. Everything else you pointed out is jump that should not have been included by me.

@jeherve, testing with "Product", "Platform" and "Type" label prompts resulted in more consistently labeled issues during my testing. I need clarification on how best to proceed here, even with the context that we're aiming to sync labels across repos at some point.

Do you have any suggestions that might unblock me? Thanks both!

[github-actions]

This PR has been marked as stale. This happened because:

• It has been inactive for the past 3 months.
• It hasn’t been labeled `[Pri] BLOCKER`, `[Pri] High`, etc.

If this PR is still useful, please do a [trunk merge or rebase](https://github.com/Automattic/jetpack/blob/trunk/docs/git-workflow.md#keeping-your-branch-up-to-date) and otherwise make sure it's up to date and has clear testing instructions. You may also want to ping possible reviewers in case they've forgotten about it. Please close this PR if you think it's not valid anymore — if you do, please add a brief explanation.

If the PR is not updated (or at least commented on) in another month, it will be automatically closed.