Agent-Skills.md

Agent Skills: dart-downstream-fix

DART Downstream Fix: fix a DART bug reported through gz-physics or Gazebo

UncategorizedID: dartsim/dart/dart-downstream-fix

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-downstream-fix

Skill Files

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

Download Skill

Loading file tree…

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

Skill Metadata

Name
dart-downstream-fix
Description
"DART Downstream Fix: fix a DART bug reported through gz-physics or Gazebo"
<!-- AUTO-GENERATED FILE - DO NOT EDIT MANUALLY --> <!-- Source: .claude/commands/dart-downstream-fix.md --> <!-- Sync script: scripts/sync_ai_commands.py --> <!-- Run `pixi run sync-ai-commands` to update -->

dart-downstream-fix

Use this skill in Codex to run the DART dart-downstream-fix 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-downstream-fix <arguments>
  • Codex: $dart-downstream-fix <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 downstream-reported DART issue: $ARGUMENTS

Required Reading

@AGENTS.md @docs/onboarding/contributing.md @docs/onboarding/ci-cd.md

When To Use

Use for downstream issues in gz-physics, Gazebo, or gz-sim that trace back to DART behavior: crashes, assertions, NaN/Inf propagation, missing validation, or DART performance regressions.

Workflow

If the downstream symptom depends on scene/model structure, simulation, collision/contact, or OSG output, route through dart-verify-sim: establish a text oracle, add assessed claim-tied visual evidence, or document a visual exception when OSG/Xvfb is unavailable or not applicable.

  1. Read the downstream issue, logs, stack traces, and reproduction steps.
  2. Identify the DART API, component, and invalid usage pattern involved.
  3. Search for related validation and recovery patterns in DART.
  4. Plan the smallest fix and the regression test location.
  5. Decide whether the bug applies to the active release line. For applicable bug fixes, implement on the active DART 6 LTS branch:
    • branch: fix/<downstream-project>-<issue-number>-<brief-description>-6-lts
    • add a regression test that reproduces the downstream symptom
    • keep the fix minimal; no unrelated refactors
  6. Run pixi run lint and relevant tests; use pixi run test-all when feasible, and run pixi run -e gazebo test-gz when Gazebo/gz-physics compatibility could be affected.
  7. Ask for explicit maintainer/user approval before pushing or creating PRs. After approval, create the release-branch PR with the branch-matching DART 6.x release milestone and reference the downstream issue.

Release-Line Conventions

  • DART 6 LTS may use dtwarn << ..., <dart/dart.hpp>, and older test CMake patterns.

Output

  • Root cause and fix summary
  • Main PR URL and release PR URL, if applicable
  • Tests run and CI status
  • Link back to the downstream issue