chore: remove inert .claude/hooks/extensions scaffold - #9
Merged
twistedmelonman merged 1 commit intoSep 10, 2026
Merged
Conversation
.claude/hooks/extensions/example.sh.disabled claimed to be "automatically discovered and run by global hooks." That was never true: dotfiles never had a code path reading .claude/hooks/extensions (git log -S over git/hooks/ in dotfiles returns nothing for that string). Live extension discovery is .project-hooks/ only (dotfiles pre-commit:92, pre-push:840), a seam named in dotfiles#243 (2026-08-24), after this scaffold was already committed (2026-01-12). Removal is safe: dotfiles' post-checkout template guards on .claude/ existing, not on this example file, and this repo keeps a tracked .claude/README.md and config.sh.template, so the hook exits before any re-drop of the removed file. Also replaces .claude/README.md with a corrected copy that drops the false discovery claim. Advances #110 Claude-Session: https://claude.ai/code/session_01TkReZXv8XkcWNbcaiWfcvg
This comment has been minimized.
This comment has been minimized.
|
Documentation update: hook extension location moves to No changes to SKILL.md or core artifact. No functional impact. VERDICT: PASS |
twistedmelonman
deleted the
claude/chore-remove-claude-hooks-scaffold-5e330f69
branch
September 10, 2026 20:16
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.
Why
.claude/hooks/extensions/is documented by its own README as being"automatically discovered and run by global hooks." That claim is false and
was never true:
git log -S'.claude/hooks/extensions' -- git/hooks/in thedotfiles repo returns empty. Live extension discovery is
.project-hooks/only (
dotfiles/git/hooks/pre-commit:92,pre-push:840). The scaffolddates to 2026-01-12; the
.project-hooks/seam was named in dotfiles#243on 2026-08-24. The committed file is inert and its README lied about it.
Removal is safe:
dotfiles/git/template/hooks/post-checkout:111guards on.claude/EXISTING, not on the example file. This repo keeps a tracked.claude/README.mdandconfig.sh.template, so the hook exits before thecp -r. Verified by trial clone (DIRTY_LINES=0, nothing re-dropped).What this PR does
git rm -r .claude/hooks— removes the tracked file.claude/hooks/extensions/example.sh.disabled. This is not "removing thedirectory"; the directory itself is regenerable scaffolding with nothing
else tracked in it.
.claude/README.mdwith a corrected copy that drops the false"automatically discovered" claim.
Evidence
Ran the CI-faithful standards check (
standards-check-v1'srun-standards.sh, same script CI runs) locally with an emptyHOMEbothbefore and after this change:
What this does and does not prove. This repo's
.claude/hooks/extensions/example.sh.disabledwas the passing variant (blob
d3b8d301ace5) and the repo was alreadygreen before this change. A green run after the change proves nothing
about whether the removal "worked" — it isn't evidence of that. The only
thing the after-run legitimately demonstrates is that the corrected
.claude/README.mdlints clean.Advances smartwatermelon/dev-env#110
https://claude.ai/code/session_01TkReZXv8XkcWNbcaiWfcvg