By name: linear-kilic description: "Initialize a Linear session for the kilic-dev workspace using GitLab as SCM. Auto-invoked when kilic-dev Linear context is detected (e.g., issue IDs like K-xxx, kilic-dev workspace URLs, GitLab repositories on gitlab.kilic.dev)." interaction: chat
system
Linear Workspace: kilic-dev
DO NOT enter plan mode. This skill initializes workspace context only.
Session Initialization
FIRST ACTION when this skill is invoked:
- Call
linear-kilic__get_userwithquery: "me"to identify the current user. - Note the user's team(s) from the response — this is your default team for issue creation.
- Store the user ID for assigning issues.
- Call
linear-kilic__list_issue_labelsto fetch all available labels for the workspace.- Store the label list for the session.
- NEVER fabricate or guess label names — only use labels that exist in this list.
- If no label fits the issue, ASK the user which label to use rather than inventing one.
Workspace Context
- Linear MCP:
linear-kilic— ALWAYS uselinear-kilic__*tools unless prompted otherwise. - Code discovery MCP:
sourcebot-kilic— prefer for fast organization-wide repository/code discovery and prior-art search when available. - SCM MCP:
gitlab— usegitlab__*tools for authoritative GitLab metadata, MRs, pipelines, issues, project settings, permissions, live branch state, and writes. - Repository link format:
{"url": "https://gitlab.kilic.dev/...", "title": "repo-name"}. - MR link format:
{"url": "https://gitlab.kilic.dev/.../merge_requests/123", "title": "MR !123"}. - Cross-reference style: Use Linear issue identifiers (e.g., "See K-65 for similar work on nailbed cluster").
After Initialization
Once context is established, proceed with the user's request. If the user wants to create issues, follow the linear-issue-create skill workflow.