erode-app/erode / .agents/skills/linearis
linearis
VerifiedInteract with Linear.app for issue tracking. Use when working with Linear tickets (format ABC-123), creating issues, updating status, or downloading attachments. Triggers on ticket references, issue management, or when user mentions Linear.
Linear Issue Tracking
We track tickets and projects in Linear (https://linear.app). Use the linearis CLI tool via Bash.
Run linearis usage to see all available commands and options.
Quick Reference
| Command | Purpose |
|---|---|
linearis issues read ABC-123 | Get issue details + attachments |
linearis issues search "keyword" | Search issues |
linearis issues create "Title" --team Team | Create issue |
linearis issues update ABC-123 --status "Done" | Update issue |
linearis comments create ABC-123 --body "text" | Add comment |
linearis documents list --issue ABC-123 | List attached docs |
linearis embeds download "<url>" --output ./file --overwrite | Download attachment |
Conventions
- Ticket format:
ABC-<number>(e.g.,FOR-123) - Always reference tickets by their identifier
- When creating subtasks, use parent ticket's project by default
- If project unclear when creating tickets, ask the user
Workflow: Starting Work on an Issue
When the user asks to start working on a Linear issue, these steps must be included in your plan (using TodoWrite or similar planning tools):
-
Read the issue details:
linearis issues read ABC-123 -
Switch to main branch:
- Ensures you're creating the feature branch from the latest main
- Avoids creating branches from other feature branches
git checkout main git pull origin main -
Create a feature branch:
- Branch name format:
feature/ABC-123-brief-description - Example:
feature/FOR-123-add-costs-projection
git checkout -b feature/ABC-123-brief-description - Branch name format:
-
Update issue status to "In Progress":
linearis issues update ABC-123 --status "In Progress" -
Implement the feature:
- Follow the task requirements from the issue description
- Add progress comments as needed
-
Verify implementation and get user sign-off:
- Before committing, verify the implementation matches the plan
- Suggest running:
/verify-plan <PLAN-PATH>(if a plan file exists) - Wait for explicit user approval before proceeding to create the PR
- This ensures the work meets requirements and follows the intended approach
-
When complete and approved, create a pull request:
git push -u origin feature/ABC-123-brief-description gh pr create --title "ABC-123: Brief description" --body "Resolves ABC-123\n\n## Summary\n- Implemented feature...\n\n## Test plan\n- [ ] Tested scenario..." -
Update issue status to "In Review":
linearis issues update ABC-123 --status "In Review"
Critical: When planning work on a Linear issue, include ALL these workflow steps in your TodoWrite plan. Don't just implement the feature - the plan must include branch creation at the start, user sign-off verification before committing, and PR creation at the end.
Workflow: Investigating an Issue
When the user asks to investigate/explore/look into a Linear issue (without immediately implementing):
- Read the issue details with
linearis issues read ABC-123 - Search the codebase for related files (grep for keywords, component names, API endpoints mentioned in the ticket)
- Summarize findings directly to the user with:
- Ticket requirements and acceptance criteria
- Relevant files and their roles
- Proposed implementation approach
- Open questions or blockers
- Estimated complexity (S/M/L)
Always produce a visible summary even if the investigation is cut short. The summary is the deliverable.
Working with Issues
Read issue with attachments:
linearis issues read ABC-123
Returns JSON including an embeds array containing uploaded files (screenshots, documents, etc.) with signed download URLs and expiration timestamps.
Download attachments to .linear-tmp/ (gitignored):
mkdir -p .linear-tmp
linearis embeds download "https://uploads.linear.app/..." --output .linear-tmp/screenshot.png --overwrite
Progress Updates
- When task status changes in ticket description (e.g.,
- [ ] task→- [x] task), update the description accordingly - When adding progress reports (more than checkbox changes), add as ticket comment:
linearis comments create ABC-123 --body "Progress update: ..."
Authentication
A project-local token file .linear_api_token exists in the project root. Always pass it explicitly when running linearis commands:
linearis --api-token "$(cat .linear_api_token)" <command>
Do NOT rely on ~/.linear_api_token or LINEAR_API_TOKEN env var — those may belong to a different team.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 117k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |