dart-fix-issue

name: dart-fix-issue description: "DART Fix Issue: resolve a GitHub issue with a fix and regression test"

Use this skill in Codex to run the DART dart-fix-issue 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-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

Workflow

gh issue view $1 - Validate issue
Classify whether the issue is a bug fix that applies to release-6.17. For applicable bug fixes, start from origin/release-6.17; otherwise start from origin/main.
Fix with minimal changes + add regression test. For dual-PR bug fixes, fix release-6.17 first, then cherry-pick or reapply to main.
pixi run lint, then run the smallest relevant tests; use pixi run test-all before finalizing when feasible, and also pixi run -e cuda test-all on Linux hosts with a visible NVIDIA CUDA runtime
Before PR creation, decide whether CHANGELOG.md needs an entry and 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 release-6.17 AND main. See docs/onboarding/contributing.md.