New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

CI-Fix Triage Protocol

by dotnet in dotnet/maui

Sets the safety and triage rules for .NET MAUI CI-fixer workflows: classify each ci-scan issue as Continue, Watch, Stop or Skip before proposing any fix.

OfficialMITAuto-check passedDevelopment

Install CI-Fix Triage Protocol

skills CLI
$ npx skills add dotnet/maui --skill ci-fix -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install dotnet/maui ci-fix --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/dotnet/maui.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/ci-fix .claude/skills/ci-fix && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ci-fix
GitHub stars
23k
Token cost
~1.2k tokens
SKILL.md length
693 words
Files
3
Skills in repo
27
Repo updated
First seen
Licence
MIT

At a glance

Sets the safety and triage rules for .NET MAUI CI-fixer workflows: classify each ci-scan issue as Continue, Watch, Stop or Skip before proposing any fix.

  • Works in 4 steps: An open CI-fix PR with the workflow's… → A merged CI-fix PR with that exact… → A closed-unmerged CI-fix PR with that… → …
  • Handling a ci-scan issue that may already have a CI-fix pull request
  • SKILL.md covers Return a decision, Deduplicate without false…, Require current, specific… and Bound autonomous work, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Before proposing a code change, the agent must return exactly one terminal decision per candidate issue, backed by concrete evidence and never revised later in the response. Continue means no dedup or safety gate blocks analysis. Watch means an open workflow-owned CI-fix pull request already owns the issue, and only that PR is advanced. Stop means an explicit human PR owns the issue. Skip covers issues that are stale, visual, already fixed, out of scope or unsafe to advance.

Deduplication relies on exact Refs references: an open CI-fix PR with the workflow's title prefix is the only Watch case, merged or closed-unmerged CI-fix PRs lead to Skip, and an open human PR that declares it fixes the issue, through a Refs line or a closing keyword, leads to Stop. A bare issue number in a comment, check summary, commit message or diff does not count as ownership. The skill ships two eval files under tests and leaves branch names, labels, attempt limits and write permissions to the calling workflow.

When your agent uses it

  • Handling a ci-scan issue that may already have a CI-fix pull request
  • Deciding whether a human pull request already owns a tracking issue
  • Running a scheduled sweep of ci-scan issues
  • Advancing a manual single-issue CI-fix dispatch safely

Example prompts

  • “Classify this ci-scan issue as Continue, Watch, Stop or Skip and show the ownership evidence.”
  • “Check whether a human pull request already claims this CI failure before we open a CI-fix PR.”
  • “Run the scheduled sweep over open ci-scan issues and report one decision for each.”
  • “A merged CI-fix PR references this issue, so decide whether new evidence justifies another attempt.”

Requirements

  • GitHub access to the dotnet/maui repository

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. An open CI-fix PR with the workflow's title prefix and exact `Refs
  2. A merged CI-fix PR with that exact reference is a Skip case until current
  3. A closed-unmerged CI-fix PR with that exact reference is a Skip case. A
  4. An open human PR is always a Stop case when its own title or body

What it can do on your machine

Read from SKILL.md and the folder at commit 7d38fd0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

CI-Fix Triage Protocol loads about 1.2k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 693 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~82
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from dotnet/maui at commit 7d38fd0, republished under its MIT licence (© dotnet). 693 words, ~1,233 tokens.

Download SKILL.mdSave it as .claude/skills/ci-fix/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
ci-fix
description
Common safety and triage protocol for .NET MAUI CI-fixer workflows. Use whenever investigating, creating, or advancing a `[ci-fix]` or `[ci-fix-net11]` pull request from a `ci-scan` issue, including frozen ownership snapshots, Continue/Watch/Stop/Skip classification, manual single-issue dispatches, and scheduled sweeps.

CI-fix triage protocol

Use this protocol before proposing a code change or emitting a CI-fixer safe output. The calling workflow supplies its branch, labels, title prefix, attempt limit, and allowed write surface; preserve those caller-specific restrictions.

Return a decision

For each candidate, state one terminal decision before taking an action:

  • Decision: Continue — no dedup or safety gate blocks current-evidence analysis.
  • Decision: Watch — exclusively an open workflow-owned CI-fix PR owns the issue; advance only that PR.
  • Decision: Stop — an explicit human PR owns the issue; do not monitor it or plan a fallback CI-fix PR.
  • Decision: Skip — the issue is stale, visual, already fixed, out of scope, or cannot be safely advanced.

Explain the concrete evidence for the decision. A search result is evidence to inspect, not a decision by itself.

