dart-fix-issue
SkillDev toolsDART Fix Issue: resolve a GitHub issue with a fix and regression test
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the dart-fix-issue skill
What this skill tells your AI
The instructions your AI receives, as published by dartsim/dart in .agents/skills/dart-fix-issue/SKILL.md and read by ahel’s review.
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 fix depends on 3D structure or behavior, route through
dart-verify-sim: text oracle plus assessed visual evidence, or a recorded
exception.
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 the smallest relevant tests and the task-type gate set fromdocs/ai/verification.md- 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
Signals
- GitHub stars
- 1k
- Forks
- 304
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
dart-fix-issue- Source
- github.com/dartsim/dart