
Linear Issue Importer
- 27 repo stars
- Updated March 1, 2026
- jamesckemp/claude-plugins
Helps with ai & agent building tasks.
About
linear-issue-importer is a Claude Code skill for ai & agent building. It helps developers move faster with AI-assisted coding.
- linear-issue-importer
- AI & Agent Building
- AI-coding skill
Linear Issue Importer by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin marketplace add jamesckemp/claude-plugins/plugin install linear-issue-importer@jck-claude-pluginsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| repo stars | ★ 27 |
|---|---|
| Last updated | March 1, 2026 |
| Repository | jamesckemp/claude-plugins ↗ |
What it does
Helps with ai & agent building tasks.
README.md
Linear Issue Importer
Extract issues from documents and import them into Linear — directly from Claude Code.
What it does
Point this plugin at any document — meeting transcript, bug list, Granola note, or raw notes — and it will:
- Extract actionable issues (bugs, tasks, feature requests) from the content
- Let you configure the Linear team, labels, assignee, project, and parent issue
- Check for duplicates with multi-layer search (parent sub-issues, team search, cross-team fallback, internal dedup)
- Create issues in Linear with properly formatted descriptions
- Generate a summary of everything that was created, skipped, or removed
Prerequisites
- Claude Code CLI installed
- Linear MCP server connected (
mcp__claude_ai_Linear__*tools available)
Installation
Add this plugin to Claude Code:
claude plugin add /path/to/linear-issue-importer
Usage
/import-issues path/to/document.md # Full import — creates issues in Linear
/preview-issues path/to/document.md # Dry run — extract and configure only, nothing created
Use /preview-issues first to verify extraction quality before committing to a real import.
Supported document types
| Type | Example |
|---|---|
| Granola JSON export | Meeting recording with transcript |
| Granola Obsidian note | Meeting notes synced to Obsidian vault |
| Markdown bug list | Categorized bug reports with "Bug:", "UX:" prefixes |
| Raw transcript | Speaker-labeled meeting transcript |
| General document | Any structured document with actionable items |
Examples
# Import bugs from a walkthrough document
/import-issues /path/to/walkthrough-bugs.md
# Import action items from a Granola meeting note
/import-issues /path/to/Obsidian/Granola/2026-02-20_Team_Sync.md
# Import from a Granola JSON export
/import-issues /path/to/meeting-export.json
Workflow
- Extract — the plugin reads your file and identifies issues
- Review — you see a numbered list of extracted issues with suggested types and priorities
- Configure — pick your Linear team, labels, and other settings
- Confirm — approve, remove, or edit issues before creation
- Import — duplicate check runs, then issues are created in Linear
- Summary — get a markdown summary with links to all created issues
For 10+ issues, the plugin can use parallel agents grouped by category to speed up creation.
Issue types
The plugin detects three types of issues and uses the appropriate description template:
- Bug report — Describe the bug / Steps to reproduce / Expected / Actual behavior
- Action item — Task / Context / Acceptance criteria
- Feature request — Description / Problem it solves / Suggested approach
Every issue includes a source attribution linking back to the original document.
Author
James Kemp