skills.rest
Maelwalser
MaelwalserCOMMUNITY
Explore all skills by this author →
GitHub

project-flow-ops

Triage GitHub issues and pull requests into Linear execution flows.

Updated Aug 23, 2026
Search Tags:#workflow#github#linear#triage#pull-request#issue-triage
One-click install
npx skills add https://github.com/Maelwalser/claude-config --skill project-flow-ops
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-flow-ops
Source: https://github.com/Maelwalser/claude-config/tree/main/skills/project-flow-ops
Command: npx skills add https://github.com/Maelwalser/claude-config --skill project-flow-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces coordination friction by turning disconnected GitHub issues, pull requests, and Linear tasks into a single, actionable execution flow so teams can decide what to merge, port, close, or track internally.

Core Features & Use Cases

  • Backlog Triage: Audit open PRs and issues to classify them as merge, port/rebuild, close, or park.
  • GitHub-to-Linear Mapping: Decide when to create or update Linear tasks for active, delegated, or cross-functional work and keep public and internal states consistent.
  • Execution Guidance: Surface CI and review blockers, recommended next operator actions, and a concise one-paragraph rationale for decisions.
  • Use Case: Run a backlog audit to map community-submitted PRs into MCC program lanes and generate exact next steps for maintainers.

Quick Start

Triage the repo's open pull requests and issues, classify each into merge/port-rebuild/close/park, and indicate whether to create, update, or skip a Linear task along with the exact next operator action.

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 issues into Linear tasks?▼

Triage GitHub pull requests and issues into Linear tasks by inspecting metadata, CI status, and linked issues to classify each item as merge, port, close, or park. The workflow then recommends whether to create, update, or skip a Linear task for each item.

What is the best way to coordinate GitHub and Linear backlogs for multi-repo programs?▼

Coordinating GitHub and Linear backlogs for multi-repo programs requires auditing open PRs and issues, classifying them into execution lanes, and mapping them to Linear tasks to keep public and internal states consistent across repositories.

Can I use this to decide whether to create or update Linear tasks for community-submitted PRs?▼

Yes, you can decide whether to create or update Linear tasks for community-submitted PRs by reviewing PR metadata, CI blockers, and linked issues to generate exact next operator actions for maintainers.

When should I not create a Linear task for an open GitHub issue?▼

You should skip creating a Linear task when the triage classifies a GitHub issue or PR to close or park, meaning no active internal tracking is required for that item.

Does this workflow handle CI and review blockers when mapping GitHub issues to Linear?▼

Yes, the workflow handles CI and review blockers by inspecting review and CI status during triage, surfacing these blockers alongside a concise rationale for each merge, port, close, or park decision.

Related Skills

Explore More Product & Management Skills→
ma08ma08
28

gh-address-comments

Fetches and triages GitHub PR comments via CLI.

Community
Intermediate
MomoDavilukeMomoDaviluke
2

project-flow-ops

Coordinate GitHub issues and PRs with Linear tasks for execution flow.

Community
Intermediate
xg-gh-25xg-gh-25
36

health-check

Execute deterministic health checks on SwarmAI subsystems and summarize pass/fail results for CI workflows.

Community
Advanced
breethomasbreethomas
16

lno-prioritize

Categorize backlog items into Leverage, Neutral, and Overhead categories.

Community
Intermediate