skywatch-fixing-osprey-rules

Resolve Osprey SML validation errors by diagnosing root causes and applying structured fix patterns. The skill categorizes failures like type mismatches and import cycles, guiding dependency-ordered debugging using the osprey-cli.

Osprey SML validation fails with undefined variables due to root causes like import cycles or type mismatches. Categorize the error and apply dependency-ordered debugging to resolve the primary issue and pass re-validation.

The best way to debug cascading SML validation failures is dependency-ordered debugging. Identify the primary root cause, apply structured remediation patterns, and iteratively re-validate using the osprey-cli until rule integrity is restored.

Yes, the osprey-cli is required to resolve SML rule validation issues. The remediation workflow relies on iterative re-validation using the osprey-cli to confirm that applied fix patterns successfully clear the validation checks.

Yes, you can use automated debugging to fix Osprey type mismatches and import cycles. The skill automatically categorizes these root causes and provides step-by-step remediation patterns to resolve them during rule-writing workflows.