メニュー
Pull Linear issues and generate a local snapshot for quick reference. Use when the user says "sync linear", "pull linear issues", "update from linear", or "show my issues".
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/opmau/claude-code-framework --skill linear-syncコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Interview the user one question at a time about a PRFAQ until shared understanding is reached. Use when the user says "prfaq", "walk through this PRFAQ", or wants to pressure-test a PRFAQ or design doc before implementation.
Pick a bug from Linear, fix it test-first, verify, and update. Use when the user says "fix issue", "fix bug", "work on known issue", or "pick a bug".
Create a new ticket for task tracking. Use when the user says "create ticket", "new ticket", or "track this".
SKILL.md を表示中
SOC 職業分類に基づく
| name | linear-sync |
| description | Pull Linear issues and generate a local snapshot for quick reference. Use when the user says "sync linear", "pull linear issues", "update from linear", or "show my issues". |
| argument-hint | [team-key] |
| user-invocable | true |
| allowed-tools | Bash, Read, Write, Glob, Grep |
| model | haiku |
Pull issues from Linear using schpet/linear-cli and generate a read-only docs/LINEAR_SNAPSHOT.md for fast local reference. Linear remains the single source of truth — this file is a cache, not a tracking system.
Verify the Linear CLI is available:
linear --version 2>/dev/null || echo "LINEAR_CLI_MISSING"
If missing, tell the user to install it:
brew install schpet/tap/lineardeno install -A --reload -f -g -n linear jsr:@schpet/linear-cli
Then authenticate: linear auth loginFetch issues from Linear. If $ARGUMENTS is provided, use it as the team key:
linear issue list --team "$ARGUMENTS" --all-states
Without arguments, fetch the current user's assigned issues:
linear issue list --all-states
Categorize issues by status and type:
Write docs/LINEAR_SNAPSHOT.md as a read-only snapshot:
<!-- LINEAR_SNAPSHOT.md — auto-generated by /linear-sync, do not edit manually -->
<!-- Last synced: YYYY-MM-DD HH:MM -->
<!-- Source: [team or "my issues"] -->
<!-- Re-generate: /linear-sync [team-key] -->
## Active Bugs
- **ENG-123** [High] Login timeout on slow connections — *In Progress*
- **ENG-124** [Medium] Stale cache after deploy — *Todo*
## In Progress
- **ENG-130** [High] OAuth flow — *In Progress*
- **ENG-131** [Medium] Rate limiting — *In Review*
## Upcoming (Top 10)
- **ENG-140** [Medium] Refactor config loader — *Todo*
- **ENG-141** [Low] Update docs — *Backlog*
## Recently Completed
- **ENG-120** [High] ~~Fix auth redirect~~ — *Done (2025-02-07)*
Report sync results:
## Linear Snapshot Updated
Source: [team or "my issues"]
File: docs/LINEAR_SNAPSHOT.md
Active bugs: [count]
In progress: [count]
Upcoming: [count]
Recently completed: [count]
For full issue details: linear issue view ENG-123 --json
$ARGUMENTS: filter by team key (e.g., ENG)/linear-synclinear issue view ENG-123 --json when you need full issue details (description, comments, etc.)/linear-update to push status changes back to Linear