How do I install the Github Actions Debug skill?

Run npx skillmds@latest add rivie13-phoenix-agentic-engine-interface/github-actions-debug in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Github Actions Debug safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Github Actions Debug?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Github Actions Debug free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Github Actions Debug?

rivie13 (@rivie13-phoenix-agentic-engine-interface) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Github Actions Debug by rivie13-phoenix-agentic-engine-interface

Name: Github Actions Debug
Rating: 4.2 (5 reviews)
Author: rivie13

Github Actions Debug

Debug failed GitHub Actions CI/CD workflow runs. Use when user asks to fix CI, debug a failed workflow, check why a build failed, investigate GitHub Actions errors, or troubleshoot pipeline failures.

rivie13 Updated Sep 10, 2026

File contents

GitHub Actions Debug — Phoenix Agentic Engine Interface

Repo Context

Owner: rivie13
Repo: Phoenix-Agentic-Engine-Interface
Type: Public (TS SDK + Contracts)

Workflows in this repo

Workflow file	Purpose
`ci.yml`	Typecheck (tsc) + Test (vitest) on push/PR to main

CI Pipeline Details

The ci.yml workflow runs:

Checkout code
Setup Node.js 20 with npm cache
Install dependencies: npm ci
Typecheck: npm run typecheck
Test: npm test

Debugging Workflow: Step-by-step

Step 1: List recent workflow runs

mcp_github_github_actions_list(owner="rivie13", repo="Phoenix-Agentic-Engine-Interface")

Step 2: Get details of a specific run

mcp_github_github_actions_get(owner="rivie13", repo="Phoenix-Agentic-Engine-Interface", run_id=<RUN_ID>)

Step 3: Get job logs for the failed job

mcp_github_github_get_job_logs(owner="rivie13", repo="Phoenix-Agentic-Engine-Interface", job_id=<JOB_ID>)

Step 4: Analyze the failure

Common failure patterns:

Failure type	Typical cause	Fix
TypeScript error	Type mismatch, missing type annotations	Run `npm run typecheck` locally
Vitest failure	Test assertion error, fixture drift	Run `npm test` locally
Contract fixture mismatch	Fixture JSON doesn't match Zod schema	Sync fixtures with backend golden tests
`npm ci` failure	Lock file out of sync	Run `npm install` and commit `package-lock.json`
`any` type flagged	Strict mode violation	Replace `any` with proper types

Step 5: Fix locally and verify

Read the error from the job logs
Run locally:
- npm run typecheck — reproduce type errors
- npm test — reproduce test failures
Make the fix
Run both typecheck and test to confirm

Step 6: Re-trigger the workflow (optional)

mcp_github_github_actions_run_trigger(owner="rivie13", repo="Phoenix-Agentic-Engine-Interface", workflow_id="ci.yml")

---name: github-actions-debugdescription: Debug failed GitHub Actions CI/CD workflow runs. Use when user asks to fix CI, debug a failed workflow, check why a build failed, investigate GitHub Actions errors, or troubleshoot pipeline failures.---# GitHub Actions Debug — Phoenix Agentic Engine Interface## Repo Context- **Owner**: `rivie13`- **Repo**: `Phoenix-Agentic-Engine-Interface`- **Type**: Public (TS SDK + Contracts)## Workflows in this repo| Workflow file | Purpose ||---------------|---------|| `ci.yml` | Typecheck (tsc) + Test (vitest) on push/PR to main |## CI Pipeline DetailsThe `ci.yml` workflow runs:1. **Checkout** code2. **Setup Node.js** 20 with npm cache3. **Install dependencies**: `npm ci`4. **Typecheck**: `npm run typecheck`5. **Test**: `npm test`## Debugging Workflow: Step-by-step### Step 1: List recent workflow runs```mcp_github_github_actions_list(owner="rivie13", repo="Phoenix-Agentic-Engine-Interface")```### Step 2: Get details of a specific run```mcp_github_github_actions_get(owner="rivie13", repo="Phoenix-Agentic-Engine-Interface", run_id=<RUN_ID>)```### Step 3: Get job logs for the failed job```mcp_github_github_get_job_logs(owner="rivie13", repo="Phoenix-Agentic-Engine-Interface", job_id=<JOB_ID>)```### Step 4: Analyze the failureCommon failure patterns:| Failure type | Typical cause | Fix ||-------------|---------------|-----|| TypeScript error | Type mismatch, missing type annotations | Run `npm run typecheck` locally || Vitest failure | Test assertion error, fixture drift | Run `npm test` locally || Contract fixture mismatch | Fixture JSON doesn't match Zod schema | Sync fixtures with backend golden tests || `npm ci` failure | Lock file out of sync | Run `npm install` and commit `package-lock.json` || `any` type flagged | Strict mode violation | Replace `any` with proper types |### Step 5: Fix locally and verify1. Read the error from the job logs2. Run locally: - `npm run typecheck` — reproduce type errors - `npm test` — reproduce test failures3. Make the fix4. Run both typecheck and test to confirm### Step 6: Re-trigger the workflow (optional)```mcp_github_github_actions_run_trigger(owner="rivie13", repo="Phoenix-Agentic-Engine-Interface", workflow_id="ci.yml")```

Frequently asked questions