andreahlert opened a new pull request, #66:
URL: https://github.com/apache/airflow-steward/pull/66

   ## Summary
   
   `skill-validator` requires every SKILL.md to declare `license` in its 
frontmatter, but 13 skills predate the requirement and were never backfilled. 
Running the validator locally on `main` surfaces them all:
   
   ```
   $ skill-validate | grep "missing required frontmatter key: 'license'"
   .claude/skills/pr-management-stats/SKILL.md:1: missing required frontmatter 
key: 'license'
   .claude/skills/security-cve-allocate/SKILL.md:1: missing required 
frontmatter key: 'license'
   ... 11 more ...
   ```
   
   All 13 skills are already Apache-2.0 (the SPDX header at the top of every 
file under `.claude/skills/` says so), so this is a mechanical one-value fill, 
no decisions needed:
   
   - `pr-management-stats`
   - `security-cve-allocate`
   - 
`security-issue-{deduplicate,fix,import,import-from-md,import-from-pr,invalidate,sync}`
   - `setup-isolated-setup-{install,update,verify}`
   - `setup-shared-config-sync`
   
   ## What this does not fix
   
   The remaining `skill-validator` violations on `main` are not mechanical:
   
   - 13 broken links to deleted `code-review.instructions.md`. Decision needed: 
restore the file or update references.
   - 3 broken `providers/AGENTS.md` links (apache/airflow-specific paths leaked 
into framework-generic skills).
   - 4 unsubstituted `<...>` placeholders in 
`pr-management-triage/comment-templates.md` (adopter-config convention vs. 
literal substitution).
   - Anchor mismatches from a slugify bug; #65 fixes most of them.
   
   Each is a separate scoped follow-up. After all of them, `skill-validator` 
can be wired into prek + CI without burning the build.


-- 
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]

Reply via email to