feat(af): clean up legacy AF skill dirs on init#17
Merged
Conversation
The AF fork's --force init overwrites current bundle files but leaves behind skill directories that were shipped in older versions and have since been removed or consolidated. Claude Code auto-discovers these via skill descriptions, which can hijack lifecycle dispatch. Concrete case: a stale speckit-af-check-version skill (replaced by the inline VERSION_FAIL branch in common.md) intercepts the VERSION_FAIL token from check-version.sh and renders its frozen-in-time "3-step" upgrade message with aggressive find-based cleanup, instead of letting common.md's current re-init prompt run. Mirror the existing .claude/commands/speckit.*.md cleanup with an explicit list of legacy AF skill directories to prune: - speckit-af-check-version — replaced by inline VERSION_FAIL branch - speckit-af-after-common — never had a SKILL.md; empty dir leftover Hardcoded list (not glob-derived) to avoid accidentally removing skills that the current bundle does ship — the install hierarchy names overlap enough that an "anything not in current bundle" heuristic is risky. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
1 participant
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.
The AF fork's --force init overwrites current bundle files but leaves behind skill directories that were shipped in older versions and have since been removed or consolidated. Claude Code auto-discovers these via skill descriptions, which can hijack lifecycle dispatch.
Concrete case: a stale speckit-af-check-version skill (replaced by the inline VERSION_FAIL branch in common.md) intercepts the VERSION_FAIL token from check-version.sh and renders its frozen-in-time "3-step" upgrade message with aggressive find-based cleanup, instead of letting common.md's current re-init prompt run.
Mirror the existing .claude/commands/speckit.*.md cleanup with an explicit list of legacy AF skill directories to prune:
Hardcoded list (not glob-derived) to avoid accidentally removing skills that the current bundle does ship — the install hierarchy names overlap enough that an "anything not in current bundle" heuristic is risky.
Description
Testing
uv run specify --helpuv sync && uv run pytestAI Disclosure