linear-milestones-read

Bind's avatarfrom Bind

List Linear project milestones via CLI (read-only operations)

⭐4stars🔀0forks📁View on GitHub🕐Updated Jan 8, 2026
[Project Management]

When & Why to Use This Skill

This Claude skill provides a streamlined way to access and list Linear project milestones directly through a command-line interface. Designed for efficiency and read-only safety, it allows users to quickly retrieve milestone data for specific projects or across the entire organization, facilitating better project tracking and visibility without leaving the terminal.

Use Cases

  • Scenario 1: Quickly checking the status and deadlines of milestones for a specific project (e.g., 'Mount Vernon') to ensure team alignment.
  • Scenario 2: Generating a comprehensive list of all active milestones across multiple projects for high-level roadmap reviews or weekly status reporting.
  • Scenario 3: Exporting milestone data in JSON format to integrate with other developer tools, custom dashboards, or automated reporting scripts.
namelinear-milestones-read
descriptionList Linear project milestones via CLI (read-only operations)
version1.0.0
licenseMIT
compatibilityopencode

Overview

CLI tools for reading Linear project milestones. Requires LINEAR_API_KEY set in <git-root>/.env or exported in the environment.

Prerequisites

  • bun runtime installed
  • LINEAR_API_KEY set in <git-root>/.env or environment

Commands

List Milestones

bun .opencode/skill/linear-milestones-read/list-milestones.js [options]

Options:

  • --project <name> - Filter by project name (required unless using --all)
  • --all - List milestones across all projects
  • --limit <n> - Max results (default: 25)
  • --json - Output as JSON

Examples:

bun .opencode/skill/linear-milestones-read/list-milestones.js --project "Mount Vernon"
bun .opencode/skill/linear-milestones-read/list-milestones.js --all --limit 10
bun .opencode/skill/linear-milestones-read/list-milestones.js --project "Monticello" --json

Output Behavior

  • Command output is displayed directly to the user in the terminal
  • Do not re-summarize or reformat table output - the user can already see it
  • Only provide additional commentary if the user explicitly requests analysis, filtering, or summarization
  • When using --json output with tools like jq, the processed results are already visible to the user

Notes

  • Project names support partial matching (case-insensitive)