chime/.claude/hooks, branch main Emacs chimes, notifications, and modeline reminders so you don't miss events https://git.cjennings.net/chime/atom?h=main 2026-06-24T02:00:33+00:00 chore: stop tracking local dev tooling 2026-06-24T02:00:33+00:00 Craig Jennings c@cjennings.net 2026-06-24T02:00:14+00:00 urn:sha1:1587c119ceeba4698974f402eda17482e68202e8 chore: refresh .claude rules and hooks to rulesets canonical 2026-06-12T23:14:19+00:00 Craig Jennings c@cjennings.net 2026-06-12T23:14:19+00:00 urn:sha1:b39633d9d482b6510e5626e0c5441ad211508a6e The startup language-bundle sync repaired drift in these rulesets-owned files. Committing them at canonical so future syncs stay no-ops. fix: scope validate-el.sh hook to in-project files 2026-05-13T18:48:56+00:00 Craig Jennings c@cjennings.net 2026-05-13T18:48:56+00:00 urn:sha1:997d839ca41b7a6fc46f3fba722476e6558688ab The PostToolUse hook tried to byte-compile every .el file edited, including ones outside the chime project. Out-of-project files typically require packages that aren't on the hook's -L paths, so validation failed for unrelated reasons. Exit 0 when the edited file isn't under $PROJECT_ROOT. fix(hooks): run validate-el test phase from tests/ directory 2026-04-22T01:38:18+00:00 Craig Jennings c@cjennings.net 2026-04-22T01:38:18+00:00 urn:sha1:b2e903826e9baf1b0a1a8c400c90625022a00dd8 Test files start with (require 'test-bootstrap (expand-file-name "test-bootstrap.el")). The expand-file-name call resolves against default-directory, which in batch mode is the directory the shell was in when emacs started. The hook ran emacs from the project root, so the require looked for the bootstrap at the project root and could not find it. Every Edit or Write to a test file failed the hook. The fix is to cd into PROJECT_ROOT/tests inside the subshell before launching emacs, so the bootstrap require resolves to tests/test-bootstrap.el where the file actually lives. chore(claude): sync validate-el.sh JSON channel + pairwise rule from rulesets 2026-04-19T22:07:29+00:00 Craig Jennings c@cjennings.net 2026-04-19T22:07:29+00:00 urn:sha1:592142e3788e55ae166103cc6b653b9531bba38a chore: add Claude Code ruleset via ~/code/rulesets install-elisp 2026-04-19T17:46:59+00:00 Craig Jennings c@cjennings.net 2026-04-19T17:46:59+00:00 urn:sha1:6d72c4eed04c7d28639ee31789e6201275e7d9b7 Installs the Elisp ruleset from the rulesets repo: - CLAUDE.md (project instructions template) - .claude/rules/ (testing, verification, elisp, elisp-testing) - .claude/hooks/validate-el.sh (check-parens + byte-compile + run matching tests on every .el edit via PostToolUse) - .claude/settings.json (permission allowlist + hook wiring) - githooks/pre-commit (secret scan + staged-file paren check) core.hooksPath set to githooks/ so the pre-commit activates automatically. Hooks use \$CLAUDE_PROJECT_DIR with a script-relative fallback, so a fresh clone works without path edits. .gitignore extended with personal-override entries (settings.local.json, .cache/) and byte-compile artifacts (*.elc, *.eln).