project-flow-ops

To link GitHub issues and PRs to Linear tasks, the Skill triages open backlogs and maps active work to Linear lanes, creating a unified execution flow with explicit rules for state classification and item creation.

Triageing a GitHub backlog across multiple repositories involves classifying work by state—such as merge, port, close, or park—and routing items to determine what belongs in Linear versus GitHub-only, ensuring public status aligns with internal plans.

Yes, you can synchronize GitHub PR status with internal Linear lanes by linking active GitHub work to Linear, classifying the work state, and auditing blockers and CI status to ensure smooth delivery and reduce handoffs.

Auditing CI status and blockers for GitHub and Linear workflows is handled by the Skill to ensure smooth delivery, reduce handoffs, and provide visibility into internal execution tracking without duplicating effort.

Workflow coordination requires explicit rules for when to create or update Linear items, satisfying cross-system mapping, state classification, and blocker auditing to maintain a unified execution flow across systems.

You should route GitHub issues to Linear instead of keeping them GitHub-only when backlog control, PR triage, or cross-system coordination is needed, ensuring visibility and internal execution tracking without duplicating effort.