project-flow-ops

Triage GitHub issues and pull requests into Linear tasks.

2|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/klu-dev/porting-ecc-to-vscode --skill project-flow-ops-klu-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-flow-ops
Source: https://github.com/klu-dev/porting-ecc-to-vscode/tree/main/.github/skills/project-flow-ops
Command: npx skills add https://github.com/klu-dev/porting-ecc-to-vscode --skill project-flow-ops-klu-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of managing the flow of work across GitHub and Linear, helping users triage issues and pull requests effectively and link them to corresponding Linear tasks for better execution flow.

Core Features & Use Cases

  • Triage PRs and Issues: Efficiently sort and categorize GitHub issues and pull requests.
  • Link to Linear Tasks: Create and update Linear tasks for active GitHub work, maintaining clear internal execution tracking.
  • Classify Work: Distinguish between mergeable, rebuildable, closeable, and parkable work items.
  • Ensure Consistency: Maintain synchronization between public GitHub information and internal Linear execution details.
  • Use Case: "Use the 'project-flow-ops' skill to review and categorize open pull requests into 'Merge', 'Port/Rebuild', 'Close', or 'Park' and link the corresponding tasks in Linear."

Quick Start

Run 'project-flow-ops skill --classify' to start the PR triage process and classify each item accordingly.

Frequently Asked Questions about project-flow-ops

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

FAQPage Schema
How do I triage GitHub pull requests and link them to Linear tasks?

Run the 'project-flow-ops' skill to sort and categorize open GitHub PRs into Merge, Port/Rebuild, Close, or Park, and automatically create corresponding Linear tasks for tracking.

What is the best way to synchronize GitHub issues with Linear execution tracking?

Synchronizing GitHub issues with Linear execution tracking is handled by classifying work items and creating or updating corresponding Linear tasks, maintaining consistency between public GitHub information and internal Linear execution details.

How does PR triage classification work for GitHub repositories?

PR triage classification works by sorting and categorizing GitHub issues and pull requests into mergeable, rebuildable, closeable, and parkable work items, then linking them to corresponding Linear tasks for effective project coordination.

Can I use project-flow-ops to manage work coordination across GitHub and Linear without other dependencies?

Yes, you can use project-flow-ops to manage work coordination across GitHub and Linear without external dependencies, as it runs entirely through internal scripts to automate issue and PR triage, task classification, and synchronization.

What are the limitations of automated issue triage between GitHub and Linear?

The limitations of automated issue triage between GitHub and Linear involve relying on the classification logic to distinguish between mergeable, rebuildable, closeable, and parkable items, meaning manual review may be needed for complex or ambiguous PRs.