linear-sync

Sync Linear or Jira issue statuses with brain execution results.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/ncsound919/deterministic-brain --skill linear-sync-ncsound919
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linear-sync
Source: https://github.com/ncsound919/deterministic-brain/tree/main/skill_packs/business/linear-sync
Command: npx skills add https://github.com/ncsound919/deterministic-brain --skill linear-sync-ncsound919

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synchronize the status of Linear and Jira issues with the brain's skill execution status, reducing manual updates and keeping task visibility accurate.

Core Features & Use Cases

  • Bidirectional issue sync: automatically update Linear or Jira tasks based on brain execution results.
  • Auto-create issues on failure: capture trace and suggested fixes to drive remediation.
  • Status queries and updates: list_issues, search, and sync_status enable proactive task management.
  • Return structured results: produce a consistent output format for downstream automation.

Quick Start

Start syncing a Linear issue by providing action, team_id, title, description, and priority.

Frequently Asked Questions about linear-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync Linear issues with brain execution status automatically?

Linear issue sync updates task states based on brain execution results, reducing manual updates. Provide action, team_id, and title parameters to keep issue tracking visibility accurate.

Can I auto-create Jira issues when a brain execution fails?

Yes, auto-creating Jira issues on failure captures trace and suggested fixes to drive remediation. Configure JIRA_TOKEN, JIRA_DOMAIN, and JIRA_EMAIL to enable automatic issue creation.

What API credentials do I need to integrate Jira issue tracking with brain workflows?

Jira issue tracking integration requires JIRA_TOKEN, JIRA_DOMAIN, and JIRA_EMAIL credentials. Linear sync requires the LINEAR_API_KEY environment variable to authenticate task management actions.

Does this issue synchronization tool support searching and listing existing Linear tasks?

Yes, the tool supports list_issues and search actions for querying existing Linear tasks, alongside sync_status to proactively update issue states based on brain execution results.

What is the best way to maintain bidirectional task visibility between issue tracking and execution results?

Bidirectional task visibility is maintained by applying sync_status actions to reflect brain execution state changes back into Linear or Jira, producing structured output for downstream automation workflows.