[agent-suggestions] Agent suggestions - 2026-06-22

## Agent Suggestions
**Date:** 2026-06-22

### 1. `trigger-pr-readiness-concierge`
**Trigger:** `pull_request` (`opened`, `synchronize`, `reopened`, `ready_for_review`, `labeled`, `unlabeled`) and optionally draft PR updates.

**Purpose:** Add a lightweight PR-readiness agent that comments with concrete next steps when a PR is likely to be blocked by missing or contradictory review hygiene: empty local test instructions, unchecked changelog/default-config/docs checklist items, `skip-changelog` vs unchecked changelog state, missing team/type labels, or draft PRs that already need early maintainer guidance. Scope should be limited to actionable checklist/metadata gaps, not code review.

**Proposed safe outputs:** `add-comment` on the PR with exact missing items and suggested commands/labels; `noop` when the PR is already review-ready. It should not create code changes.

**Evidence:**
- The PR template explicitly asks contributors to keep mandatory checklist items and local test instructions: `.github/PULL_REQUEST_TEMPLATE.md:32-45` and `.github/PULL_REQUEST_TEMPLATE.md:55-59`.
- The existing changelog workflow only fails the check when a fragment is missing/syntactically invalid; it does not explain broader PR-readiness gaps or comment with next steps: `.github/workflows/fragment-in-pr.yml:3-8` and `.github/workflows/fragment-in-pr.yml:15-26`.
- Existing AI PR review skips draft PRs and only runs for owner/member/collaborator authors: `.github/workflows/trigger-pr-review.yml:15-19`. PR Actions Detective only reacts after selected workflow failures: `.github/workflows/trigger-pr-actions-detective.yml:3-5` and `.github/workflows/trigger-pr-actions-detective.yml:16-19`.
- Recent open PR examples show repeated readiness friction that is not a code-review finding:
- https://github.com/elastic/beats/pull/51408 is a draft PR whose body has an empty local test code block and an unchecked changelog item while also carrying `skip-changelog`.
- https://github.com/elastic/beats/pull/51326 is a ready-for-review PR with the changelog checklist item still unchecked.
- https://github.com/elastic/beats/pull/50840 is a draft PR with an empty `How to test this PR locally` section.
- https://github.com/elastic/beats/pull/51083 remains labeled `needs_team`, showing a PR metadata gap that reviewers still need to resolve manually.

**Why not covered already:** Current workflows cover code review, docs review, CI/build failure diagnosis, duplicate issues, issue triage, and changelog validation. None proactively performs a narrow, low-risk PR hygiene/readiness pass before or independently of code review, especially for draft PRs and non-CI-blocking template gaps.

## Duplicate Checks
- Prior open agent-suggestion reports reviewed:
- https://github.com/elastic/beats/issues/51149 (`trigger-backport-branch-health-guard`)
- https://github.com/elastic/beats/issues/50211 (`trigger-downstream-compat-smoke`)
- https://github.com/elastic/beats/issues/49774 (Agentic Workflow Failure Triage)
- Open duplicate searches returned no matching PR-readiness suggestion for `"PR readiness concierge"`, `"pull request readiness"`, `"PR hygiene"`, or `"missing changelog"` in `elastic/beats` open issues/PRs.

## Downstream Signals
- Downstream repositories using `elastic/ai-github-actions` workflows were reviewed as part of the investigation, but no downstream-only workflow gap was stronger or less duplicative than the Beats PR-readiness gap above.

## Suggested Next Steps
- [ ] Prototype `trigger-pr-readiness-concierge.yml` using comment/noop safe outputs only.
- [ ] Start with deterministic checks for empty `How to test`, unchecked changelog/default-config/docs checklist items, `needs_team`, and missing type labels.
- [ ] Tune the workflow to comment once per PR state change and suppress duplicate comments when the same readiness gap is already reported.

---
[What is this?](https://ela.st/github-ai-tools) | [From workflow: Agent Suggestions](https://github.com/elastic/beats/actions/runs/27958727808)

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
> - [x] expires on Jun 29, 2026, 2:21 PM UTC

Start by reading .github/PULL_REQUEST_TEMPLATE.md:32-45 and :55-59, then compare fragment-in-pr.yml and the existing PR review and Actions Detective workflows. Define trigger and state-change behavior for trigger-pr-readiness-concierge.yml, covering the listed deterministic checklist and metadata gaps. Done means it comments exact actionable gaps, returns noop for ready PRs, and suppresses duplicate reports.

Written by the indexing model from the issue text.