사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/lwlee2608/agent-skills --skill linear-issues시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Work with Linear
Do all Linear work through the installed Linear MCP server.
Rules
- Use the Linear MCP tools (
mcp__linear__*:list_issues,get_issue,create_issue,update_issue,list_comments,create_comment, …). Read the actual schemas before calling — Linear renames tools without notice.
- Never fall back to the GraphQL API or web UI. If no Linear MCP server is connected, stop and tell the user to add
https://mcp.linear.app/mcp(HTTP transport) to their agent. In Claude Code:
claude mcp add --transport http linear https://mcp.linear.app/mcp- Resolve names to IDs before writing. Team, state, label, and assignee fields take UUIDs; a display name fails or silently no-ops. Call the matching
list_*tool first.
- Keep comments short. 1–3 sentences. Outcome first, link the PR instead of pasting the diff, no preamble, no recap of the ticket, no sign-off, no emoji.
Root cause: config loader reads `retry_count` but the YAML key is `retryCount`, so it binds 0. Fixed in #482.- Don't hand-move a PR-linked issue to Done. A linked PR (branch name, or
Fixes ENG-482in the title/body) moves the issue to Done on merge. Set it by hand only when no PR is linked, or the user asks.
- Confirm before writes the user did not ask for. Issues, status changes, and comments are visible to the whole team. If they asked for the write, just do it.
Verification
- Re-read the object after a write; report the identifier and URL (
ENG-482 — https://linear.app/…). - If a comment runs past ~3 sentences, cut it.

