feat(skills): add verify-apache-steward skill for adopter tracker integration check - #28
Merged
Merged
Conversation
…egration check Adds a sixth skill that verifies the framework is correctly integrated as a git submodule of the adopter's tracker repository. The skill is the missing companion to the existing `verify-secure-config` (which checks the secure-agent setup): the two are independent layers of the adopter-side health check and both should pass for a fully-wired tracker. Checks (read-only, never modifies anything): 1. Pre-flight — refuses to run from inside the framework checkout itself; surfaces the framework remote and tells the user to invoke from the tracker root. 2. `.apache-steward/` directory present at tracker root. 3. `<project-config>/project.md` exists and required `TODO:` placeholders are filled — distinguishes runtime- blocking gaps (`tracker_repo`, `upstream_repo`, `tracker_default_branch`) from optional fields tied to specific skills (mailing-list addresses, CVE tooling URLs, Gmail/PonyMail flags). 4. `.gitmodules` carries the framework entry with a sane `url` (warns on a fork URL). 5. Submodule initialised + working tree present (catches the most common "fresh tracker clone, never ran `git submodule update --init`" failure). 6. Submodule pointer aligned with parent's index — surfaces the `+` "HEAD ahead of recorded SHA" / `U` "merge conflict" states that `git submodule status` reports. 7. Post-merge hook wired (⚠ if not — optional ergonomics). Cross-references: - `secure-agent-setup.md` Quick start: agent-guided list grows to six skills, with `verify-apache-steward` as step 2 (the prerequisite check before the secure-config flow makes sense for adopters consuming the framework as a submodule). - `upgrade-apache-steward`: the post-pull "if you're consuming the framework as a tracker submodule" branch now suggests `verify-apache-steward` to confirm the parent tracker's pointer is still aligned (the skill catches the `+` state directly). Generated-by: Claude Code (Opus 4.7)
andreahlert
added
the
mode:platform
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
verify-apache-steward— sixth secure-config-adjacent skill, but unlike the other five it checks the adopter tracker integration layer rather than the secure-agent setup. Read-only checklist over.apache-steward/,<project-config>/project.md,.gitmodules, submodule init state, submodule pointer alignment, and the optional post-merge hook. Reports ✓/✗/⚠ with concrete remediation commands. Refuses to run from inside the framework checkout itself.secure-agent-setup.mdQuick start: list grows from 5 to 6 skills; new skill lands at position 2 (after opening Claude Code, beforesetup-secure-config) with a clear "if you consume the framework as a submodule" scope note.upgrade-apache-steward: post-pull tracker-submodule branch now cross-references the new skill to confirm pointer alignment.The new skill is the missing companion to the existing
verify-secure-config. Both are read-only adopter-side checks; the two together cover (a) "is the framework integrated?" and (b) "is the secure-agent setup wired?". An adopter can have one without the other.Test plan
prek run --files <changed files>clean (markdownlint, typos, placeholder linter, doctoc TOC regen).verify-apache-steward/SKILL.mdfrontmatter parses (name/description/when_to_use).verify-apache-steward↔verify-secure-config,verify-apache-steward↔upgrade-apache-steward, README anchors (Adopting the framework).secure-agent-setup.mdlists exactly 6 skills, in the order verify-apache-steward → setup → verify-secure-config → upgrade → update → sync.