Github Ci Debug logo

Github Ci Debug

CommunityPopular
Devin-AXIS
github-ci-debug

Diagnose failing GitHub Actions runs from bounded run, job, and step evidence, propose a focused fix, and modify the local checkout only when the requested task includes implementation.

Overview

PublisherDevin-AXIS
RepositoryiPolloWork
Skill namegithub-ci-debug
Stars
6.3K
Forks
1.2K
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Devin-AXIS on GitHub. Read the source before you install it.

Installation

Install the Github Ci Debug AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork.git /tmp/iPolloWork
mkdir -p .claude/skills
cp -r /tmp/iPolloWork/examples/plugin-packages/github/skills/github-ci-debug .claude/skills/github-ci-debug
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Github Ci Debug in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Github Ci Debug on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Github Ci Debug is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

GitHub CI Debug

Use this skill only for GitHub Actions failures.

Workflow

  1. Resolve the repository and Actions run ID from the supplied URL, PR, or current branch context.
  2. Call actions-failure through the connected GitHub service.
  3. Report the run URL, failing jobs, failing steps, and the most likely root cause supported by the returned evidence.
  4. If the check belongs to an external provider, report its URL and do not pretend the GitHub service controls it.
  5. Propose the smallest fix tied directly to the failing step.
  6. When the user asked for a fix, implement it locally and run the relevant local check.
  7. Summarize remaining uncertainty and what needs a remote rerun.

Guardrails

  • Do not rerun or cancel workflows; those actions are not part of this plugin version.
  • Do not claim complete log coverage when the service returned only job and step summaries.
  • Do not change code when the evidence points to an unrelated infrastructure or flaky failure unless the user chooses that scope.

Frequently asked questions

What does the Github Ci Debug AI skill do?

Diagnose failing GitHub Actions runs from bounded run, job, and step evidence, propose a focused fix, and modify the local checkout only when the requested task includes implementation.

Why use Github Ci Debug on TypingMind?

Because you install it once and use it with any model. Github Ci Debug is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Github Ci Debug in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Devin-AXIS/iPolloWork/tree/main/examples/plugin-packages/github/skills/github-ci-debug. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Github Ci Debug?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Github Ci Debug?

As many as you like. As long as a model supports skills, you can use Github Ci Debug with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Github Ci Debug AI skill free?

It is published on GitHub by Devin-AXIS. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