dart-fix-ci
GitHub用于调试和修复 DART 项目中任意基础分支上的 CI 失败。支持自动识别分支、检查日志、本地复现问题并应用最小化修复，特别针对 release 分支提供 cherry-pick 策略，确保 CI 状态恢复绿色。
Trigger Scenarios
Install
npx skills add dartsim/dart --skill dart-fix-ci -g -y
SKILL.md
Frontmatter
{
"name": "dart-fix-ci",
"description": "DART Fix CI: debug and fix failing CI checks on any base branch"
}
dart-fix-ci
Use this skill in Codex to run the DART dart-fix-ci workflow. The editable
workflow source lives in .claude/commands/; this file is its generated adapter
in the shared .agents/skills/ catalog.
Invocation
- Claude Code/OpenCode:
/dart-fix-ci <arguments> - Codex:
$dart-fix-ci <arguments>
Treat the text after the skill name as $ARGUMENTS. When the workflow
references $1, $2, etc., map those to the positional values supplied by the
user.
Command Body
Fix CI failure: $ARGUMENTS
Required Reading
@AGENTS.md @docs/onboarding/ci-cd.md @docs/onboarding/release-management.md
Workflow
For a failure involving model/scene structure, physics behavior, or GUI output,
use dart-verify-sim to reproduce the claim with text and assessed visual
evidence. Document a visual exception when the relevant renderer is unavailable
or not applicable.
- Identify the base branch. Default to
main; usebase=<branch>from$ARGUMENTSor the PR's own base when it is arelease-*branch. For arelease-*base, also readdocs/onboarding/release-management.mdand apply the release caveats called out below. - Identify failing checks:
gh pr checks <PR_NUMBER>orgh run view <RUN_ID>. - Inspect the first real failure:
gh run view <RUN_ID> --log-failed gh run view <RUN_ID> --job <JOB_ID> --log - If a job is still in progress, wait for logs instead of guessing.
- Choose where to fix. Check whether an equivalent fix already exists on
main. If continuing an existing PR, fetch and check out that PR branch instead of creating a new one. For arelease-*base, branch from the release branch and prefer cherry-picking the provenmainfix; keep any new fix release-scoped and minimal:git fetch origin <RELEASE_BRANCH> git checkout -B fix/<issue>-<release-branch> origin/<RELEASE_BRANCH> - Reproduce locally with the smallest relevant command:
- formatting:
pixi run lint - tests:
pixi run test,pixi run test-unit, or another existing focusedpixi run ...test task - coverage: add targeted tests for uncovered changed lines
- formatting:
- Fix the root cause with minimal scope. Explain why the failure was not caught earlier and whether workflow coverage should change.
- If the failure is infrastructure-only, ask for explicit maintainer/user
approval before rerunning the failed job or running:
gh run rerun <RUN_ID> --failed - Ask for explicit maintainer/user approval before pushing, CI re-triggers, or
other GitHub mutations; after approval, push and watch CI until green. For a
release-*base, use the current release milestone and the PR template when creating or updating the release-branch PR.
Output
- Root cause
- Fix or rerun action
- Commands run
- PR URL, when a PR was created or updated
- Current CI status
- Prevention recommendation, if any
Version History
- b9fbefc Current 2026-07-19 11:29
