How does it match my code to Linear tickets?

It uses a multi-tiered matching strategy: first looking for exact title matches, then partial title matches, and finally checking for specific Linear identifiers (like ENT-123).

What permissions are required for this skill?

The skill requires either a configured Linear MCP or a valid Linear API token with permissions to read issues and post comments/updates.

Does this skill automatically update my Linear issues without asking?

No. The skill generates a comprehensive preview table of all proposed changes and requires your explicit 'yes' confirmation before performing any updates.

Can it accidentally move a 'Done' issue back to 'In Progress'?

No. The skill enforces an 'Upgrade-Only' rule, meaning it will only advance an issue's status. If Linear shows a higher status than the code evidence suggests, the update is skipped.

What happens if a code component doesn't have a matching ticket?

The skill identifies these as 'No Match' and lists them separately in the report, offering you the option to create a new issue if needed.

Linear Issue Sync

Name: Linear Issue Sync
Author: my-entourage

bymy-entourage

•

Collaboration Tools

Synchronizes Linear issues with implementation progress based on real-time evidence from your code repository.

About

The Linear Issue Sync skill bridges the gap between manual project tracking and actual development reality. By analyzing your codebase status, it identifies implementation evidence—such as feature branches, merged pull requests, and CI status—and maps them to specific Linear tickets. The skill follows a safety-first approach with an 'upgrade-only' rule, ensuring that Linear statuses are only moved forward based on evidence and never downgraded automatically. It provides a detailed preview of all proposed changes, requiring explicit user confirmation before modifying any project data.

Key Features

Automated matching of code components to Linear issues via titles or identifiers
Safety-first 'Upgrade-Only' logic to prevent accidental progress loss
Evidence-based status upgrades (Backlog to In Progress, In Review to Done)
Support for both Linear MCP and direct GraphQL API fallback authentication
2 GitHub stars
Detailed change previews including current status, proposed status, and evidence

Use Cases

Updating project boards instantly after a series of commits or PR merges
Ensuring project managers see the most accurate, evidence-backed status of development
Identifying components in the codebase that are missing corresponding Linear issues

About

Key Features

Automated matching of code components to Linear issues via titles or identifiers
Safety-first 'Upgrade-Only' logic to prevent accidental progress loss
Evidence-based status upgrades (Backlog to In Progress, In Review to Done)
Support for both Linear MCP and direct GraphQL API fallback authentication
2 GitHub stars
Detailed change previews including current status, proposed status, and evidence

Use Cases

Updating project boards instantly after a series of commits or PR merges
Ensuring project managers see the most accurate, evidence-backed status of development
Identifying components in the codebase that are missing corresponding Linear issues