lukaszlenart opened a new pull request, #304: URL: https://github.com/apache/struts-site/pull/304
## Summary Adds a `documenting-struts-release` Claude Code skill that captures the repeatable **content-audit** procedure for a new Struts release — a sibling to the existing `announcing-struts-release` skill (which handles the GA announcement mechanics). The skill codifies the non-obvious judgment calls: - **Find the gap, don't re-document** — check existing coverage (git history + grep) before planning any edit. - Real feature docs live in `core-developers/`, `tag-developers/`, `plugins/` — **not** `source/docs/` (which is only an index). - **Verify constant names/defaults against the released `STRUTS_X_Y_Z` git tag source**, because JIRA descriptions are proposals that often differ from merged code. - Classify every release-note item: documented / gap / no-doc-home. - Keep announcement mechanics out of scope (that's `announcing-struts-release`). ## How it was built Followed the superpowers writing-skills TDD cycle: ran a baseline subagent (no skill) to capture the natural failure modes, wrote the skill to address them, then re-ran with the skill and confirmed the agent now checks existing coverage first, verifies against the tag source, and targets the correct directories. Derived from the 7.2.0 content audit (#303). ## Test Plan - [ ] Skill is discoverable and its `description` triggers on "update docs for a new Struts release" - [ ] Frontmatter is valid (name/description) 🤖 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]
