smoke-test

To verify Olympus hooks, run a pre-release smoke test that checks PreToolUse, PostToolUse, and agent tracking hooks within a dedicated test directory. This process validates hook firing, file read/write operations, and agent spawning to ensure correct system configuration.

A smoke test for multi-agent orchestration systems checks critical integration points like hook firing, agent spawning, and file read/write operations. It verifies that automated features function as expected and validates correct environment configuration before new releases.

Testing Olympus integration hooks requires correct hook configuration in the Claude Code environment. The smoke test checks user settings and script paths to confirm the Olympus installation is properly set up before validating automated features.

Test PreToolUse and PostToolUse hooks by executing a smoke test in a dedicated test directory. This validates hook firing and responses for file read/write operations and agent spawning, followed by mandatory cleanup of all temporary test files and artifacts.

Olympus hooks may not work if they are incorrectly configured in the Claude Code environment. Running a smoke test checks user settings and script paths to identify configuration issues and verify that all integration points fire correctly.