skills.rest
luongldptit
luongldptitCOMMUNITY
Explore all skills by this author →
GitHub

project-flow-ops

Classify GitHub issues and pull requests into Linear execution lanes.

Updated Mar 26, 2026
Search Tags:#github#linear#issue-tracking#backlog-management#workflow-coordination#pr-triage#execution-flow
One-click install
npx skills add https://github.com/luongldptit/move-ticket --skill project-flow-ops-luongldptit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-flow-ops
Source: https://github.com/luongldptit/move-ticket/tree/main/.agent/skills/project-flow-ops
Command: npx skills add https://github.com/luongldptit/move-ticket --skill project-flow-ops-luongldptit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the disjointed workflow between public GitHub repositories and internal Linear task tracking, removing the need for manual cross-referencing and reducing misalignment between public-facing work and internal execution plans.

Core Features & Use Cases

  • PR & Issue Triage: Classify open GitHub pull requests and issues into merge, port/rebuild, close, or park states to efficiently clear backlogs and prioritize work.
  • GitHub-Linear Coordination: Link active GitHub work to internal Linear execution lanes, and determine which public issues require internal tracking without unnecessary mirroring across tools.
  • Execution Audit: Review CI failures, stale issues, and review comments to identify blockers and keep cross-team workstreams aligned.
  • Use Case: Engineering teams using GitHub for public community contributions and Linear for internal project management can use this Skill to automate mapping public work to internal program lanes and resolve backlog clutter without manual effort.

Quick Start

Ask the Skill to audit your open GitHub pull request backlog, classify each item for merge, rebuild, or closure, and note which items require the creation of a corresponding Linear task.

Frequently Asked Questions about project-flow-ops

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

FAQPage Schema
How do I sync GitHub issues with Linear backlog management without manual cross-referencing?▼

Syncing GitHub issues with Linear backlog management requires linking public pull requests to internal execution lanes. This workflow classifies open GitHub work items and determines which public issues require internal tracking, eliminating manual cross-referencing and maintaining consistent status across both platforms.

What is the best way to triage open GitHub pull requests and clear backlog clutter?▼

Triageing open GitHub pull requests involves classifying each item into merge, port/rebuild, close, or park states. This backlog management process clears open PR states efficiently and identifies which items require corresponding internal Linear tasks for execution tracking.

How do I audit CI failures and stale GitHub issues to identify cross-team blockers?▼

Auditing CI failures and stale GitHub issues requires reviewing review comments and execution states to identify blockers. This execution audit keeps cross-functional engineering workstreams aligned by resolving stale items and maintaining consistent tracking across public and internal systems.

Can I use PR triage to determine which GitHub issues need internal Linear task tracking?▼

PR triage can determine internal Linear task tracking needs by evaluating public GitHub contributions against internal execution lanes. This classification process identifies which open issues require internal mirroring and which can remain tracked solely in public GitHub repositories without duplication.

Does this workflow coordination approach work for cross-functional engineering teams using GitHub and Linear?▼

Workflow coordination for cross-functional engineering teams using GitHub for public community contributions and Linear for internal project management is supported. It automates mapping public work to internal program lanes and resolves backlog clutter without manual effort across the disjointed tracking systems.

Why does misalignment occur between public GitHub tracking and internal Linear execution plans?▼

Misalignment between public GitHub tracking and internal Linear execution plans occurs due to disjointed workflows and lack of automated cross-referencing. Without classifying open PRs or linking public contributions to internal execution lanes, cross-functional teams experience status inconsistencies and unresolved blockers.

Related Skills

Explore More Product & Management Skills→
wuyuxiangXwuyuxiangX

yux-linear-pr

Create pull requests and sync Linear issue states via Git and GitHub APIs.

Community
Advanced
flutterflutter
178.3k

dart-log-failure-parser

Parse Dart and Flutter test logs to detect and summarize failure patterns.

Official
Intermediate
OmniNode-aiOmniNode-ai
3

pr-review-dev

Consolidate PR comments and CI failures, then dispatch agents to fix issues.

Official
Advanced
softmgsoftmg

github-project-management

Automate GitHub issue triage, board synchronization, and sprint planning via CLI.

Official
Advanced