potiuk opened a new pull request, #32: URL: https://github.com/apache/airflow-steward/pull/32
## Summary - Slim top-level README from 1139 → 996 lines (-12%, +279/-422 diff). The 478-line "Process reference: the 16 steps" deep dive duplicated content already authoritative in each skill's `SKILL.md`; replaced with a Mermaid lifecycle diagram + 1-3 sentence per-step summaries that link to the responsible skill. - Add new top-level `## Skills` section: categorised index grouping the 14 skills by function (Setup / Security workflow / PR triage and review). PR triage section is a placeholder — the `pr-*` skill family lift from `apache/airflow` lands in the next PR. - Step anchors preserved (`#step-1--report-arrives-on-security` … `#step-16--credit-corrections`) so existing in-doc links still resolve. doctoc TOC regenerated. The Mermaid lifecycle diagram colour-codes by role (yellow = triager Steps 1-5, blue = remediation developer Steps 6-11, green = release manager Steps 12-16, red = invalid-close terminal state) so role hand-offs are visible at a glance. ## Deferred to a follow-up Per-skill flow diagrams in skill folders (the *"eventually in mermaid diagram docs in the skill folders"* part of the original ask) are intentionally **not** in this PR — keeping it focused on the README restructure. Each skill's `SKILL.md` (currently 100-2150 lines) is the authoritative process doc today; a follow-up PR can add a `flow.md` per skill with a workflow mermaid + brief narrative once the categorised structure has settled. ## Test plan - [x] doctoc TOC regenerated with new Skills section + subsections - [x] All 16 step anchors preserved (no broken in-doc links) - [x] All pre-commit hooks pass locally (markdownlint, typos, doctoc, etc.) - [ ] CI link-check (lychee) passes - [ ] Mermaid renders correctly on github.com (visual check on the PR page) - [ ] Reviewer eyeballs the new Skill index for accuracy of each skill's one-line purpose 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
