justinmclean opened a new pull request, #585:
URL: https://github.com/apache/airflow-steward/pull/585
## Summary
workflow-security-audit and dependency-audit landed on main in PRs #567 and
#569 respectively but docs/repo-health/README.md still listed them as
"Candidate skills (not yet built)". Move both into the Current skills section
alongside ci-runner-audit, update their descriptions to match the shipped skill
frontmatter, and note that license-compliance-audit and flaky-test-triage are
still proposed candidates.
Update tools/spec-loop/specs/repo-health-family.md Known Gaps to replace
"Family is one skill deep" with the accurate three-skill count, record that
repo-health-config.md is already on main (via PR #567), and drop the stale "no
adopter-config scaffold yet" note.
Also sync uv.lock to match tools/spec-validator/pyproject.toml (pytest
specifier was >=9.1.0 in the lock but >=8.0 in the pyproject).
Generated-by: Claude (Opus 4.7)
## Type of change
<!-- Tick all that apply. -->
- [ ] Skill change (`.claude/skills/<name>/`) — eval fixtures updated below
- [ ] Tool / bridge contract (`tools/<system>/*.md`)
- [ ] Python package (`tools/*/` with `pyproject.toml`)
- [ ] Groovy reference impl
- [ ] Cross-cutting (RFC, AGENTS.md, sandbox, privacy-LLM)
- [X] Documentation (`docs/`, `README.md`, `CONTRIBUTING.md`)
- [ ] Project template (`projects/_template/`)
- [ ] CI / dev loop (`prek`, workflows, validators)
- [ ] Other:
## Test plan
- [X] `prek run --all-files` passes
- [ ] For Python packages touched: `uv run pytest` / `ruff check` / `mypy`
passes
- [ ] For Groovy bridges touched: command-line invocation tested end-to-end
- [ ] For skill changes: eval suite passes for the affected skill
(`PYTHONPATH=tools/skill-evals/src python3 -m skill_evals.runner
tools/skill-evals/evals/<skill>/`)
- [ ] For skill *behaviour* changes: a new or updated eval fixture is
included in this PR
(a regression test for the bug fixed / the behaviour added — see
CONTRIBUTING.md)
- [ ] Other:
--
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]
