Menu
ALWAYS check before working with Linear issues. Guide for Linear-related skills for ticket management and debugging workflows.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Generic migration orchestrator that reads CHANGELOG.md to understand and execute version-specific migrations
Determine feature slug interactively by auto-detecting next number and prompting user for description
Share personal documents to the shared namespace with atomic git commit and push
Use when creating implementation plans to generate properly structured plans with phases, success criteria, and project references.
Use when documenting research findings to create properly structured research documents with frontmatter, sections, and file references.
ALWAYS check this skill before using grep, glob, Task tool, or doing any codebase exploration. Guides you to use specialized agents that are more efficient than basic tools.
| name | linear-awareness |
| description | ALWAYS check before working with Linear issues. Guide for Linear-related skills for ticket management and debugging workflows. |
You have specialized Linear issue management skills. Use these for structured ticket workflows during debugging investigations.
Simple issue fetch or update? → Use Linear skills
linear-issues - Fetch, list, search issues (single linearis command)linear-update - Update issue, add commentsComplex investigation requiring analysis? → Use Task tool with Linear agents (conserves context)
linear-locator - Find issues by criteria, save to /tmplinear-analyzer - Extract debugging context, parse technical detailslinear-pattern-finder - Find patterns across issues, detect recurring problemsJust need to find issues broadly?
→ Use linear-locator agent only
Investigating single issue for debugging?
→ Use linear-locator + linear-analyzer agents
Need to find patterns or recurring problems?
→ Use all three: linear-locator + linear-analyzer + linear-pattern-finder
Adding debugging findings to a ticket?
→ Use linear-update skill
linearis comments create commandsUpdating issue status after investigation?
→ Use linear-update skill
| Type | Name | Purpose |
|---|---|---|
| Skill | linear-issues | Simple queries (single linearis command) |
| Skill | linear-update | Update issues, add comments |
| Agent | linear-locator | Find issues by criteria across teams |
| Agent | linear-analyzer | Extract debugging context from issues |
| Agent | linear-pattern-finder | Find patterns, recurring problems, trends |
Only use linearis CLI directly when:
linearis issues create)For systematic ticket workflows (read → debug → update), use the specialized skills above.
Covered by skills:
linearis issues read → Use linear-issueslinearis issues list → Use linear-issueslinearis issues search → Use linear-issueslinearis comments create → Use linear-updatelinearis issues update → Use linear-updateNot covered yet (use directly):
linearis issues create (issue creation)linearis projects, linearis teams, linearis users (non-issue operations)Check linearis CLI is available and authenticated:
linearis --version
linearis issues list --limit 1
Note: Set LINEARIS_API_TOKEN environment variable or use --api-token flag.
Linear skills integrate with platform debugging:
Workflow:
linear-issues → Fetch ticket contextlinear-update → Add findings to ticketlinear-update → Update status to "Done"Example:
User: "Debug issue ENG-1234"
Claude: [Checks linear-awareness] → Uses linear-issues
[Investigates using GCP/K8s skills]
[Checks linear-awareness] → Uses linear-update