Agents & OrchestrationSûr9292/100

Gh Fix Ci (Alibaba)

Debug and fix failing GitHub PR checks for xquic. Use when a PR, branch, or commit has failed CI, GitHub Actions, build checks, test checks, or requested validation failures that should be diagnosed from logs before editing.

ou envoie-le directement à ton agent.

Installer dans ton projet

$ curl -fsSL https://arboristhree.xyz/cli/install-skill.mjs -o /tmp/arboris-install-skill.mjs && node /tmp/arboris-install-skill.mjs gh-fix-ci__alibaba-xquic__harness-skills-a6ae9a988921
Alibaba
alibaba/xquic
Contenu à copier
---
name: gh-fix-ci
description: Debug and fix failing GitHub PR checks for xquic. Use when a PR, branch, or commit has failed CI, GitHub Actions, build checks, test checks, or requested validation failures that should be diagnosed from logs before editing.
metadata:
  origin: Alibaba
---

# GitHub Fix CI

## Workflow

1. Identify the exact failing check, run ID, job, command, and commit SHA. Use GitHub tools or `gh` when available.
2. Read logs before editing. Capture the first failing command and the most relevant error lines.
3. Map the failure to source using `harness/spec/harness-manifest.yml` and read the required docs before changing code.
4. Inspect the real code path or build/test script that produced the failure.
5. Make the smallest fix that addresses the confirmed cause. Preserve unrelated local edits and staged state.
6. Re-run local validation using `scripts/validate.sh` and `harness/skills/validate/SKILL.md` when feasible. If CI-only, explain why local validation is not equivalent.
7. Report the failing command, cause, changed files, validation result, and any checks that still need remote rerun.

## Guardrails

- Do not guess from check names; logs are required evidence.
- Do not paper over test failures by weakening assertions unless the expected behavior is proven wrong.
- Do not run destructive Git commands unless the user explicitly asks and local changes are preserved.
- Do not push fixes without showing the commit/push scope and receiving confirmation, unless the user already requested push in the same task.
Colle ce Markdown dans ton agent ou utilise les boutons ci-dessus pour l’écrire dans ton projet.

Ce que fait Gh Fix Ci (Alibaba)

Do not guess from check names; logs are required evidence.
Do not paper over test failures by weakening assertions unless the expected behavior is proven wrong.
Do not run destructive Git commands unless the user explicitly asks and local changes are preserved.
Do not push fixes without showing the commit/push scope and receiving confirmation, unless the user already requested push in the same task.

Comment utiliser Gh Fix Ci (Alibaba)

1
Copie le prompt
Un clic copie le prompt packagé (ou l'envoie à ton agent).
2
L'agent installe le skill
Il ajoute le SKILL.md et ses ressources à ton projet.
3
Activation automatique
Le skill s'active dès que le contexte correspond.

Déclencheurs pour Gh Fix Ci (Alibaba)

Dis simplement à ton agent quelque chose comme :

Applique le skill gh-fix-ci__alibaba-xquic__harness-skills-a6ae9a988921 à cette tâche
Utilise gh-fix-ci__alibaba-xquic__harness-skills-a6ae9a988921 pour améliorer cette implémentation
Passe en revue ce sujet avec gh-fix-ci__alibaba-xquic__harness-skills-a6ae9a988921

Skills liés à Gh Fix Ci (Alibaba)