choo121600 opened a new pull request, #119:
URL: https://github.com/apache/airflow-steward/pull/119
## Summary
Trims `pr-management-mentor` frontmatter (`description` + `when_to_use`)
from **1,514 → 972** characters. The skill was sitting **22 characters under**
Claude Code's per-skill metadata budget of 1,536 — one edit could push it over.
Same principle as #103: keep trigger phrases, short task descriptions, and
routing cues in the frontmatter. Move rationale, "distinct from X"
explanations, implementation details, and enumerated hand-off triggers to the
body, which already covers them.
Tracking: #118
## Before / after
| | before | after | Δ |
|--------------|-------:|------:|-------:|
| description | 954 | 512 | -442 |
| when_to_use | 560 | 460 | -100 |
| **total** | **1,514** | **972** | **-542** |
| budget margin | 22 | 564 | +542 |
| budget | 1,536 | 1,536 | |
## What moved where
| Detail
| Where it lives now
|
|-------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|
| `<upstream>` default-resolution detail (`default: read from
<project-config>/project.md → upstream_repo`) | Placeholder-convention HTML
comment + `## Adopter contract` |
| "runs the tone checklist, then waits for explicit maintainer confirmation
before posting via `gh`" | `## Runtime loop` steps 7–9
|
| "Does **not** triage / review code / open PRs" distinctions
| `## What this skill does not do` (already
enumerated) |
| Four hand-off triggers (`max_agent_turns`, design pushback,
`out_of_scope_topics`, asks for human) | `## Hand-off` section (already
enumerated) |
| "the agent should not talk over a human reviewer"
| `## Runtime loop` step 4
|
No body content was removed — the body already covered everything the
frontmatter was duplicating.
## Trigger-phrase preservation
Every literal trigger phrase from the original `when_to_use` is preserved
verbatim:
- `"mentor PR NNN"`
- `"help the reporter on issue NNN"`
- `"draft a clarifying comment for NNN"`
- `"explain the convention to this contributor on NNN"`
- chains after `pr-management-triage` flags as `"first contributor, missing
repro / convention"`
Skip cues also retain their matchable substrings (`"mid-review with a
maintainer"`, `"security-sensitive"`, `"*deliberately* not replied yet"`).
Routing recall does not regress.
--
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]
