# CI Workflow Debug

> CI Workflow Debug is an Agent Skill for devops & security published in the fossasia/visdom repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Diagnose and fix GitHub Actions workflow failures. Use when CI jobs fail for lint, tests, JS build updates, or release automation.

- Skill name: `ci-workflow-debug`
- Category: [DevOps & Security](https://www.openparable.com/skill/devops-security/1)
- Source: https://github.com/fossasia/visdom/blob/HEAD/.agents/skills/ci-workflow-debug/SKILL.md
- Repository: fossasia/visdom (10,264 GitHub stars when collected)

## SKILL.md

# Skill: CI Workflow Debugging

## When to Use

Use this skill when pull requests fail checks or automation jobs.

## Core Workflow

1. Identify failing job scope (lint, tests, build artifacts, release pipeline).
2. Reproduce failure locally with matching commands.
3. Fix root cause while preserving existing workflow intent.
4. Confirm related jobs are not impacted by the fix.
5. Keep automation assumptions aligned with repository policies.

## Guardrails

- Do not patch around failures by weakening tests/lints.
- Keep release and JS auto-build workflows intact.
- Avoid introducing branch- or actor-specific CI logic hacks.

## Documentation

- [Skill reference](references/REFERENCE.md)
- `.github/workflows/`
- `package.json`
- `test-requirements.txt`
- `AGENTS.md`
- `CONTRIBUTING.md`

## Assets

- See `assets/README.md` and store templates/resources in `assets/`.

## Tests

- Follow the default flow in `references/TESTS.md`.

---

Source: https://www.openparable.com/skill/devops-security/ci-workflow-debug (OpenParable). Cite the canonical URL above.