Agent-Skills.md

Agent Skills: dart-fix-ci

DART Fix CI: debug and fix failing CI checks

UncategorizedID: dartsim/dart/dart-fix-ci

Repository

dartsim/dart
dartsimLicense: BSD-2-Clause
1,212304

Install this agent skill to your local

pnpm dlx add-skill https://github.com/dartsim/dart/tree/HEAD/.agents/skills/dart-fix-ci

Skill Files

Browse the full folder contents for dart-fix-ci.

Download Skill

Loading file tree…

.agents/skills/dart-fix-ci/SKILL.md

Skill Metadata

Name
dart-fix-ci
Description
"DART Fix CI: debug and fix failing CI checks"
<!-- AUTO-GENERATED FILE - DO NOT EDIT MANUALLY --> <!-- Source: .claude/commands/dart-fix-ci.md --> <!-- Sync script: scripts/sync_ai_commands.py --> <!-- Run `pixi run sync-ai-commands` to update -->

dart-fix-ci

Use this skill in Codex to run the DART dart-fix-ci workflow. The editable workflow source currently lives in .claude/commands/, and this generated Codex skill is a first-class Codex entrypoint.

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/ai/verification.md

Workflow

When the failing claim depends on model/scene structure, simulation, dynamics, collision/contact/constraints, or GUI/OSG output, use dart-verify-sim to pair the focused reproduction with assessed, claim-tied visual evidence. Document a visual exception when OSG/Xvfb is unavailable or not applicable.

  1. Identify failing checks: gh pr checks <PR_NUMBER> or gh run view <RUN_ID>.
  2. Inspect the first real failure: 
    gh run view <RUN_ID> --log-failed
gh run view <RUN_ID> --job <JOB_ID> --log
  3. If a job is still in progress, wait for logs instead of guessing.
  4. Reproduce locally with the smallest relevant command:
    • formatting: pixi run lint
    • tests: pixi run test, pixi run test-py, or another existing focused pixi run ... test task
    • coverage: add targeted tests for uncovered changed lines
  5. Fix the root cause with minimal scope.
  6. 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
  7. Ask for explicit maintainer/user approval before pushing, CI re-triggers, or other GitHub mutations; after approval, push and watch CI until the PR is green.

Output

  • Root cause
  • Fix or rerun action
  • Commands run
  • Current CI status