diff options
| author | Craig Jennings <c@cjennings.net> | 2026-04-19 12:36:04 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-04-19 12:36:04 -0500 |
| commit | 019db5f9677902ba02d703a8554667d1b6e88f6b (patch) | |
| tree | 37c7991c7e29b443348996f1c2407030b3571026 /languages/elisp/claude | |
| parent | 18fcaf9f27d03849487078b30f667c3b574e6554 (diff) | |
| download | rulesets-019db5f9677902ba02d703a8554667d1b6e88f6b.tar.gz rulesets-019db5f9677902ba02d703a8554667d1b6e88f6b.zip | |
refactor: generalize testing.md, split Python specifics, DRY install
claude-rules/testing.md is now language-agnostic (TDD principles, test
categories, coverage targets, anti-patterns). Scope header widened to
**/*. Python-specific content (pytest, fixtures, parametrize, anyio,
Django DB testing) moved to languages/python/claude/rules/python-testing.md.
Added languages/python/ bundle (rules only so far; no CLAUDE.md template
or hooks yet — Python validation tooling differs from Elisp). Added
install-python shortcut to the Makefile.
Updated scripts/install-lang.sh to copy claude-rules/*.md into each
target project's .claude/rules/. Bundles no longer need to carry their
own verification.md copy — deleted languages/elisp/claude/rules/verification.md.
Single source of truth in claude-rules/, fans out via install.
Elisp-testing.md now references testing.md as its base (matches the
python-testing.md pattern).
Diffstat (limited to 'languages/elisp/claude')
| -rw-r--r-- | languages/elisp/claude/rules/elisp-testing.md | 3 | ||||
| -rw-r--r-- | languages/elisp/claude/rules/verification.md | 42 |
2 files changed, 3 insertions, 42 deletions
diff --git a/languages/elisp/claude/rules/elisp-testing.md b/languages/elisp/claude/rules/elisp-testing.md index fcad9de..6cb59b1 100644 --- a/languages/elisp/claude/rules/elisp-testing.md +++ b/languages/elisp/claude/rules/elisp-testing.md @@ -2,6 +2,9 @@ Applies to: `**/tests/*.el` +Implements the core principles from `testing.md`. All rules there apply here — +this file covers Elisp-specific patterns. + ## Framework: ERT Use `ert-deftest` for all tests. One test = one scenario. diff --git a/languages/elisp/claude/rules/verification.md b/languages/elisp/claude/rules/verification.md deleted file mode 100644 index 8993736..0000000 --- a/languages/elisp/claude/rules/verification.md +++ /dev/null @@ -1,42 +0,0 @@ -# Verification Before Completion - -Applies to: `**/*` - -## The Rule - -Do not claim work is done without fresh verification evidence. Run the command, read the output, confirm it matches the claim, then — and only then — declare success. - -This applies to every completion claim: -- "Tests pass" → Run the test suite. Read the output. Confirm all green. -- "Linter is clean" → Run the linter. Read the output. Confirm no warnings. -- "Build succeeds" → Run the build. Read the output. Confirm no errors. -- "Bug is fixed" → Run the reproduction steps. Confirm the bug is gone. -- "No regressions" → Run the full test suite, not just the tests you added. - -## What Fresh Means - -- Run the verification command **now**, in the current session -- Do not rely on a previous run from before your changes -- Do not assume your changes didn't break something unrelated -- Do not extrapolate from partial output — read the whole result - -## Red Flags - -If you find yourself using these words, you haven't verified: - -- "should" ("tests should pass") -- "probably" ("this probably works") -- "I believe" ("I believe the build is clean") -- "based on the changes" ("based on the changes, nothing should break") - -Replace beliefs with evidence. Run the command. - -## Before Committing - -Before any commit: -1. Run the test suite — confirm all tests pass -2. Run the linter — confirm no new warnings -3. Run the type checker — confirm no new errors -4. Review the diff — confirm only intended changes are staged - -Do not commit based on the assumption that nothing broke. Verify. |