michaelschecht Linear
Use this skill for structured work inside Linear rather than ad hoc ticket editing.
Prerequisites
- Linear tools or app connection must already be available
- Confirm the correct workspace, team, and project before making changes
When To Use
- Create or update issues
- Triage bugs and prioritize backlogs
- Plan cycles or release work
- Audit documentation tasks and open follow-up tickets
- Rebalance workload across assignees
Recommended Workflow
- Clarify the goal: triage, planning, documentation, project setup, or status update.
- Read first: list issues, projects, teams, labels, cycles, or documents.
- Confirm identifiers before mutating anything.
- Apply grouped updates in logical batches.
- Summarize what changed, what is blocked, and what should happen next.
Common Operations
- Issue management: list, search, get, create, update, comment
- Planning: review active cycles, assign work, create labels, track blockers
- Project work: create or update a project, then attach related issues
- Documentation audit: search docs, identify gaps, and open actionable follow-ups
Practical Tips
- Read existing state before creating duplicates
- Batch related edits to avoid noisy ticket churn
- Use consistent labels and priorities
- Break large cleanup jobs into smaller passes
Troubleshooting
- If tools are unavailable, stop and connect the Linear integration first
- If data looks incomplete, verify workspace access and archived filters
- If requests are large, split them into smaller batches