project-flow-ops
Operate execution flow across GitHub and Linear by triaging issues and pull requests, linking active work, and keeping GitHub public-facing while Linear remains the internal execution layer. Use when the user wants backlog control, PR triage, or GitHub-to-Linear coordination.
npx skills add mturac/everything-openai-codex --skill project-flow-ops --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Project Flow Ops This skill turns disconnected GitHub issues, PRs, and Linear tasks into one execution flow. Use it when the problem is coordination, not coding. ## When to Use - Triage open PR or issue backlogs - Decide what belongs in Linear vs what should remain GitHub-only - Link active GitHub work to internal execution lanes - Classify PRs into merge, port/rebuild, close, or park - Audit whether review comments, CI failures, or stale issues are blocking execution ## Operating Model - **GitHub** is the public and community truth - **Linear** is the internal execution truth for active scheduled work - Not every GitHub issue needs a Linear issue - Create or update Linear only when the work is: - active - delegated - scheduled - cross-functional - important enough to track internally ## Core Workflow ### 1. Read the public surface first Gather: - GitHub issue or PR state - author and branch status - review comments - CI status - linked issues ### 2. Classify the work Every item should end up in one of these states: | State | Meaning | |-------|---------| | Merge | self-contained, policy-compliant, ready | | Port/Rebuild | useful idea, but should be manually re-landed inside ecc
- When to Use
- Operating Model
- Core Workflow
- 1. Read the public surface first
- 2. Classify the work
- 3. Decide whether Linear is warranted
- 4. Keep the two systems consistent
- Review Rules
- Output Format
- Good Use Cases
What does the project-flow-ops skill do?
Operate execution flow across GitHub and Linear by triaging issues and pull requests, linking active work, and keeping GitHub public-facing while Linear remains the internal execution layer. Use when the user wants backlog control, PR triage, or GitHub-to-Linear coordination.
How do I install it?
Run `npx skills add mturac/everything-openai-codex --skill project-flow-ops --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mturac/everything-openai-codex, a repository with 84 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.