dart-fix-issue
GitHub自动化修复DART项目GitHub Issue。验证问题，分类是否为LTS分支Bug，执行最小化修复并添加回归测试。根据需求路由至仿真验证，运行Lint和测试，生成Changelog，最终创建双PR（LTS与main）以完成合并。
Trigger Scenarios
Install
npx skills add dartsim/dart --skill dart-fix-issue -g -y
SKILL.md
Frontmatter
{
"name": "dart-fix-issue",
"description": "DART Fix Issue: resolve a GitHub issue with a fix and regression test"
}
dart-fix-issue
Use this skill in Codex to run the DART dart-fix-issue 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-issue <arguments> - Codex:
$dart-fix-issue <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 GitHub issue: $ARGUMENTS
Required Reading
@AGENTS.md @docs/onboarding/contributing.md @docs/onboarding/changelog.md @docs/ai/verification.md
Workflow
If the issue's fix depends on model/scene structure, simulation, dynamics,
collision/contact/constraints, or GUI output, route through dart-verify-sim:
pair the focused behavioral oracle with assessed, claim-tied visual evidence,
or document a visual exception when rendering is unavailable or not
applicable.
gh issue view $1- Validate issue- Classify whether the issue is a bug fix that applies to the active DART 6
LTS branch. For applicable bug fixes, start from the highest maintained
origin/release-6.*branch; otherwise start fromorigin/main. - Fix with minimal changes + add regression test. For dual-PR bug fixes, fix
the active DART 6 LTS branch first, then cherry-pick or reapply to
main. pixi run lint, then run the smallest relevant tests; usepixi run test-allbefore finalizing when feasible, and alsopixi run -e cuda test-allon Linux hosts with a visible NVIDIA CUDA runtime- Before PR creation, invoke the
dart-changelogroutine to decide whetherCHANGELOG.mdneeds an entry, then fill.github/PULL_REQUEST_TEMPLATE.md. - After explicit maintainer/user approval,
git push -u origin HEAD && gh pr create --base <target-branch> --milestone "<milestone>" - Before PR: If task used
docs/dev_tasks/<task>/, remove the folder (include in this PR, not after merge)
CRITICAL: Dual-PR for Bug Fixes
PRs to BOTH the active DART 6 LTS branch AND main. See
docs/onboarding/contributing.md.
Output
- Issue number and classification (bug fix, dual-PR, or main-only)
- Fix summary and regression test added
- Gates run (lint, focused tests,
pixi run test-all) - PR readiness for each target branch, noting any explicitly approved mutation
Version History
- b9fbefc Current 2026-07-19 11:29
