What problem does it solve? GitHub Actions workflows can silently break when a step marked continue-on-error: true is followed by a guard that hard-exits on the same failure: every unprotected step below is skipped, turning teardown, fallback, and reporting steps into unreachable dead code that looks correct on review. ## Core Features & Use Cases - Stranded-step detection: The bundled stranded-steps.py script parses workflow YAML and reports every guard that derives from a continue-on-error step, can exit non-zero, and strands unprotected steps below it, with exact file and line references. - Degradation-path prioritization: Findings where a stranded step reads the same signal the guard fires on are sorted first, surfacing the most likely real defects before correct-by-design cases. - Structured review procedure: The skill walks through classifying each stranded step (teardown, degradation path, report, or intentional skip) and applying one of four resolutions: hard exit in place, !cancelled() protection, deferred guard, or continue-on-error on the guard. - Use Case: When reviewing a pull request that adds an if: condition, a continue-on-error: flag, or a step that exits non-zero in .github/workflows/, run this skill to verify the change does not strand cleanup, fallback, or reporting steps. ## Quick Start Ask the AI to review the workflow changes in this pull request for step-gating defects using the review-step-gating skill.
