Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

[Extension]: Update Linear Weave to v1.0.2

オープン 初心者向け
#5,045 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
2/5
見積もり時間
1〜3時間
初心者へのやさしさ
70/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
領域
release

調査の方向性

まず、既存のカタログエントリ linear-weave を読みます。このエントリは #3603 で最初に追加され、#3758 で最後に更新されました。そのバージョンとダウンロードURLを、このissueで提案されているエントリと比較し、それらのフィールドを1.0.2とv1.0.2のアーカイブURLに更新します。残りのフィールドが変更されていないことと、カタログが新しいリリースを指していることを確認します。

索引モデルが issue の本文から書いたものです。

説明

Extension ID

linear-weave

Extension Name

Linear Weave

Version

1.0.2

Description

Weave Spec Kit into Linear: pull requirements, mirror tasks.md into sub-issues, sync statuses.

Author

Tony Woodhouse

Repository URL

https://github.com/tonydwoodhouse/spec-kit-linear-weave

Download URL

https://github.com/tonydwoodhouse/spec-kit-linear-weave/archive/refs/tags/v1.0.2.zip

License

MIT

Homepage (optional)

https://github.com/tonydwoodhouse/spec-kit-linear-weave

Documentation URL (optional)

https://github.com/tonydwoodhouse/spec-kit-linear-weave/blob/main/README.md

Changelog URL (optional)

https://github.com/tonydwoodhouse/spec-kit-linear-weave/blob/main/CHANGELOG.md

Required Spec Kit Version

=0.13.0,<1.0.0

Required Tools (optional)
linear-mcp (required) — a connected Linear MCP server in the coding agent (Claude Code: /mcp, or the claude.ai connector settings). All hooks no-op silently when the MCP server is unavailable, so the plain Spec Kit workflow is never blocked. Declared in extension.yml's requires.tools since v1.0.1.
Number of Commands

5

Number of Hooks (optional)

5

Tags

linear, issue-tracking, integration, workflow

Key Features
  • Pulls requirements from a referenced Linear issue (before_specify) and links the feature back to it (after_specify) — the only local state is one **Linear Issue**: line in spec.md.
  • Mirrors tasks.md into Linear sub-issues at configurable granularity — task, phase, or story (one sub-issue per user story + a shared bucket; minimises issue count). Deduplicates on re-runs and places sub-issues on the parent's project board.
  • Reconciles tasks.md checkbox state with Linear statuses during implement (before/after_implement), rewriting per-task checklists inside story/phase sub-issues. Idempotent.
  • Ships a guided one-chat orchestrator (/speckit-linear-weave-flow) that runs specify → clarify → plan → tasks with a review gate after each phase, isolating heavy phases in subagents. Stops before implement.
  • All hooks no-op silently when a feature isn't linked to Linear, so the plain Spec Kit workflow is never blocked.
  • New in 1.0.2: documentation consistency fixes — story is consistently identified as the shipped default granularity, and the README describes status transitions via the configurable statuses.in_progress / statuses.done values.
Testing Checklist
  • Extension installs successfully via download URL
  • All commands execute without errors
  • Documentation is complete and accurate
  • No security vulnerabilities identified
  • Tested on at least one real project
Submission Requirements
  • Valid extension.yml manifest included
  • README.md with installation and usage instructions
  • LICENSE file included
  • GitHub release created with version tag
  • All command files exist and are properly formatted
  • Extension ID follows naming conventions (lowercase-with-hyphens)
Testing Details

Tested on:

  • Windows 11 with Spec Kit v0.13.0

Test project: a real feature workflow in a private project, linked to Linear issues.

Test scenarios:

  1. Installed extension from the GitHub release v1.0.1 into a real project
  2. Configured linear-config.yml (default story granularity)
  3. Ran a full /speckit-linear-weave-flow (specify → clarify → plan → tasks) against a Linear issue, then /speckit-implement
  4. Verified: requirements pulled from the Linear issue, spec.md linked back to it, sub-issues created per user story with correct task checklists, and all statuses reconciled to Done once tasks completed.

(End-to-end scenarios above were run on v1.0.1.) What's new in 1.0.2: documentation-only changes (command prompt wording and README); no change to extension.yml beyond the version, and no runtime behaviour change.

Example Usage
# Install extension
specify extension add linear-weave --from https://github.com/tonydwoodhouse/spec-kit-linear-weave/archive/refs/tags/v1.0.2.zip

# Use it — no Linear steps typed in chat, just reference the issue
/speckit-specify ENG-123
/speckit-clarify
/speckit-plan
/speckit-tasks
/speckit-implement

# Or drive specify -> clarify -> plan -> tasks in one guided chat using sub-agents for context management
/speckit-linear-weave-flow ENG-123
Proposed Catalog Entry
{
  "linear-weave": {
    "name": "Linear Weave",
    "id": "linear-weave",
    "description": "Weave Spec Kit into Linear: pull requirements, mirror tasks.md into sub-issues, sync statuses.",
    "author": "Tony Woodhouse",
    "version": "1.0.2",
    "download_url": "https://github.com/tonydwoodhouse/spec-kit-linear-weave/archive/refs/tags/v1.0.2.zip",
    "repository": "https://github.com/tonydwoodhouse/spec-kit-linear-weave",
    "homepage": "https://github.com/tonydwoodhouse/spec-kit-linear-weave",
    "documentation": "https://github.com/tonydwoodhouse/spec-kit-linear-weave/blob/main/README.md",
    "changelog": "https://github.com/tonydwoodhouse/spec-kit-linear-weave/blob/main/CHANGELOG.md",
    "license": "MIT",
    "requires": {
      "speckit_version": ">=0.13.0,<1.0.0",
      "tools": [{ "name": "linear-mcp", "required": true }]
    },
    "provides": { "commands": 5, "hooks": 5 },
    "tags": ["linear", "issue-tracking", "integration", "workflow"]
  }
}
Additional Context

Update to the existing linear-weave entry (originally #3603, last updated via #3758). Only the version and download URL change, to 1.0.2. This release fixes documentation inconsistencies reported in https://github.com/tonydwoodhouse/spec-kit-linear-weave/issues/1: the tasks command no longer labels task as the default granularity (story is the shipped default), and the README describes status transitions via the configurable statuses.done value rather than a literal Done. All other fields are unchanged.

主要言語
Python
スター
142k
フォーク
12.7k
平均マージ
23時間 11分
マージ済み PR(30日)
194

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

github/spec-kit のほかの issue

github/spec-kit の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。