How do I install the Dart Fix Issue skill?

Run npx skillmds@latest add dartsim/dart-fix-issue 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 Fix Issue skill do?

DART Fix Issue: resolve a GitHub issue with a fix and regression test It is listed under Coding & Dev Tools on SkillMD.

Is Dart Fix Issue 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 Fix Issue?

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 Fix Issue free to use?

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

Who published Dart Fix Issue?

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

Dart Fix Issue by dartsim — Agent Skill

Name: Dart Fix Issue
Author: dartsim

File contents

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.

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 from origin/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.
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.
pixi run lint, then the smallest relevant tests and the task-type gate set from docs/ai/verification.md
Before PR creation, invoke the dart-changelog routine to decide whether CHANGELOG.md needs 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>"

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

---name: dart-fix-issuedescription: DART Fix Issue: resolve a GitHub issue with a fix and regression test---# dart-fix-issueUse this skill in Codex to run the DART `dart-fix-issue` workflow. The editableworkflow source lives in `.claude/commands/`; this file is its generated adapterin 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 workflowreferences `$1`, `$2`, etc., map those to the positional values supplied by theuser.## Command BodyFix GitHub issue: $ARGUMENTS## Required Reading@AGENTS.md@docs/onboarding/contributing.md@docs/onboarding/changelog.md@docs/ai/verification.md## WorkflowIf the fix depends on 3D structure or behavior, route through`dart-verify-sim`: text oracle plus assessed visual evidence, or a recordedexception.1. `gh issue view $1` - Validate issue2. 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 FixesPRs 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

Frequently asked questions

Dart Fix Issue