Track bugs, features, and UI regressions as repo-local markdown tickets using the `issue` CLI (repo-issue). Use this skill whenever the user wants to file a bug, log a feature request, track a TODO that deserves a ticket, list or search existing issues, check issue status, resolve or close tickets, or set up issue tracking in a repository. Also use it when the user mentions "issue tracker", "ticket", "BUG-001"-style IDs, an `issues/` directory, or asks "what's open", "what am I working on", or "file this as an issue" — even if they don't name the tool. Prefer this over GitHub issues when the repo has an `issues/` directory.
2026-07-14