emacs-testing
Test changes in a dedicated Emacs session. Good for validating behavior and UI results.
When & Why to Use This Skill
This Claude skill enables automated testing and validation within a dedicated Emacs session. By leveraging Emacs daemon and emacsclient, it allows developers to verify code changes, validate UI behavior, and ensure environment consistency in an isolated sandbox without disrupting the primary workspace.
Use Cases
- UI and Behavior Validation: Run and inspect visual changes or interactive functions in a sandboxed Emacs instance to ensure correct rendering and logic.
- Isolated Code Testing: Execute Emacs Lisp snippets or package tests in a clean daemon server to prevent side effects on the user's main configuration.
- Automated Workflow Verification: Use emacsclient to programmatically trigger commands and evaluate results, streamlining the debugging process for complex Emacs setups.
| name | emacs-testing |
|---|---|
| description | Test changes in a dedicated Emacs session. Good for validating behavior and UI results. |
Before starting, you MUST ask me if you have permission to test in the existing Emacs server. If
not, start a new Emacs daemon server: emacs --daemon=kele-testing.
Send commands to the Emacs with: emacsclient --eval. If I did not give permission to run in the
existing server, use emacsclient -s kele-testing --eval.
If you created a separate daemon server, terminate it once you are done testing.