project-flow-ops

Classify GitHub PRs and issues into merge, port, close, or park states.

2|Updated May 11, 2026
One-click install
npx skills add https://github.com/himanshu231204/AI_Research_agent --skill project-flow-ops-himanshu231204
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-flow-ops
Source: https://github.com/himanshu231204/AI_Research_agent/tree/main/.opencode/skills/project-flow-ops
Command: npx skills add https://github.com/himanshu231204/AI_Research_agent --skill project-flow-ops-himanshu231204

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the misalignment between public GitHub issue/PR tracking and internal Linear task management, which causes unclear ownership, duplicated work, and missed priorities for development teams.

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.
  • Cross-Platform Sync: Link active GitHub work to internal Linear execution lanes, ensuring public status updates match internal task tracking for cross-functional initiatives.
  • Backlog Auditing: Identify stale issues, CI failures, and review blockers that are holding up execution, and determine what needs internal tracking versus staying public-only. For example, use this skill to audit a backlog of 20 open PRs, classify each one, and create Linear tasks only for PRs that are part of a cross-functional product release program.

Quick Start

Use the project-flow-ops skill to triage all open pull requests in the main repository and map active ones to the appropriate Linear project lanes.

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 and pull requests with Linear task tracking?

To sync GitHub issues and pull requests with Linear task tracking, you classify open PRs and issues into merge, port, close, or park states, then map the active ones to corresponding Linear project lanes for unified execution tracking.

What is the best way to triage a large backlog of open GitHub pull requests?

Triageing a large backlog of open GitHub pull requests involves auditing each PR to identify stale issues, CI failures, and review blockers, then classifying them into merge, port, close, or park states to clear the execution path.

How does cross-platform project coordination between GitHub and Linear work?

Cross-platform project coordination links active GitHub work to internal Linear execution lanes, ensuring public-facing status updates match internal ownership tracking for cross-functional initiatives.

Can I use backlog auditing to identify which GitHub issues need internal Linear tasks?

Yes, backlog auditing identifies stale issues, CI failures, and review blockers holding up execution, determining what needs internal Linear tracking versus staying public-only.

When should I create Linear tasks for GitHub pull requests in a cross-functional release?

You should create Linear tasks for GitHub pull requests when the PRs are part of a cross-functional product release program, ensuring public status updates match internal task tracking.

Why does my GitHub PR backlog have unclear ownership and duplicated work?

Your GitHub PR backlog has unclear ownership and duplicated work due to misalignment between public issue tracking and internal task management, which can be resolved by classifying items and syncing active work to Linear lanes.