Linear
ProductivityCommonly used with
Skills using Linear (102)
linear-automation
Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels. Always search tools first for current schemas.
clay-hello-world
Send your first record to Clay and get enriched data back. Use when starting a new Clay integration, testing webhook setup, or verifying that enrichment columns are working. Trigger with phrases like "clay hello world", "clay example", "clay quick start", "first clay enrichment", "test clay webhook".
linear-ci-integration
Integrate Linear with GitHub Actions CI/CD pipelines. Use when setting up automated testing, PR-to-issue linking, or creating Linear issues from CI failures. Trigger: "linear CI", "linear GitHub Actions", "linear CI/CD", "linear automated tests", "linear PR integration".
linear-common-errors
Diagnose and fix common Linear API and SDK errors. Use when encountering Linear API errors, debugging integration issues, or troubleshooting authentication, rate limits, or query problems. Trigger: "linear error", "linear API error", "debug linear", "linear not working", "linear 429", "linear authentication error".
linear-core-workflow-a
Issue lifecycle management with Linear: create, update, transition, relate, comment, and organize issues through the SDK and GraphQL API. Trigger: "linear issue workflow", "linear issue lifecycle", "create linear issues", "update linear issue", "linear state transition", "linear sub-issues", "linear comments".
linear-core-workflow-b
Project, cycle, and roadmap management workflows with Linear. Use when implementing sprint planning, managing projects and milestones, or organizing work into cycles. Trigger: "linear project", "linear cycle", "linear sprint", "linear roadmap", "linear planning", "linear milestone".
linear-cost-tuning
Optimize Linear API usage, reduce unnecessary calls, and maximize efficiency within rate limit budgets. Trigger: "linear cost", "reduce linear API calls", "linear efficiency", "linear API usage", "optimize linear costs", "linear budget".
linear-data-handling
Data synchronization, backup, and consistency patterns for Linear. Use when implementing data sync, creating backups, exporting data, or ensuring data consistency between Linear and local state. Trigger: "linear data sync", "backup linear", "linear export", "linear data consistency", "sync linear issues".
linear-debug-bundle
Comprehensive debugging toolkit for Linear integrations. Use when setting up logging, tracing API calls, or building debug utilities for Linear. Trigger: "debug linear integration", "linear logging", "trace linear API", "linear debugging tools".
linear-hello-world
Create your first Linear issue and query using the SDK and GraphQL API. Use when making initial API calls, testing connection, or learning basic Linear CRUD operations. Trigger: "linear hello world", "first linear issue", "create linear issue", "linear API example", "test linear".
linear-incident-runbook
Production incident response procedures for Linear integrations. Use when handling production issues, diagnosing outages, or responding to Linear-related incidents. Trigger: "linear incident", "linear outage", "linear production issue", "debug linear production", "linear down", "linear 500".
linear-install-auth
Install and configure Linear SDK/CLI authentication. Use when setting up a new Linear integration, configuring API keys, OAuth2 flows, or initializing LinearClient in your project. Trigger: "install linear", "setup linear", "linear auth", "configure linear API key", "linear SDK setup", "linear OAuth".
linear-multi-env-setup
Configure Linear across development, staging, and production environments. Use when setting up per-environment API keys, secret management, or environment-specific Linear configurations. Trigger: "linear environments", "linear staging", "linear dev prod", "linear environment setup", "multi-environment linear".
linear-observability
Implement monitoring, logging, and alerting for Linear integrations. Use when setting up metrics collection, dashboards, or configuring alerts for Linear API usage. Trigger: "linear monitoring", "linear observability", "linear metrics", "linear logging", "monitor linear", "linear Prometheus", "linear Grafana".
linear-performance-tuning
Optimize Linear API queries, caching, and batching for performance. Use when improving response times, reducing API calls, or implementing caching strategies for Linear data. Trigger: "linear performance", "optimize linear", "linear caching", "linear slow queries", "speed up linear", "linear N+1".
linear-prod-checklist
Production readiness checklist for Linear integrations. Use when preparing to deploy, reviewing production requirements, or auditing existing Linear deployments. Trigger: "linear production checklist", "deploy linear", "linear production ready", "linear go live", "linear launch".
linear-rate-limits
Handle Linear API rate limiting, complexity budgets, and quotas. Use when dealing with 429 errors, implementing throttling, or optimizing request patterns to stay within limits. Trigger: "linear rate limit", "linear throttling", "linear 429", "linear API quota", "linear complexity", "linear request limits".
linear-sdk-patterns
TypeScript/JavaScript SDK patterns and best practices for Linear. Use when learning SDK idioms, implementing pagination, filtering, relation loading, or custom GraphQL queries. Trigger: "linear SDK patterns", "linear best practices", "linear typescript", "linear API patterns", "linear pagination".
linear-security-basics
Secure API key management, OAuth best practices, and webhook verification for Linear integrations. Trigger: "linear security", "linear API key security", "linear OAuth", "secure linear", "linear webhook verification", "linear secrets management", "linear token refresh".
linear-upgrade-migration
Upgrade Linear SDK versions and handle breaking changes safely. Use when updating to a new SDK version, handling deprecations, or migrating between API versions. Trigger: "upgrade linear SDK", "linear SDK migration", "update linear", "linear breaking changes", "linear deprecation".
linear-automation
Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels. Always search tools first for current schemas.
linear-claude-skill
Manage Linear issues, projects, and teams
linear-issue-generator
Generate linear issue generator operations. Auto-activating skill for Enterprise Workflows. Triggers on: linear issue generator, linear issue generator Part of the Enterprise Workflows skill category. Use when working with linear issue generator functionality. Trigger with phrases like "linear issue generator", "linear generator", "linear".
knowledge-ops
Knowledge base management, ingestion, sync, and retrieval across multiple storage layers (local files, MCP memory, vector stores, Git repos). Use when the user wants to save, organize, sync, deduplicate, or search across their knowledge systems.
project-flow-ops
Operate execution flow across GitHub and Linear by triaging issues and pull requests, linking active work, and keeping GitHub public-facing while Linear remains the internal execution layer. Use when the user wants backlog control, PR triage, or GitHub-to-Linear coordination.
unified-notifications-ops
Operate notifications as one ECC-native workflow across GitHub, Linear, desktop alerts, hooks, and connected communication surfaces. Use when the real problem is alert routing, deduplication, escalation, or inbox collapse.
linear-automation
Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels. Always search tools first for current schemas.
linear
Manage issues, projects & team workflows in Linear. Use when the user wants to read, create or updates tickets in Linear.
ux-compare
Compare UX patterns across multiple reference apps using pattern libraries produced by ux-extract. Reads 2+ pattern-library.md files, walks them category by category, identifies where apps converge (strong signal), where they diverge (genuine design choice), what's unique to one app, and what's absent across the set. Produces an opinionated comparison document with recommendations for a new build. No browser needed — pure markdown analysis. Trigger with 'compare UX patterns', 'how do top apps handle X', 'ux comparison', 'pattern comparison across reference apps'.
phxreview
Review code with parallel agents — tests, security, Ecto, LiveView, Oban. Use after implementation to catch bugs and anti-patterns before committing.
linear
Manage Linear issues, projects, and teams via the GraphQL API. Create, update, search, and organize issues. Uses API key auth (no OAuth needed). All operations via curl — no dependencies.
add-linear
Add Linear channel integration via Chat SDK. Issue comment threads as conversations.
kv-storage
Use the swarm KV store (Redis-like, namespaced) for cross-task / cross-session / per-page state. Auto-scoped to your context (Slack thread / PR / Linear issue / agent / page). Use for counters, cursors, page state. Do NOT use for secrets (`swarm_config`), embedded knowledge (`memory`), or files (`agent-fs`).
ops-linear
Linear command center. Shows current sprint, creates/updates issues, manages priorities, syncs with GSD phases.
linear-issues-write
Create and update Linear issues via CLI (write operations)
ui-craft-dense-dashboard
Dense dashboard / admin / Bloomberg / Retool / data-heavy internal tools. Locked knobs: CRAFT=7, MOTION=3, DENSITY=9. IBM Plex + mono numbers, semantic palette, 4/8px grid, sparklines, tabular-nums. Trigger on: dashboard, admin panel, data-dense, analytics, Bloomberg-like, Retool-like.
vellum-pr-readiness
Prepare Vellum Assistant branches for review by checking git hygiene, PR scope, tests, docs, migrations, Linear linking, and companion repo needs. Use before creating a pull request, splitting work into PRs, or asking whether a branch is ready.
linear-claude-skill
Manage Linear issues, projects, and teams
linear
Managing Linear issues, projects, and teams. Use when working with Linear tasks, creating issues, updating status, querying projects, or managing team workflows.
linear-issues-read
List and get Linear issues via CLI (read-only operations)
linear-automation
Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels. Always search tools first for current schemas.
linear
Manages Linear issues, teams, and projects via CLI. Lists issues, creates tasks, views details, links issues, and runs GraphQL queries. Must use for "my Linear issues", "create Linear task", "link issues in Linear", "Linear API query", or any Linear project management request.
add-linear
Add Linear project management MCP integration to Deus. Gives host-side Claude Code sessions read/write access to Linear issues, projects, cycles, and workflow states via @tacticlaunch/mcp-linear.
ccc-linear-board
"View your Linear board, pick a task to work on, and sync issue status. Use when: 'linear board', 'show issues', 'pick a task', 'what should I work on', 'my Linear',…
team-issues
Import GitHub/Jira/Linear issues into the local backlog. Use with /team-issues.
closing-linear-loop
Reports completion on a Linear issue, closes the loop, and checks what should happen next at the project level. Use when the user wants to mark work done, close an issue, or replace the legacy `/linear:done` workflow.
linear-loop
Loop methodology for Linear — issue taxonomy, triage framework, spec workflow bridge, and template routing for /pm and /linear:* commands. Use when working with Linear issues or running the product loop.
running-product-loop
Reviews the current Linear product loop, recommends the most important next action, and optionally executes it. Use when asked to assess project status, decide what to do next, audit loop health, or work a specific Linear issue directly.
plan
Produce a draft PLAN-*.md file within the first few tool calls — structured for downstream consumption by /abc:scaffold-sub-issues (Linear issue creation) and /abc:ship-epic (parallel multi-repo shipping). Front-loads writing over Q&A. TRIGGER when the user says "/plan", "draft a plan for X", "write a PLAN doc", or asks Claude to plan a feature/migration/refactor before implementation.
review-epic
Linear · Review-only counterpart to /abc:ship-epic. Self-arming /loop that watches a Linear parent issue's sub-issues, reviews each child's PR/MR (GitHub or GitLab, routed via the `repo:` label) as it surfaces against the FULL epic context (parent spec + merged-sibling decisions + pending children's criteria), posts inline + spec-cross-referenced summary comments via the abc:reviewer subagent, and exits when the parent reaches Done. Never merges. TRIGGER when the user says "/abc:review-epic PARENT-ID", asks to "review this epic as it ships" against a Linear parent, or wants a standing reviewer session running parallel to /abc:ship-epic.
scaffold-sub-issues
Linear · Read one or more PLAN-*.md files and turn them into Linear sub-issues. Either creates a new parent issue from the plan (auto-detect mode) or adds sub-issues to an existing parent (when a parent ID is passed). Handles repo labels, blocks/blocked-by relations, and the manual-validation gate for /abc:ship-issue. Output is a parent ID you can paste into /abc:ship-issue or /abc:ship-epic. TRIGGER when the user says "/scaffold-sub-issues", "create Linear issues from this plan", "scaffold sub-issues for PARENT-ID", or passes a PLAN-*.md path.
ship-issue
Linear · Drives a Linear issue (or list, or parent with sub-issues) from Backlog to Done through the implement → PR → address-review → merge loop. TRIGGER when the user says "/ship-issue TICKET-ID", asks to ship/land/drive/autoland a ticket, or wants Claude to take a Linear issue through review to merge. Also trigger when resuming work on a ticket with an open PR and pending reviewer comments. Supports GitHub + GitLab and multi-repo parent issues via `repo:` Linear labels. Self-arms its own `/loop` — the user invokes once and walks away.
memory-entity-bootstrap
Enrich a low-info entity by pulling source data specifically about it. Triggers when ingest or refresh encounters an entity that's being newly created OR an existing entity with too few memories (< 5) that just got touched by new activity. Searches the user's enabled source MCPs (Slack history, Linear issues, Notion pages, Gmail threads, Granola meetings) for content about this entity, then synthesizes a richer canonical entity file or adds the missing context as new memories. Use when '/memory-refresh' wants to deep-dive a specific entity, or when 'memory-master-ingest' is about to create a new entity it should bootstrap properly first.
backlog
Maintain Linear backlog at ~50 items by generating context-aware feature ideas based on the platform's current capabilities.
compact-fix
Restore context after chat compaction by retrieving the execution plan and checking current progress.
create-pr
Create a pull request with automatic Linear + Vercel integration. Links to issue, attaches preview deployment, and updates Linear status.
feature-from-backlog
Start a new feature from Linear backlog. Refines backlog item, breaks into sub-tasks if needed, and starts work.
new-feature
Start a new feature with full Linear + Git workflow. Use when beginning new feature development or checking project status.
project-status
Show comprehensive project status across Linear, Git, and Vercel. See what's in progress, in review, and deployed.
quick-start
Zero-friction backlog-to-implementation. Takes a backlog item, analyzes codebase, creates plan + sub-issues, and starts work immediately.
setup-project
Set up a new project for the Claude Code SaaS workflow system. Creates .claude/project.json with Linear, GitHub, and Vercel configuration.
linear-issue-manager
Linear Issue Manager is built around GraphQL API ecosystem. The underlying ecosystem is represented by graphql/graphql-js (20,335+ GitHub stars). It gives an agent a more technical and reliable way to work with the tool than a thin one-line wrapper, using stable interfaces like queries, mutations, schema introspection, fragments, pagination, subscriptions and preserving the operational context […]
capturing-linear-ideas
Captures a new idea into the Linear backlog as a type/idea issue without doing full triage. Use when the user wants quick idea capture, backlog intake, or a direct replacement for the legacy `/linear:idea` workflow.
pickup-task
Claim the next ready task from the configured tracker (Linear / GitHub Issues / Notion), create a git worktree, and inject relevant learnings.
plan-task
Run Plan mode for the current task. Outputs structured plan; required before /implement.
push-to-tracker
Push phases.yaml to the configured tracker (linear|github|notion) — creates project, per-phase grouping, issues with depends_on relations.
reconcile
Bidirectional sync between plans/phases.yaml and the configured tracker. --pull reads tracker → phases.yaml; --push writes phases.yaml → tracker bodies via updateIssueBody.
ship
Push branch, run final gates (tests, secrets scan, conventional commit), open PR with Linear issue ID, mark issue In Review.
qa
Run test suite, browser checks, and verify acceptance criteria. Bootstrap test framework if missing.
linear-claude-skill
Manage Linear issues, projects, and teams
linear-workspace
Linear issue management — routes work to specialized agents and slash commands. Use when: creating, updating, searching, bulk-editing, cleaning up, syncing Linear. TRIGGERS: "linear", "ticket", "issue", "create issue", "update issue", "search issues", "my issues", "bulk", "cleanup", "sync", "log bug", "file issue", "report bug", "new ticket", "add task", "open ticket", "open issue", "throw this in linear", "track this in linear", "capture as issue", "put on the backlog".
coverage-pass
Compatibility mode for Symphony Requirements Elicitation. Use when Pedro asks whether stakeholder input, bugs, requirements, or meeting/chat follow-ups are covered in Linear/docs; report coverage gaps first and mutate Linear only when Pedro asks to fix coverage.
evidence-intake
Preserve meeting, call, audio-note, transcript, Drive, Gmail, or local media evidence before Symphony issue intake, coverage passes, review artifacts, or Linear extraction. Do not create Linear issues by default.
implementation-dispatch
Use when Pedro has approved a Linear work packet and wants Symphony to create a fresh Codex thread/agent to implement it. This skill takes the approved Linear issue plus source pointers, creates a separate implementation thread, sends a bounded prompt, and reports the new thread back without implementing in the current thread.
merge
Run the explicit Symphony publish/merge/release-proof lifecycle: branch, PR, merge, rollout babysitting, tracker reconciliation, and worktree cleanup across GitHub, Azure DevOps, or another repo host.
linear-issue-workflow
Linear Issue (1 PEV task に相当する作業単位) を AI agent が読む・書く・更新するときの規約と template (v3.4.0+)。 project (Why/What 容器) は linear-project-workflow、 issue 単位の PEV pipeline 入出力は pev-linear-sync。 この skill は issue 自身の命名規則 / template / Good-Bad パターンを提供する
linear-project-tracker
Linear Project の進捗監視と完了判定。 child issue 群の状態を読み取り、 全 Done なら project status を completed 候補と判定する。 linear-project-workflow とは責務分離 (workflow = active 操作、 tracker = 監視と判定)。 pev-linear-sync の outbound success 後の after-hook として呼ばれることが多い。
linear-project-workflow
Linear Project (機能・ユーザーストーリー単位の Why/What 容器) を AI agent が読む・書く・更新するときの規約と template。 1 issue で完結する作業は対象外 (linear-issue-workflow を使う)。 進捗監視は linear-project-tracker に委ねるが、 必要な場面では status 遷移も担う。
pev-linear-sync
Linear MCP server 経由で plan.md / verify.json を Linear Issue と双方向 sync。inbound (Linear → spec 抽出)、issue-first (実装前に issue 作成 + branch checkout、v3.3.0+)、outbound success (Done + コメント)、outbound fail (failure summary コメント) の4方向。Linear MCP plugin (`@plugin_linear_linear`) が install済みで認証済みであることが前提
linear-issue-craft
Use when creating, drafting, or rewriting Linear issues (epics, stories, hardening tickets, refactor tasks) in any workspace. Trigger when the user says "draft an issue", "open an epic", "file a ticket", "write a Linear issue", or pastes a rough idea or bug report and asks for it to be filed.
dev-workflow
SDLC workflow with MCP tools. Triggers on "start", "implement", "work on", or unclear workflow.
launchpad
End-to-end planning and execution orchestrator. Chains SPARC or wave-planner (Stage 1), plan-review, linear, and hive-workers-skill into a single workflow. Automatically routes infra changes through SPARC research instead of wave-planner. Use when starting a new initiative, executing a set of Linear issues, or running plan-to-deployment.
linear
Managing Linear issues, projects, and teams. Use when working with Linear tasks, creating issues, updating status, querying projects, or managing team workflows.
linear-issue-writer
Internal/compatibility rules for writing grounded Linear issues from Symphony Requirements Elicitation. Use when Pedro explicitly asks to write/rewrite a Linear issue body, or when another Symphony skill needs concise issue-body policy.
linear
Manage issues, projects & team workflows in Linear. Use when the user wants to read, create or updates tickets in Linear.
saas-reverse
Reverse-engineer any SaaS into a venture-analyst-grade build blueprint. Scrapes the domain, gathers multi-source intelligence (reviews, HN, Reddit, job listings), and outputs a production-ready blueprint with moat analysis, churn vectors, upgrade gates, and a build prompt.
session-cleanup
End-of-session housekeeping for git repositories. Use when the user asks to 'end of session', 'clean up session', 'session housekeeping', 'clean up branches', 'clean up worktrees', or 'clean up remote branches'.
plan-design
Design planning entry point — reads DESIGN.md, CONTEXT.md, and ADRs plus a Linear issue, identifies all UI surfaces that need design, lets you choose which to work through, then for each surface conducts an alignment interview, generates three layout-archetype mockups via OpenAI image generation, lets you pick one, produces an HTML/CSS implementation, and attaches it to the Linear issue. Use when starting design work on any feature, when you need visual options before committing to layout, or any time you want a Linear ticket to carry its own design artifacts.
plan-qa
Test-planning entry point — reads a Linear issue and its acceptance criteria (plus the repo's test conventions if available), then drafts a comprehensive, layer-aware test plan — per-AC scenarios (happy path, edge, negative) each tagged with a test layer and an expected result, the auth roles / fixtures / data setup needed, the visual states to verify, and the regression watch areas. Shows you the draft for approval, then attaches it to the ticket as <issue-id>-test-plan.md so the qa skill can execute against it later. Use this skill whenever you are refining or grooming a ticket, planning QA before implementation, or whenever someone says "/plan-qa", "plan the QA", "write a test plan", "what should we test for this ticket", "QA plan", "test strategy for this issue", or "how do we verify this" — even if they don't say the words "plan-qa".
qa
Software QA skill — validates that current code changes satisfy the linked Linear issue. Fetches the issue, reads acceptance criteria, executes the ticket's attached test plan when one exists (produced by /plan-qa), runs every test layer it finds, and uses Playwright to visually verify the UI against any design attachments on the ticket. Use whenever the user wants to QA a feature, verify a fix, check that code matches a ticket's acceptance criteria, run a pre-merge review, or confirm the UI looks right against a design. Trigger on — "/qa", "run QA", "QA this", "verify the feature", "does this match the ticket", "check AC", "acceptance criteria check", "visual QA", "playwright verify", "does this pass QA".
new-feature
Start a new feature for this project. Use when the user says "start a feature", "plan X", "new feature", "begin work on", "let's build X", or picks up a Linear issue to work on. Sets up the run folder, writes a plan with the Three-Surface Rule and test approach baked in, and claims the Linear issue.
gsd-to-linear
Migrate a repo's GSD (.planning/) data to Linear issues. Use this skill when the user wants to transition from GSD to Linear, move planning data to Linear, import GSD phases into Linear, or asks about migrating their .planning/ directory. Also triggers on "migrate to linear", "move GSD to linear", "import planning to linear", or any mention of converting GSD phases/plans into Linear issues. Only relevant for repos that have a .planning/ directory.
linear-seed
Capture project ideas as lightweight Linear issues before they become real repos. Use when the user floats an idea, riffs on a concept, says "what if we...", "we should build...", "imagine if...", "idea:", or any variation of sharing a project idea they're not ready to commit to. Also triggers on "catch this idea", "pin this thought", "seed this", or "add to the wall". This is the sticky-note-on-the-studio-wall skill.
linear-workflow
Track work in Linear via linctl without leaving your editor. Use this skill whenever the user describes work to be done — feature requests, bugs, improvements, things to build, things to fix. Also use it when the user explicitly asks to create an issue, check what's open, or work on a ticket. Triggers on intent like "let's build X", "we need to fix Y", "add support for Z", "X is broken", "it would be nice if", "what's ready", "what should I work on next", "what's on the board", as well as explicit "create an issue". If this skill is loaded in your context, use Linear for task tracking.
executor
Load before using the `execute` tool, external systems, and configured MCP/OpenAPI/GraphQL integrations. Use `tools.search({ ... })`, then `tools.describe.tool({ path })`, then call the full `tools.<namespace>.<tool>(args)` path.
prospect-temporal-gate
Enforces the Brite Labs 2-cycle/year + 180-day non-repeat hard rule by querying EB workspaces 55+13 plus SF Activity history and emitting a suppression-aware filtered prospect list. Runs as a mandatory pre-enrichment gate inside list-building Workflow 2. Triggers "temporal gate", "180-day check", "non-repeat enforcement", "cycle dedup", "outreach recency suppression".
brainstorming
Socratic discovery and design exploration before planning. Activates when objective complexity criteria are met (2+ modules, 4+ tasks, 2+ approaches, or new patterns/integrations) — asks clarifying questions, explores alternatives and tradeoffs, produces a design document for approval. Pulls context from Linear issue description, linked docs, and existing CLAUDE.md learnings.
git
git workflows for agents: ship (stage → commit → push), worktree (parallel branches), hunks (selective staging). never force push, never git add -A, conventional commits. triggers on: commit, push, stage, ship, git add, worktree, hunks, selective staging.
linear-editing
Render Linear issues as an interactive inline editor for review and edit before saving. Works for fresh drafts AND substantive edits to existing issues (title and/or description). A freeform prompt field captures next-turn instructions. Use when the user wants to draft new Linear issues OR rewrite the title or description of an existing issue inline, including phrases like "draft a Linear issue", "queue up Linear tickets so I can edit", "look at SAPP-1234 and let's edit the description", or "rewrite the description of X". The widget IS the editing surface; do not draft the content as Markdown prose first. Do not trigger for read-only queries (list, search, assign, comment). Do not trigger for single-field swaps ("change the title to X"); apply those inline. Do not trigger for one-shot create-and-save with no review step.
issue-quality-gate
Apply 7 quality checks to a single Linear issue object. Returns pass/fail per check. Phase 1 audit and Phase 2 scope both consume this skill.
logics-connector-linear
Connect Linear (GraphQL) to the Logics workflow: list issues and import a Linear issue into `logics/backlog/` as a new `item_###_*.md` with a link back to Linear.
git-workflow
Use this skill when the user asks to commit changes, create a branch, open a pull request, or update a PR description.
Integration detected automatically from skill content. Some results may be false positives.