# Dart Fix Issue

> DART Fix Issue: resolve a GitHub issue with a fix and regression test

- Skill: `dartsim/dart-fix-issue` (Agent Skill)
- Install (CLI): `npx skillmds@latest add dartsim/dart-fix-issue`
- Raw SKILL.md: https://api.skillmd.com/api/skills/dartsim/dart-fix-issue/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: dartsim (https://skillmd.com/u/dartsim)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/dartsim/dart-fix-issue

---


<!-- AUTO-GENERATED FILE - DO NOT EDIT MANUALLY -->
<!-- Source: .claude/commands/dart-fix-issue.md -->
<!-- Sync script: scripts/sync_ai_commands.py -->
<!-- Run `pixi run sync-ai-commands` to update -->

# 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: `/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.

1. `gh issue view $1` - Validate issue
2. 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 from `origin/main`.
3. 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`.
4. For an intermediate commit or PR, preserve and update the active task folder.
   In the completing change, follow `docs/dev_tasks/README.md`: complete feasible
   work, promote durable artifacts, and remove the folder before final validation
   and commit. Preserve its approval requirement for retiring unfinished work.
5. `pixi run lint`, then the smallest relevant tests and the task-type gate
   set from `docs/ai/verification.md`
6. Before PR creation, invoke the `dart-changelog` routine to decide whether
   `CHANGELOG.md` needs an entry, then fill `.github/PULL_REQUEST_TEMPLATE.md`.
7. After explicit maintainer/user approval, `git push -u origin HEAD && gh pr create --base <target-branch> --milestone "<milestone>"`

## 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