issueslisted

# Issues Find and rank the issues that are candidates for your next unit of work, so you can choose one — the plural, read-only counterpart to the `issue` skill. Where `issue` *authors* a single issue (file a new one, or update a known one), `issues` *surveys* the backlog: it fetches, ranks, and points at the next thing to pick up. It never writes to the forge. The default view answers "what's next?" — **your** open issues, ranked by **soonest due date, then most recently updated**. So the item most likely to be next sits at the top. **Don't narrate your work.** Every step below is an operating instruction, not a script to read aloud — follow the execute-quietly discipline: `${CLAUDE_PLUGIN_ROOT}/guides/execute-quietly.md`. For this skill, the only things worth surfacing are a question you need answered, the ranked list, the recommended next pick, and — if the user opens one — its detail or URL. Issues = GitHub issues or GitLab issues. Pick the forge tool by the `origin` remote (`gh` / `glab`). ```mermaid %%{ init: { 'look': 'handDrawn' } }%% flowchart TD Start(["/issues [query]"]) --> Scope["Step 1: Resolve the scope from the query"] Scope --> Fetch["Step 2: Fetch (forge JSON)"] Fetch --> Rank["Step 3: Rank — due first, then most-recently-updated"] Rank --> Present["Step 4: Present the list + recommend next"] Present --> Pick{Open a pick?} Pick -->|Yes| View(["View detail / open in browser"]) Pick -->|No| Done([Done]) ``` ## Target repo By