linear — community linear, lobe-windos-build, community, ide skills

v1.0.0

이 스킬 정보

Linear를 사용하여 프로세스를 최적화하고 워크플로우를 자동화해야 하는 개발 에이전트에게 완벽 Linear issue management. MUST USE when: (1) user mentions LOBE-xxx issue IDs (e.g. LOBE-4540), (2) user says linear, linear issue, link linear, (3) creating PRs that reference Linear issues. Provides workflows for retrieving issues, updating status, and adding comments.

Staysr Staysr
[0]
[0]
Updated: 3/11/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for teams, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution
Review Score
7/11
Quality Score
33
Canonical Locale
en
Detected Body Locale
en

Linear를 사용하여 프로세스를 최적화하고 워크플로우를 자동화해야 하는 개발 에이전트에게 완벽 Linear issue management. MUST USE when: (1) user mentions LOBE-xxx issue IDs (e.g. LOBE-4540), (2) user says linear, linear issue, link linear, (3) creating PRs that reference Linear issues. Provides workflows for retrieving issues, updating status, and adding comments.

이 스킬을 사용하는 이유

에이전트가 Linear 워크플로우와 MCP 도구를 사용하여 문제 추적 및 해결을 자동화할 수 있도록 하며, 'Fixes LOBE-xxx'와 같은 마법의 키워드를 제공하여 참조된 Linear 문제에 대한 PR 생성 및 완료 댓글을 무결점으로 처리

최적의 용도

Linear를 사용하여 프로세스를 최적화하고 워크플로우를 자동화해야 하는 개발 에이전트에게 완벽

실행 가능한 사용 사례 for linear

Linear 문제를 사용하여 PR를 자동으로 생성
참조된 문제에 대한 완료 댓글을 생성
Linear 워크플로우와 MCP 도구를 사용하여 문제 관리를 최적화

! 보안 및 제한 사항

  • Linear 워크플로우와 MCP 도구를 설치해야 함
  • PR 생성을 위해 특정 마법의 키워드를 사용해야 함
  • 참조된 Linear 문제에 완료 댓글을 즉시 추가해야 함

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is linear?

Linear를 사용하여 프로세스를 최적화하고 워크플로우를 자동화해야 하는 개발 에이전트에게 완벽 Linear issue management. MUST USE when: (1) user mentions LOBE-xxx issue IDs (e.g. LOBE-4540), (2) user says linear, linear issue, link linear, (3) creating PRs that reference Linear issues. Provides workflows for retrieving issues, updating status, and adding comments.

How do I install linear?

Run the command: npx killer-skills add Staysr/lobe-windos-build/linear. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for linear?

Key use cases include: Linear 문제를 사용하여 PR를 자동으로 생성, 참조된 문제에 대한 완료 댓글을 생성, Linear 워크플로우와 MCP 도구를 사용하여 문제 관리를 최적화.

Which IDEs are compatible with linear?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for linear?

Linear 워크플로우와 MCP 도구를 설치해야 함. PR 생성을 위해 특정 마법의 키워드를 사용해야 함. 참조된 Linear 문제에 완료 댓글을 즉시 추가해야 함.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add Staysr/lobe-windos-build/linear. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use linear immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

linear

Install linear, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Linear Issue Management

Before using Linear workflows, search for linear MCP tools. If not found, treat as not installed.

⚠️ CRITICAL: PR Creation with Linear Issues

When creating a PR that references Linear issues (LOBE-xxx), you MUST:

  1. Create the PR with magic keywords (Fixes LOBE-xxx)
  2. IMMEDIATELY after PR creation, add completion comments to ALL referenced Linear issues
  3. Do NOT consider the task complete until Linear comments are added

This is NON-NEGOTIABLE. Skipping Linear comments is a workflow violation.

Workflow

  1. Retrieve issue details before starting: mcp__linear-server__get_issue
  2. Check for sub-issues: Use mcp__linear-server__list_issues with parentId filter
  3. Update issue status when completing: mcp__linear-server__update_issue
  4. Add completion comment (REQUIRED): mcp__linear-server__create_comment

Creating Issues

When creating issues with mcp__linear-server__create_issue, MUST add the claude code label.

Completion Comment Format

Every completed issue MUST have a comment summarizing work done:

markdown
1## Changes Summary 2 3- **Feature**: Brief description of what was implemented 4- **Files Changed**: List key files modified 5- **PR**: #xxx or PR URL 6 7### Key Changes 8 9- Change 1 10- Change 2 11- ...

This is critical for:

  • Team visibility
  • Code review context
  • Future reference

PR Association (REQUIRED)

When creating PRs for Linear issues, include magic keywords in PR body:

  • Fixes LOBE-123
  • Closes LOBE-123
  • Resolves LOBE-123

Per-Issue Completion Rule

When working on multiple issues, update EACH issue IMMEDIATELY after completing it:

  1. Complete implementation
  2. Run bun run type-check
  3. Run related tests
  4. Create PR if needed
  5. Update status to "In Review" (NOT "Done")
  6. Add completion comment immediately
  7. Move to next issue

Note: Status → "In Review" when PR created. "Done" only after PR merged.

❌ Wrong: Complete all → Create PR → Forget Linear comments

✅ Correct: Complete → Create PR → Add Linear comments → Task done

관련 스킬

Looking for an alternative to linear or another community skill for your workflow? Explore these related open-source skills.

모두 보기

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
인공지능

widget-generator

Logo of f
f

prompts.chat 피드 시스템을 위한 사용자 지정 가능한 위젯 플러그인을 생성합니다

149.6k
0
인공지능

flags

Logo of vercel
vercel

리액트 프레임워크

138.4k
0
브라우저

pr-review

Logo of pytorch
pytorch

파이썬에서 텐서와 동적 신경망 구현 및 강력한 GPU 가속 지원

98.6k
0
개발자