doctorbot-ci-validator

What This Skill Does

DoctorBot CI Validator is a specialized diagnostic engine designed for OpenClaw agents to perform offline, deterministic validation of CI/CD configuration files. Instead of waiting for a remote server to reject your pipeline, this skill uses advanced mocking techniques to check your GitHub Actions, GitLab CI, and Keep (AIOps) workflows for schema errors, syntax mismatches, and structural flaws. By operating entirely offline, it eliminates the need for live database connections or network overhead, providing instantaneous feedback on whether your automation scripts will succeed or fail.

Installation

To integrate this tool into your OpenClaw environment, execute the following command in your terminal:

openclaw install openclaw/skills/skills/bamontejano/skill-doctorbot-ci-validator

Once installed, the tool adds validate_keep.py and validate_yaml.py to your local environment, allowing your agent to interface with them directly through CLI commands.

Use Cases

This skill is indispensable for DevOps engineers and automation developers. Key use cases include:

• Pre-commit Automation: Integrate the validator into your local git hooks to ensure no broken YAML is ever committed to a repo.
• Agentic Code Review: Allow your AI agent to self-correct its generated workflow code by validating it against the schema before presenting the file to you.
• AIOps Configuration: Use the specialized Keep workflow mocker to test complex monitoring logic without needing to simulate a live production environment.

Example Prompts

1. "Validate the entire .github/workflows directory and list any syntax errors found."
2. "Check my new Keep workflow located at './alerts/disk-space.yaml' to ensure all providers are properly defined."
3. "The pipeline failed in production; can you use the CI validator to dry-run the config and tell me exactly which line is causing the schema violation?"

Tips & Limitations

• Tip: Always run the validator against directories rather than single files to ensure that cross-file dependencies in your CI logic are also checked.
• Tip: Combine this with a linter for even higher confidence in your code quality.
• Limitation: As an offline validator, it cannot verify the availability of external network services or the actual state of production databases. It checks structural and logical correctness rather than integration success. It is not a replacement for full-environment integration testing.