Agent Skills: dart-release-ci-fix

DART Release CI Fix: debug and fix CI failures on the DART 6.20 release branch

ID: dartsim/dart/dart-release-ci-fix

Repository

dartsimLicense: BSD-2-Clause
1,212304

Install this agent skill to your local

npx skills add dartsim/dart --skill dart-release-ci-fix

Skill Files

The files that make up dart-release-ci-fix.

Download Skill

Loading file tree…

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

Skill Metadata

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

dart-release-ci-fix

Use this skill to run the DART dart-release-ci-fix workflow. The editable workflow source lives in .claude/commands/; this generated skill is its entrypoint for Codex and Muse.

Invocation

  • Claude Code: /dart-release-ci-fix <arguments>
  • Codex: $dart-release-ci-fix <arguments>
  • Muse: /dart-release-ci-fix <arguments>

Treat the text after the skill name, or the user's request when the skill is loaded on demand, as $ARGUMENTS. When the workflow references $1, $2, etc., map those to the positional values supplied by the user.

Command Body

Fix DART CI: $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 Filament output, use dart-verify-sim to reproduce the claim with text and assessed visual evidence. Document a visual exception when graphics support is unavailable or not applicable.

  1. Inspect the failing run:
    gh run view <RUN_ID> --log-failed
    gh run view <RUN_ID> --job <JOB_ID> --log
    
  2. Resolve the target from the live PR base or failing run's branch. Default to main when no target is specified. Fetch that target and read its docs/onboarding/release-management.md § "Release target"; verify the exact DART <Next release> milestone is open on GitHub. Publishing requires explicit maintainer/user approval.
  3. If continuing an existing PR, fetch and checkout that branch. Otherwise branch from the resolved target branch without resetting an existing local branch:
    TARGET_BRANCH=${TARGET_BRANCH:-main}
    git fetch origin "$TARGET_BRANCH"
    BRANCH=fix/<issue>-${TARGET_BRANCH}
    if git show-ref --verify --quiet "refs/heads/$BRANCH"; then
      git switch "$BRANCH"
    else
      git switch --no-track -c "$BRANCH" "origin/$TARGET_BRANCH"
    fi
    
  4. If a proven fix exists in a named reference, adapt it only when its assumptions exist here; otherwise make the smallest branch-scoped fix. Follow the resolved branch's compatibility rules in AGENTS.md, preserving C++17, its dartpy binder and GUI backend (nanobind and Filament on main and DART 7 release branches; pybind11 and OSG on release-6.20), dart::utils, and downstream Gazebo/gz-physics behavior.
  5. Explain why the failure was not caught earlier and whether workflow coverage should change.
  6. Run pixi run lint and release-relevant build/tests.
  7. Ask for explicit maintainer/user approval before pushing, creating, or updating the PR. After approval, push to the existing PR when step 3 continued one; otherwise open a new draft PR with the resolved next-release milestone and PR template. Then follow docs/onboarding/ai-tools.md § "PR Lifecycle".
  8. Monitor CI until green.

Output

  • Root cause
  • Fix summary
  • PR URL
  • CI status
  • Prevention recommendation, if any

More agent skills