How do I install the Dart Downstream Fix skill?

Run npx skillmds@latest add dartsim/dart-downstream-fix in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Dart Downstream Fix skill do?

DART Downstream Fix: fix a DART bug reported through gz-physics or Gazebo It is listed under Coding & Dev Tools on SkillMD.

Is Dart Downstream Fix safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dart Downstream Fix?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dart Downstream Fix free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Dart Downstream Fix?

dartsim (@dartsim) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dart Downstream Fix by dartsim — Agent Skill

Name: Dart Downstream Fix
Author: dartsim

File contents

dart-downstream-fix

Use this skill in Codex to run the DART dart-downstream-fix workflow. The editable workflow source lives in .claude/commands/; this file is its generated adapter in the shared .agents/skills/ catalog.

Invocation

Claude Code: /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 3D structure or behavior, route through dart-verify-sim: text oracle plus assessed visual evidence, or a recorded exception.

Read the downstream issue, logs, stack traces, and reproduction steps.
Identify the DART API, component, and invalid usage pattern involved.
Search for related validation and recovery patterns in DART.
Plan the smallest fix and the regression test location.
Decide whether the bug applies to the active release line. For applicable bug fixes, implement on the active DART 6 LTS branch first, then cherry-pick or reapply to main for DART 7:
- 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
Run pixi run lint and the relevant tests per docs/ai/verification.md.
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.
Create the matching main PR with milestone DART 7.0; adapt API differences if needed.

Release-Line Differences

DART 7 commonly uses DART_WARN() and <dart/all.hpp>.
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

---name: dart-downstream-fixdescription: DART Downstream Fix: fix a DART bug reported through gz-physics or Gazebo---# dart-downstream-fixUse this skill in Codex to run the DART `dart-downstream-fix` workflow. The editableworkflow source lives in `.claude/commands/`; this file is its generated adapterin the shared `.agents/skills/` catalog.## Invocation- Claude Code: `/dart-downstream-fix <arguments>`- Codex: `$dart-downstream-fix <arguments>`Treat the text after the skill name as `$ARGUMENTS`. When the workflowreferences `$1`, `$2`, etc., map those to the positional values supplied by theuser.## Command BodyFix downstream-reported DART issue: $ARGUMENTS## Required Reading@AGENTS.md@docs/onboarding/contributing.md@docs/onboarding/ci-cd.md## When To UseUse 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.## WorkflowIf the downstream symptom depends on 3D structure or behavior, route through`dart-verify-sim`: text oracle plus assessed visual evidence, or a recordedexception.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 first, then cherry-pick or reapply to `main` for DART 7: - 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 refactors6. Run `pixi run lint` and the relevant tests per `docs/ai/verification.md`.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.8. Create the matching `main` PR with milestone `DART 7.0`; adapt API differences if needed.## Release-Line Differences- DART 7 commonly uses `DART_WARN()` and `<dart/all.hpp>`.- 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

Frequently asked questions

Dart Downstream Fix