skywatch-osprey-validate

Validating SML rules without deployment involves executing an automated dry-run push command using the osprey-cli tool. This checks syntactical and logical integrity to catch configuration errors early before any production push occurs.

Yes, validating SML rules requires local access to the osprey-for-atproto repository. The validation process intelligently resolves paths between your rules project and this repository to execute the dry-run successfully.

Yes, the Osprey rules engine validation requires the uv environment manager. It utilizes uv to manage dependencies and execute the shell commands necessary for running the osprey-cli dry-run validation process.

An SML rules dry-run is an automated validation process that executes push commands with a dry-run flag to test rule integrity. You should use it when modifying SML rules to verify them against the current environment without affecting production.

Osprey SML rules validation may fail if the required osprey-for-atproto repository is not accessible locally. The tool intelligently locates this repository path alongside your rules project to execute the dry-run validation correctly.