startup-hook-skill

You can automate dependency installation at session start by creating a startup hook script and registering it in Claude Code settings. This ensures dependencies are installed before your web-enabled session begins, enabling consistent development workflows.

A Claude Code startup hook works by executing a shell script at session start to install dependencies and configure environment variables. It registers in settings.json, ensuring reproducible environments for tests and linters during initialization.

The best way to ensure idempotent startup hooks is to use scripts that validate dependency states before installing and handle errors robustly. This prevents duplicate installations and ensures reliable startup behavior across repeated session initializations.

Yes, you can use startup hooks to run tests and linters in web-based Claude Code sessions. By designing session-start hooks that install required dependencies, you ensure the environment is fully prepared for tests and linters to execute during initialization.

Session-start hooks may fail to persist environment variables if they are not properly registered in Claude's settings or lack robust error handling. Ensuring proper settings registration and idempotent script behavior resolves persistence issues.

Yes, you need to register hooks in settings.json for Claude Code to recognize them at session start. The startup hook script must be placed in the hooks directory and properly referenced in settings to ensure reliable startup behavior.