keystone:new-sensor

Automated sensor creation is handled by generating a new sensor at the canonical path with the necessary configurations, reducing manual setup. You can run the command 'keystone new sensor <name> [--kind <kind>]' to quickly add the automated check.

Computational and inferential sensor types represent the two kinds of automated checks you can select when creating a sensor. You specify the desired kind using the --kind flag to determine the logic type for your repository-level charter engineering.

Adding a new automated check requires running the 'keystone new sensor <name>' command. This generates the sensor at the correct path within the charter system, streamlining the setup for checks like unit-test runners or security reviews.

No dependencies are required to set up automated checks for charter engineering. The sensor creation process operates independently using its internal scripts to generate the necessary configurations at the canonical path.

Yes, you can generate sensors for repository-level code quality checks. The tool is specifically intended for charter engineering, allowing you to automate the setup of various development checks directly within your repository structure.

The best way to streamline the setup of automated checks is to use a command-line generation tool. Running 'keystone new sensor <name>' for each check automates the configuration file creation, eliminating repetitive manual path setup.