project-flow-ops

Analyze GitHub issues and pull requests to recommend Linear task actions.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/abhishekdutta18/blogspro --skill project-flow-ops-abhishekdutta18
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-flow-ops
Source: https://github.com/abhishekdutta18/blogspro/tree/main/.claude/skills/project-flow-ops
Command: npx skills add https://github.com/abhishekdutta18/blogspro --skill project-flow-ops-abhishekdutta18

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams coordinate issues and pull requests across GitHub and Linear systems, enabling efficient backlog triage, linking active work, and maintaining consistency between public and internal workflows.

Core Features & Use Cases

  • Issue and PR triage: Assessing the state, review comments, CI status, and linked issues for efficient classification.
  • Work management: Deciding whether to create, update, or omit Linear tasks based on the work’s activity level and cross-repo involvement.
  • Review and synchronization: Ensuring GitHub and Linear statuses reflect actual project progress, reducing manual oversight.

Quick Start

Provide a GitHub PR or issue link and request an assessment of its status, classification, and recommended next steps.

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

To triage GitHub issues and pull requests with Linear, you provide the PR or issue link to assess CI status and review comments, then recommend whether to create or update a Linear task for tracking.

What is the best way to keep Linear tasks in sync with GitHub issues?

Keeping Linear tasks in sync with GitHub issues involves analyzing the issue activity and PR state to classify them, then updating the linked Linear task to reflect actual project progress and reduce manual oversight.

When should I create a Linear task for a GitHub pull request?

You should create a Linear task for a GitHub pull request when the work is active and involves cross-repo coordination, ensuring that public and internal workflows remain consistent and linked.

Does this issue management workflow assess CI status and review comments for backlog triage?

Yes, this issue management workflow assesses CI status and review comments during backlog triage to determine the current status of GitHub issues and pull requests for appropriate classification.

Can I use this to classify cross-repo work for Linear task creation?

You can use this to classify cross-repo work by analyzing GitHub issues and pull requests to decide whether to create, update, or omit Linear tasks based on the work's activity level.