Reason through all ownership evidence before emitting the decision. Return exactly one terminal decision; never emit a provisional decision and then correct it later in the response.

When the caller requests a strict decision format, complete the classification before writing any response text. Emit only the final decision and requested next action. Do not include a draft, correction, or alternate decision.

Deduplicate without false ownership

  1. An open CI-fix PR with the workflow's title prefix and exact Refs: dotnet/maui#<issue> is the only Watch case. Never open a second CI-fix PR for that issue.
  2. A merged CI-fix PR with that exact reference is a Skip case until current evidence establishes a new regression.
  3. A closed-unmerged CI-fix PR with that exact reference is a Skip case. A human closing the PR is a stop signal for the keep-one-PR loop.
  4. An open human PR is always a Stop case when its own title or body explicitly declares that it addresses the tracking issue. Do not monitor it or plan a fallback CI-fix PR. Accept a Refs: declaration or a closing/reference keyword such as Fix, Fixes, Fixed, Close, Closes, Closed, Resolve, Resolves, or Resolved followed by the issue reference, including #<issue>, dotnet/maui#<issue>, or https://github.com/dotnet/maui/issues/<issue>.

GitHub search normally includes comments and incidental status text. Do not treat a raw issue number in a comment, check summary, commit message, diff, or unrelated list as human ownership. Inspect the PR title and body before stopping. If every result is incidental, return Decision: Continue; an unrelated search hit is not independently a reason to Stop or Skip.

Show full SKILL.md (301 more words)Show less

Require current, specific evidence

Before a fresh attempt:

  1. Confirm the issue is in the caller's branch and label scope.
  2. Skip screenshot and visual-regression failures; do not modify baselines.
  3. Verify the cited failure still reproduces on the latest completed base-branch build. A historical failure alone is not a reason to create a PR.
  4. Trace the exact failing test, platform path, and deepest relevant stack frame. Check whether an intervening merged PR already fixed that path before proposing a duplicate or adjacent workaround.
  5. Preserve the test's assertion. Do not mute, ignore, retry, weaken, or extend a timeout to hide a failure. A legitimate de-flake makes the state transition or synchronization deterministic.

Bound autonomous work

Advance only the existing CI-fix PR and respect the caller's effective attempt counter. When the cap is reached, return Decision: Skip and defer rather than advancing the existing PR or opening a replacement. Never claim the target test is fixed from a category-level result or an unrelated green leg; require evidence for the specific test on the CI-fix PR's current head.

Fail closed at the write boundary

Before any code-push safe output, apply the caller's transport gate to the saved base and head. Reject transport unless the saved base is an ancestor, all new commits are append-only and merge-free, and the complete diff stays within the caller's allowed paths, commit count, file count, and patch-byte bounds. Never trim, conceal, or retry an unrelated or oversized diff merely to make it pass.

If a supported safe-output call returns a backend, connection, or validation error, do not retry that mutation, continue the remaining mutation set, emit a noop, or use a direct write path. Request one bounded report_incomplete safe output and stop. A missing expected safe output is a failed/incomplete run, not a successful no-write result.

© dotnet, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files in .github/skills/ci-fix of dotnet/maui.

  • SKILL.md
  • tests/eval.ownership.vally.yaml
  • tests/eval.vally.yaml

Open the folder on GitHubat commit 7d38fd0

Compare with similar skills

CI-Fix Triage Protocol next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

CI-Fix Triage Protocol compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
CI-Fix Triage Protocol this skilldotnet/maui23k—~1.2kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Exposed Bug Fix WorkflowJetBrains/Exposed9.3k—~3.8kAutomated safety check: PassApache-2.0
Pull Request Babysitterthedotmack/claude-mem97k—~1.1kAutomated safety check: PassApache-2.0
Pre-Release PR Triagejamiepine/voicebox57k—~3.1kAutomated safety check: PassMIT
Ouroboros Maintainer TriageQ00/ouroboros6.2k—~1.7kAutomated safety check: PassMIT

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Exposed Bug Fix Workflow

    JetBrains/Exposed

    Official

    Takes a GitHub or YouTrack issue for the Exposed project through reproduction, a failing test, a fix, validation and a pull request.

    9.3k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Pull Request Babysitter

    thedotmack/claude-mem

    Keeps watching a pull request, fixing real review and CI problems and resolving stale threads, until it is clean and ready to merge.

    97k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed

  • Pre-Release PR Triage

    jamiepine/voicebox

    Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.

    57k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check passed

  • Ouroboros Maintainer Triage

    Q00/ouroboros

    Triages and works through GitHub issues and pull requests in the Q00/ouroboros repo as a maintainer, within a stated review boundary and clear limits on what it may change.

    6.2k GitHub stars~1.7k tokensUpdated today
    DevelopmentAuto-check passed

  • PR Triage

    rtk-ai/rtk

    Audits a repository's open pull requests, deep-reviews chosen ones and drafts review comments that are only posted after you approve them.

    83k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check: notes

