skills.rest
freedom909
freedom909COMMUNITY
Explore all skills by this author →
GitHub

project-flow-ops

Triages GitHub issues and pull requests and coordinates execution tracking with Linear.

Updated Mar 18, 2026
Search Tags:#project management#github#Linear#pull requests#issue tracking#backlog#triage
One-click install
npx skills add https://github.com/freedom909/real-estate-saas --skill project-flow-ops-freedom909
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-flow-ops
Source: https://github.com/freedom909/real-estate-saas/tree/main/.trae/skills/project-flow-ops
Command: npx skills add https://github.com/freedom909/real-estate-saas --skill project-flow-ops-freedom909

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams working across GitHub and Linear often lose track of which issues and pull requests need internal execution tracking, leading to stale backlogs, unlinked work, and inconsistent public versus internal status. ## Core Features & Use Cases - Backlog Triage: Classify open PRs and issues into merge, port/rebuild, close, or park states based on diffs, CI status, and review comments. - GitHub-to-Linear Coordination: Decide which GitHub work warrants a Linear issue and keep public status and internal execution lanes consistent. - Use Case: Ask the Skill to audit your open PR backlog; it returns each item's public status, a classification with rationale, the required Linear action, and the exact next operator move. ## Quick Start Audit the open PR backlog in this repository and tell me what to merge, rebuild, close, or park, and which items need Linear issues.

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 a GitHub pull request backlog?▼

Gather each PR's state, author, branch status, review comments, CI status, and linked issues, then classify it as merge, port/rebuild, close, or park. Always review the full diff rather than relying on titles or summaries.

When should a GitHub issue get a Linear issue?▼

Create a Linear issue only when work is active, delegated, scheduled, cross-functional, or important enough to track internally. GitHub remains the public truth, so not every issue needs mirroring into Linear.

How do I keep GitHub and Linear status in sync?▼

For active work, the GitHub issue or PR states what is happening publicly while Linear tracks owner, priority, and execution lane. When work ships or is rejected, post the public resolution to GitHub and update the Linear task.

What should I do when CI is failing on a pull request?▼

Treat red CI as a blocker: classify the failure and either fix it or block the PR. Do not mark the item as merge-ready, and if the real blocker is product direction, state that directly.

When should an external contribution be rebuilt instead of merged?▼

Rebuild externally sourced features inside your own codebase when the idea is valuable but the PR is not self-contained or policy-compliant. Classify these as port/rebuild rather than merging them directly.

Related Skills

Explore More Product & Management Skills→
TencentBlueKingTencentBlueKing
2.5k

github-repository-management

Manages GitHub repository collaboration workflows including issues, pull requests, reviews, and merge checks via GitHub MCP.

Official
Intermediate
arbisoftarbisoft
4

project-flow-ops

Triage GitHub issues and PRs into Linear tasks with public status updates.

Official
Intermediate
thrawn01thrawn01
11

babysit-pr

Monitor and fix CI failures and automated review comments on a pull request.

Community
Advanced
ROYCE-8425ROYCE-8425
1

project-flow-ops

Categorize GitHub issues and pull requests and create corresponding Linear tasks.

Community
Intermediate