choo121600 opened a new pull request, #103: URL: https://github.com/apache/airflow-steward/pull/103
## Summary The frontmatter for `pr-management-code-review` was carrying the body's job — 5-signal enumeration, criteria source-file paths, the `addPullRequestReview` mutation, and the OpenAI Codex / adversarial-reviewer note — which pushed `description + when_to_use` to **1,708 chars**, over Claude Code's per-skill metadata budget of **1,536**. This PR rewrites `description` and `when_to_use` back to the discovery / routing role they're actually meant for: a short summary the agent uses to *decide whether to invoke the skill*. Everything removed from frontmatter is already covered by the existing body. ## Before / after | | before | after | budget | |------------------|-------:|------:|-------:| | `description` | 1,187 | 448 | | | `when_to_use` | 521 | 496 | | | **total** | **1,708 (over)** | **944 (+592 margin)** | **1,536** | ## What moved where | Detail | Where it lives now | |---|---| | 5-signal semantics (`review-requested`, `touching-mine`, `CODEOWNER`, `mention`, `reviewed-before`) | `# Inputs` table | | Project review-criteria source files | `# Adopter configuration` + Golden rule 3 | | `addPullRequestReview` mutation | `## Step 2 — Sequential per-PR review` | | OpenAI Codex / adversarial-reviewer integration | Golden rule 4 + `adversarial.md` | | `ready for maintainer review` label selector | `# Inputs` table | ## Trigger-phrase preservation `when_to_use` keeps every literal trigger phrase from the original — including the niche ones (`review my CODEOWNER PRs`, `pair this PR with Codex / adversarial review`, `review the ready-for-maintainer-review queue`) — so routing-time matching is no weaker than before. related: #92 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