More from dotnet/maui

All 27 skills in this repo

  • Copilot Session Failure Analysis

    dotnet/maui

    Official

    Mines local Copilot CLI session logs for dotnet/maui to rank costly or failing runs, tag recurring failure modes, propose repo edits and emit guard evals.

    23k GitHub stars~3.4k tokensUpdated today
    Auto-check passed

  • Evaluate PR Tests

    dotnet/maui

    Official

    Reviews the tests added in a pull request for fix coverage, quality, edge cases and test type, and recommends lighter test types where they would do.

    23k GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • .NET MAUI Release Readiness

    dotnet/maui

    Official

    Produces evidence-backed ship-readiness verdicts for .NET MAUI Servicing Releases and Previews, and drafts public-safe release handoff pages from the result.

    23k GitHub stars~15k tokensUpdated today
    Auto-check passed

  • MAUI PR Performance Analysis

    dotnet/maui

    Official

    Interprets pinned managed benchmark evidence for a dotnet/maui pull request and writes a narrative for the performance review workflow, without running or publishing anything.

    23k GitHub stars~2.4k tokensUpdated today
    Auto-check passed

  • PR Finalize

    dotnet/maui

    Official

    Checks that a pull request's title and description match its implementation and reviews the code for best practices before merge, without posting anything.

    23k GitHub stars~3.1k tokensUpdated today
    Auto-check passed

  • .NET MAUI Dependency Flow Guide

    dotnet/maui

    Official

    Adds MAUI-specific guardrails on top of the maestro-cli skill and Maestro MCP tools for darc, BAR, and channel or feed lookups in dotnet/maui.

    23k GitHub stars~10k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about CI-Fix Triage Protocol

What does CI-Fix Triage Protocol do?

Sets the safety and triage rules for .NET MAUI CI-fixer workflows: classify each ci-scan issue as Continue, Watch, Stop or Skip before proposing any fix. Before proposing a code change, the agent must return exactly one terminal decision per candidate issue, backed by concrete evidence and never revised later in the response. Continue means no dedup or safety gate blocks analysis.

When should I use CI-Fix Triage Protocol?

CI-Fix Triage Protocol fits situations like: handling a ci-scan issue that may already have a CI-fix pull request; deciding whether a human pull request already owns a tracking issue; running a scheduled sweep of ci-scan issues; advancing a manual single-issue CI-fix dispatch safely.

How do I install CI-Fix Triage Protocol in Claude Code?

Run `npx skills add dotnet/maui --skill ci-fix -a claude-code`. Or copy the skill folder (.github/skills/ci-fix in dotnet/maui) into .claude/skills/ci-fix in your project. Claude Code loads it when a task matches its description.

How do I install CI-Fix Triage Protocol in Codex?

Run `npx skills add dotnet/maui --skill ci-fix -a codex`. Or copy the skill folder (.github/skills/ci-fix in dotnet/maui) into .agents/skills/ci-fix in your project. Codex loads it when a task matches its description.

Can I use CI-Fix Triage Protocol in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dotnet/maui --skill ci-fix -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ci-fix, .gemini/skills/ci-fix, .github/skills/ci-fix and .opencode/skills/ci-fix in your project.

What does CI-Fix Triage Protocol need to run?

SKILL.md names no scripts, command-line tools or credentials: CI-Fix Triage Protocol is instructions for the agent only. Our summary lists: GitHub access to the dotnet/maui repository.

Does CI-Fix Triage Protocol access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is CI-Fix Triage Protocol safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does CI-Fix Triage Protocol use?

CI-Fix Triage Protocol is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does CI-Fix Triage Protocol use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to CI-Fix Triage Protocol?

Skills that share tags, products or a category with CI-Fix Triage Protocol: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Exposed Bug Fix Workflow (JetBrains/Exposed, 9.3k stars), Pull Request Babysitter (thedotmack/claude-mem, 97k stars) and Pre-Release PR Triage (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains CI-Fix Triage Protocol?

dotnet (a GitHub organization, an official publisher) maintains it in dotnet/maui, which has 23,322 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on October 7, 2026.

Source: dotnet/maui on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.