# Dart Triage Issue

> DART Triage Issue: triage a GitHub issue and recommend next action

- Skill: `dartsim/dart-triage-issue` (Agent Skill)
- Install (CLI): `npx skillmds@latest add dartsim/dart-triage-issue`
- Raw SKILL.md: https://api.skillmd.com/api/skills/dartsim/dart-triage-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-triage-issue

---


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

# dart-triage-issue

Use this skill in Codex to run the DART `dart-triage-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-triage-issue <arguments>`
- Codex: `$dart-triage-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

Triage issue: $ARGUMENTS

## Required Reading

@AGENTS.md
@docs/onboarding/contributing.md

## Workflow

1. Inspect the issue:
   ```bash
   gh issue view <ISSUE_NUMBER> --comments
   ```
2. Determine whether the report is still valid on current `origin/main`.
3. Classify status:
   - still valid
   - already fixed
   - needs more information
   - duplicate
   - out of scope
4. If validity depends on behavior, reproduce or inspect the relevant code path.
5. Do not close or comment unless the user explicitly asks for that action.

## Output

- Status
- Rationale in 1-3 bullets
- Recommended next step
- Suggested reply text, if useful