issues

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):

   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.

2. Run the narrowest query that matches the request, always with the project:

   Request	MCP tool	tix
   Open tickets	ticket_search {project: "<repo>", state: "open"}	tix ls -p <repo> -s open
   One ticket	ticket_get {key: "<IDENT>-<n>"}	tix show <IDENT>-<n>
   By label	ticket_search {project: "<repo>", state: "open", labels: ["<label>"]}	tix ls -p <repo> -s open -l "<label>"
   Recently closed	ticket_search {project: "<repo>", state: "closed", limit: 10}	tix ls -p <repo> -s closed
   Keyword	ticket_search {project: "<repo>", state: "open", query: "<query>"}	tix ls -p <repo> -s open -q "<query>"