setup-project

Project safety guards are automated by reading the detection cache, installing baseline hooks, and merging stack-specific rules into project settings. This provides a hardened baseline that blocks destructive actions and enforces best practices.

Project safety guards are protective rules and hooks that block destructive commands and enforce best practices across a repository. They are needed when initializing a project or updating safety templates to maintain a hardened baseline.

Stack-specific guards can be applied based on detected stack patterns including Terraform, Docker, Kubernetes, and secrets. The setup reads detection results to install the appropriate templates and rules for your specific stack.

Updating safety templates involves reading the detection cache, installing updated baseline and stack-specific guards, merging settings into project configurations, and recording plugin metadata for traceability to ensure your project stays current.

Configuring project hooks requires no external dependencies, operating independently to read detection caches and install safety templates. It relies solely on the existing project environment to apply baseline and stack-specific rules.

Automated safety guards ensure projects start with a hardened baseline and stay up to date with templates automatically. Unlike manual rules, they block destructive actions and enforce best practices consistently by reading detection caches and merging settings.