CI Check Fixer
Diagnose failed CI checks from their annotations and output, then repair the current session’s code.
The skill is scoped to failed CI checks in the current session and asks to avoid unrelated changes; no malware, credential theft, or covert exfiltration is indicated. However, it demands immediate edits without user confirmation, explicit permission boundaries, sensitive-log handling, rollback guidance, or data-flow disclosure, so points are deducted.
The workflow is internally coherent: read check information, identify causes, edit code, and validate locally where possible. It lacks handling for missing or malformed input, concrete validation commands, failure feedback, and a stop condition when reproduction is impossible; static calibration caps the score at 10.
The trigger and goal are reasonably specific: use the Fix Checks button in the Changes toolbar to repair CI for the current session. However, non-fit cases, input schema, output expectations, permission requirements, and environment coverage are unspecified, including Chinese-language support and mainland-China reachability.
The name, description, and workflow are consistent, concise, and readable. Repository evidence supplies MIT licensing, Microsoft attribution, and version information, but the skill lacks dependency or installation notes, examples, FAQs, known limitations, changelog/versioning details, and a clear maintenance path.
It plausibly covers the core path from CI diagnostics through code changes and local validation, while emphasizing focus on the reported failures. It provides no concrete tool commands, output format, representative verified results, or comparison with alternatives, and “where possible” validation may leave fixes unconfirmed; static calibration caps the score at 7.
Failed checks are described as containing status, detail links, annotations, and output, providing some traceability. The repository also contains real CI workflows and tests, but they do not establish coverage of this skill’s execution path, and the skill has no reproducible tests of its own; static calibration caps the score at 5.
- Immediate code changes lack confirmation and rollback requirements; the agent should summarize the intended scope and seek confirmation for high-impact edits.
- The skill does not define handling for missing CI data, sensitive log content, inability to reproduce locally, or failed validation.
- Commands, output format, environment dependencies, and non-fit scenarios are unspecified; Chinese-user and mainland-China network support cannot be established from the supplied material.
What does this skill do, and when should you use it?
This skill is designed to fix failed CI checks for the current session. It reads the supplied check status, conclusion, details URL, annotations, and output to identify root causes. It then makes the code changes needed to address issues such as compile errors, lint or hygiene violations, and failing tests. Where practical, it validates the changes locally, without naming a specific CI platform.
Reads the failed CI information attached to the current session, including the pull request link, check name, status, conclusion, details URL, annotations, and output; analyzes the root causes; makes the necessary code changes; and, when possible, performs local compilation, linting, or relevant test validation.
- A developer clicks Fix Checks in the Changes toolbar and needs to resolve the current session’s failed CI checks.
- A maintainer receives a pull request failure with check output and annotations and needs to fix compile errors.
- A contributor needs to address lint or code-hygiene violations reported by CI.
- A developer wants to modify code after a CI test failure and run relevant local validation.
What are this skill's strengths and limitations?
- Focuses diagnosis on the annotations and output from failed checks.
- Covers common causes including compile errors, lint or hygiene violations, and failing tests.
- Calls for local validation where possible and limits unrelated changes.
- Depends on complete failed-check information being attached to the current session.
- The SKILL.md does not identify supported CI services or platforms.
- Local validation is conditional and no fixed validation commands are provided.
- The README does not document standalone installation for this skill.
How do you install this skill?
The skill is located at src/vs/sessions/skills/fix-ci/SKILL.md in the VS Code repository. The README says the repository bundles 61 skills, but it does not document a separate installation command or procedure for this skill.
How do you use this skill?
In a current session containing failed CI check information, click Fix Checks in the Changes toolbar. Example trigger: "Fix the failed CI checks for the current session." Include the failed check annotations and output so the skill can analyze and repair the code.