linearlisted

# Linear CLI Interacts with Linear for issue tracking and project management using the `linear` command. ## Scope - Use for Linear issue/project/teams management via the CLI or GraphQL (`linear gql`). - Prefer built-in commands over raw GraphQL unless functionality is missing. - Keep defaults in sync with the user's config; do not hard-code team IDs/outputs. ## Install & Setup - Install: `npm install -g @0xbigboss/linear-cli` - Auth: `linear auth set` or set `LINEAR_API_KEY` - Defaults: `linear config set default_team_id TEAM_KEY`, `linear config set default_output json|table`, `linear config set default_state_filter completed,canceled` - Inspect or reset defaults: `linear config show`, `linear config unset default_output` - Config path: `~/.config/linear/config.json` (override with `--config PATH` or `LINEAR_CONFIG`) ## Prerequisites - CLI installed and on PATH - Valid Linear API key available - Team defaults set or provided per command (team key/UUID) ## Hygiene - **Branches**: Name as `{TICKET}-{short-name}` (e.g., `ENG-123-fix-auth`); prefer git worktrees for parallel work - **Commits**: Use conventional commits; ticket ID in body or trailer, not subject - **Assignment**: Assign yourself when starting work (`linear issue update ENG-123 --assignee me --yes`) - **Sub-issues**: Set parent to associate related work (requires UUID: `linear issue update ENG-123 --parent PARENT_UUID --yes`) - **Scope creep**: Create separate issues for discovered work; link with blocks rel