← ClaudeAtlas

ticketslisted

Work with the project's issue tracker (Linear, GitHub Issues, Jira, GitLab, etc.) — auto-detect whichever tracker is available (a loaded tracker skill, an installed CLI, or a repo signal), then list / claim / comment / close / create / search issues, always closing with proof. Also drives the check-first / open-if-missing / close-on-delivery ticket lifecycle the conventions rule asks for. Triggers on: 'tickets', 'issues', 'issue tracker', 'my queue', "what's on my plate", 'claim/close/comment/create/search a ticket or issue', 'open an issue', 'move it to In Progress', 'linear', 'gh issue', 'jira', 'the board'.
phnx-labs/.agents · ★ 0 · Code & Development · score 56
Install: claude install-skill phnx-labs/.agents
You're being asked to do something with the project's issue tracker (arguments, if any, describe the action). (If no action is given, default to "show me what's on my plate right now.") ## Step 1: Find the available tracker Check in this order. Stop at the first one that's actually present. 1. **Skill-level integration.** Look for a skill in this loaded session whose name or description matches an issue-management system. Common names: `linear`, `github`, `jira`, `gitlab`, `shortcut`, `asana`. If one exists, read its `SKILL.md` and follow it — that file is the contract. 2. **Installed CLI.** No skill? Check what's already on `PATH`: - `linear --version` (Linear, via [phnx-labs/linear-cli](https://github.com/phnx-labs/linear-cli)) - `gh --version` (GitHub Issues) - `jira --version` (Jira, via `jira-cli`) - `glab --version` (GitLab) 3. **Repo-level signal.** Still nothing? Check the repo for tracker breadcrumbs: - `git remote -v` → if origin is `github.com`, GitHub Issues is the likely tracker. Install `gh` if missing. - Look for `.linear/`, `linear.config.*`, or env vars like `LINEAR_API_KEY` / `LINEAR_TEAM_KEY` → Linear. The canonical CLI is shipped as `~/.agents-system/cli/linear-cli.yaml`; install with `agents cli install linear-cli` (one confirm, then `linear setup --api-key ...`). - Look for Jira/Atlassian config (`.jira-cli.yml`, `JIRA_URL` in env). 4. **Ask.** If nothing's detectable, ask the user where issues live (Linear team key, GitHub re