# Classify Issue > Classify a GitHub issue into a problem class (chore, bug, or feature) for ADW routing. Use to determine which planning template to apply. Use when this capability is needed. - Skill: `tomevault-io/classify-issue` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/classify-issue` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/classify-issue/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/classify-issue --- # Issue Classification Analyze the issue and respond with exactly one classification. ## Categories ### /chore Maintenance tasks, updates, cleanup, refactoring: - Dependency updates - Code cleanup and formatting - Documentation improvements - Refactoring without behavior change ### /bug Defects, errors, unexpected behavior: - Something broken that should work - Crashes, errors, incorrect output - Regressions from previous functionality - Performance issues causing failures ### /feature New functionality, enhancements: - New user-facing capabilities - Enhancements to existing features - New API endpoints or integrations - UI/UX improvements ## Rules 1. Respond with exactly one: `/chore`, `/bug`, `/feature`, or `0` 2. If the issue fits multiple categories, choose the primary purpose 3. If unclear between chore and feature, prefer `/chore` (safer) 4. If the issue is a question or discussion, respond with `0` 5. Your response should be ONLY the classification, nothing else ## Examples - "Update dependencies to latest" → `/chore` - "Login form submits twice" → `/bug` - "Add dark mode toggle" → `/feature` - "Question about the API" → `0` ## Issue $ARGUMENTS --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/melodic-software) — claim your Tome and manage your conversions.