lucky-ci-gate-recovery

Diagnose and classify GitHub CI gate failures blocking pull request merges.

17|8|Updated Apr 11, 2022

Search Tags:#automation #troubleshooting #github actions #pr #ci #sonarcloud #dependabot

Ready to run

npx skills add https://github.com/LucasSantana-Dev/Lucky --skill lucky-ci-gate-recovery

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lucky-ci-gate-recovery
Source: https://github.com/LucasSantana-Dev/Lucky/tree/main/.cursor/skills/lucky-ci-gate-recovery
Command: npx skills add https://github.com/LucasSantana-Dev/Lucky --skill lucky-ci-gate-recovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps unblock pull requests that are stuck due to failing CI checks, especially when the failures seem unrelated to the code changes or are specific to automated processes like Dependabot.

Core Features & Use Cases

Diagnose CI Blockers: Identifies the root cause of required check failures on GitHub PRs.
Context Reconciliation: Helps align CI check names with repository ruleset configurations.
Failure Classification: Categorizes failures into specific buckets like token-permission, quality-gate, workflow-runtime, ruleset-mismatch, or deploy-checkout-drift.
Guided Remediation: Provides a sequence of steps to fix common CI gate issues.
Use Case: A Dependabot PR is failing due to a SonarCloud quality gate mismatch, but the code changes are minimal. This Skill can help diagnose if it's a configuration issue or a genuine code quality problem before merging.

Quick Start

Use the lucky-ci-gate-recovery skill to diagnose why pull request number 123 is blocked by required checks.

Frequently Asked Questions about lucky-ci-gate-recovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I fix GitHub CI failures blocking my pull request from merging?▼

To fix GitHub CI failures blocking your pull request, diagnose the root cause by classifying the issue into categories like token permissions, quality gates, or workflow runtime errors, then apply a deterministic remediation checklist to safely unblock the merge.

Why do Dependabot PRs fail SonarCloud quality gate checks despite minimal code changes?▼

Dependabot PRs fail SonarCloud quality gate checks due to contract mismatches between the automated dependency update and the static analysis configuration, requiring context reconciliation to determine if it is a genuine code quality problem or a ruleset mismatch before merging.

How do I reconcile CI check names with GitHub repository ruleset configurations?▼

Reconciling CI check names with GitHub repository ruleset configurations involves aligning the expected required check names in your branch protection rules with the actual names output by your GitHub Actions workflows to resolve ruleset mismatch failures.

What causes deploy checkout drift in GitHub Actions CI pipelines and how do I resolve it?▼

Deploy checkout drift in GitHub Actions CI pipelines occurs when workflow runtime environments use inconsistent repository states during deployment, and you resolve it by diagnosing the workflow runtime errors and aligning the checkout configurations across your jobs.

Can I automate troubleshooting for GitHub Actions PR blocks without manual log inspection?▼

Automating troubleshooting for GitHub Actions PR blocks without manual log inspection is achievable by classifying failures into deterministic buckets like token-permission and quality-gate issues, providing a guided sequence of steps to remediate CI gate failures.

What are the common categories of CI gate failures in GitHub Actions?▼

Common categories of CI gate failures in GitHub Actions include token-permission errors, quality-gate mismatches, workflow-runtime errors, ruleset-mismatches, and deploy-checkout-drift, each requiring specific diagnostic and remediation steps to unblock pull requests.