mcpbeat

Fix CI

microsoft/fix-ci

Fix the failed CI checks for the current session. Use when the user requests a CI fix via the Fix Checks button in the Changes toolbar.

299 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
188278
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/microsoft/vscode --skill fix-ci

The instruction itself

2 sections, as written by the author

<!-- Customize this skill and select save to override its behavior. Delete that copy to restore the built-in behavior. -->

Fix CI

Please fix the failed CI checks for this session immediately.

Use the failed check information provided with this message, including annotations and check output, to identify the root causes and make the necessary code changes.

Workflow

  • Read the failed check information attached to this message. It includes a link to the pull request, and for each failed check the check name, status, conclusion, a details URL, and any annotations or output.
  • Use the annotations and output to identify the root cause of each failure (e.g. compile errors, lint/hygiene violations, failing tests).
  • Make the necessary code changes to resolve the failures. Focus on resolving these CI failures and avoid unrelated changes unless they are required to fix the checks.
  • Validate your changes locally where possible (e.g. compile, lint, run the relevant tests) to confirm the failures are addressed.

How to use it

Copy the folder

Take microsoft/fix-ci from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.