Issues
Inspect current-repository tickets in Plane (via the tickets MCP tools, else the tix CLI) or prepare a specifically requested routed ticket. Use when the user asks to list, view, filter, search, or create an issue or ticket.
Install
npx skills add Magnus-Gille/claude-skills --skill issuesgit clone --depth 1 https://github.com/Magnus-Gille/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/codex/issues ~/.claude/skills/issuesPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Tickets Use this skill to inspect and summarize tickets for the current repository. Tickets live in Plane CE (`https://tickets.gille.ai`, workspace `gille`) and replaced GitHub Issues: one Plane project per repository, ticket key `IDENT-N` (for example `GRIM-87`), and migrated tickets keep their GitHub number (`grimnir#87` is `GRIM-87`). Do not use `gh issue`; old GitHub issues are closed with a link to their ticket and no new ones are filed. Pull requests stay on GitHub. ## Tools Prefer the `tickets` MCP tools when available (`ticket_search`, `ticket_get`, `ticket_create`, `ticket_update`, `ticket_comment`, `ticket_close`, `project_list`, `project_meta`, `roadmap`); otherwise use the `tix` CLI. They share one gateway and one set of conventions. In `tix`, `-p` takes the Plane identifier (`GRIM`) or the repo name (`grimnir`). Priorities are `urgent`, `high`, `medium`, `low`, `none`; states are Plane state names (`Backlog`, `Todo`, `In Progress`, `Done`, `Cancelled`) or the aliases `open` and `closed`. If neither route works, report the exact error and stop; do not mint tokens or change authentication. ## Workflow 1. Resolve the project from the git remote (not the directory name): ```bash git remote get-url origin ``` Use the last path segment without `.git` as the project (for example `grimnir`) and confirm it with `project_list` or `tix projects`. If the repo has no project, report that and stop instead of guessing.
Details
- Skill name
issues- Repository
- Magnus-Gille/claude-skills
- Path
codex/issues/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Issues skill do?
Inspect current-repository tickets in Plane (via the tickets MCP tools, else the tix CLI) or prepare a specifically requested routed ticket. Use when the user asks to list, view, filter, search, or create an issue or ticket.
How do I install the Issues skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add Magnus-Gille/claude-skills --skill issues. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Issues popular?
It lives in Magnus-Gille/claude-skills, which has 5 GitHub stars and 0 forks.
Related skills
Close
5Magnus-Gille/claude-skills
Close a coding-agent session or produce its final handoff only when the user explicitly asks to close, wrap up, or produce an end-of-session handoff.
Cloudflare Private Static Site
5Magnus-Gille/claude-skills
Create, preview, test, release, verify, or roll back a small static Cloudflare site protected by per-person HTTP Basic Auth. Use for private briefings, reports, one-pagers, document portals, or similar sites that should go from finished content to a custom domain in about ten minutes. Do not use for full applications or when the user requires SSO, identity lifecycle, or Cloudflare Access policy management.
Code Friction
5Magnus-Gille/claude-skills
Capture a small, opt-in set of concrete code-changeability observations during a coding task and hand them to Close without affecting readiness.
Project Validator
5tomada1114/tomada-claude-plugins
Check a Node project for the setup failures that surface later as confusing runtime errors — malformed package.json, uninstalled node_modules, missing .env, uninitialized git — and scaffold the missing pieces. Use when onboarding to an unfamiliar repo, bootstrapping a new project, or diagnosing "it works on my machine".
Http Status Guide
5tomada1114/tomada-claude-plugins
Pick the HTTP status code an API should return for a given outcome, and settle the cases where two codes both look defensible — 401 vs 403, 400 vs 422, 404 vs 403 for hidden resources, 409 vs 422 for conflicts. Use when designing REST endpoints, reviewing an API's error handling, or debugging a client that mishandles a response.
Review PR Codex
5Magnus-Gille/claude-skills
Review a requested pull request or branch diff read-only in this Codex session. Use when the user asks for review-pr-codex or a Codex PR review.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.