checks-phase

Review and fix failed CI/CD checks to achieve merge readiness.

Updated Aug 27, 2026

Search Tags:#automation #testing #linting #debugging #deployment #CI/CD #build

Ready to run

npx skills add https://github.com/marcusgoll/robinhood-algo-trading-bot --skill checks-phase

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: checks-phase
Source: https://github.com/marcusgoll/robinhood-algo-trading-bot/tree/main/.claude/skills/checks-phase
Command: npx skills add https://github.com/marcusgoll/robinhood-algo-trading-bot --skill checks-phase

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes references (resource) components.

What problem does it solve?

This Skill addresses the common frustration of CI/CD pipeline failures that block pull requests and delay deployments, providing a systematic approach to resolution.

Core Features & Use Cases

Failure Review & Categorization: Helps you quickly review and categorize failed CI/CD checks (e.g., linting, tests, build, deploy config).
Systematic Issue Fixing: Guides you through a structured process to fix issues, ensuring thoroughness and preventing recurrence.
Re-run & Verification: Facilitates re-running checks and verifying that all issues are resolved before merging.
Use Case: When your pull request fails CI checks, use this Skill to identify if it's a syntax error, a broken test, or a deployment configuration issue, apply the necessary code changes, and re-run the pipeline until all checks pass, allowing for a confident merge.

Quick Start

1. Review failed checks in your CI/CD pipeline output

2. Categorize failures (e.g., linting, tests, build, deploy config)

3. Fix issues systematically in your code

4. Re-run checks (e.g., push a new commit to your PR branch)

5. Verify all checks pass before merging

Frequently Asked Questions about checks-phase

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

FAQPage Schema

How do I fix CI/CD pipeline failures blocking my pull request merge?▼

CI/CD failures block merges when linting, tests, build, or deployment checks fail. Review the failed check output, categorize the issue type, fix the underlying code or configuration, push a new commit to re-run checks, and verify all pass before merging.

What's the best way to diagnose and resolve linting and test failures in a PR workflow?▼

Systematically review failed CI checks to identify whether issues are linting errors, broken tests, or build configuration problems. Fix each categorized issue in your code, commit changes, and re-run the pipeline until all checks pass.

Can I use this approach with multiple CI/CD check types across my deployment pipeline?▼

Yes. This approach handles linting, tests, build failures, and deployment configuration issues simultaneously, allowing you to identify, fix, and verify all blockers across your entire CI/CD pipeline in one workflow.

How do I verify that all CI/CD checks pass before merging a pull request?▼

After applying fixes and pushing commits, monitor your CI/CD pipeline output to confirm all linting, test, build, and deployment checks complete successfully. Merge only when all checks pass.

What types of CI/CD failures can this approach resolve?▼

This approach resolves linting errors, failed tests, build configuration issues, and deployment configuration failures. It categorizes each failure type and guides systematic fixes to achieve merge readiness.