Summary
The setup family's documentation table lists every setup skill except setup — the bootstrap
skill the whole family depends on. Add a row for it.
Background
PR #798 filled three gaps in the table (setup-status, setup-override-upstream,
setup-upstream-fix) and bumped the skill count in the top-level README.md from 8 to 9. That
count is right: there are exactly nine skills/setup* directories.
But after that PR, skills/setup/SKILL.md is the only one of the nine with no row of its own.
Two of its sub-commands are listed — setup upgrade links skills/setup/upgrade.md and
setup verify links skills/setup/verify.md — but the skill's entry point is not, even though
skills/setup/SKILL.md exists alongside adopt.md, unadopt.md, overrides.md,
agents.md, worktree-init.md and skill-sources.md.
The top-level README calls this skill out by name — "The prerequisite — at minimum the setup
skill itself runs out of this family" — so a reader who follows that pointer into
docs/setup/README.md finds the family's other eight skills and not the one they were sent to
read about.
Where to look
docs/setup/README.md — the skill table; the existing rows show the format
([name](../../skills/name/SKILL.md) | one-sentence description).skills/setup/SKILL.md — read this to describe what the skill does; do not infer it from the
name.README.md (repo root) — the families table, for the "9 skills" count this row makes true.
Acceptance criteria
Estimated effort
~30 minutes for someone new to the codebase.
Getting started
[How to contribute](https://github.com/apache/airflow-steward/blob/main/CONTRIBUTING.md#your-first-contribution)
This issue was drafted with the help of an AI-assisted tool and reviewed by a Magpie maintainer before posting. If anything here is unclear or looks wrong, say so on the issue: a real person is reading.
Summary
The setup family's documentation table lists every setup skill except
setup— the bootstrapskill the whole family depends on. Add a row for it.
Background
PR #798 filled three gaps in the table (
setup-status,setup-override-upstream,setup-upstream-fix) and bumped the skill count in the top-levelREADME.mdfrom 8 to 9. Thatcount is right: there are exactly nine
skills/setup*directories.But after that PR,
skills/setup/SKILL.mdis the only one of the nine with no row of its own.Two of its sub-commands are listed —
setup upgradelinksskills/setup/upgrade.mdandsetup verifylinksskills/setup/verify.md— but the skill's entry point is not, even thoughskills/setup/SKILL.mdexists alongsideadopt.md,unadopt.md,overrides.md,agents.md,worktree-init.mdandskill-sources.md.The top-level README calls this skill out by name — "The prerequisite — at minimum the
setupskill itself runs out of this family" — so a reader who follows that pointer into
docs/setup/README.mdfinds the family's other eight skills and not the one they were sent toread about.
Where to look
docs/setup/README.md— the skill table; the existing rows show the format(
[name](../../skills/name/SKILL.md) | one-sentence description).skills/setup/SKILL.md— read this to describe what the skill does; do not infer it from thename.
README.md(repo root) — the families table, for the "9 skills" count this row makes true.Acceptance criteria
docs/setup/README.mdhas a row linking../../skills/setup/SKILL.md.skills/setup/SKILL.mdactually does.prek run --all-filespasses, including the lychee link check.Estimated effort
~30 minutes for someone new to the codebase.
Getting started
[How to contribute](https://github.com/apache/airflow-steward/blob/main/CONTRIBUTING.md#your-first-contribution)
This issue was drafted with the help of an AI-assisted tool and reviewed by a Magpie maintainer before posting. If anything here is unclear or looks wrong, say so on the issue: a real person is reading.