Coordinate GitHub and Linear
Your AI manages issue and pull request flow between GitHub and Linear to keep public work visible and internal tasks organized. It triages PR backlogs, links active work, and decides which items need internal tracking in Linear.
affaan-m on GitHub
Curated by PromptsEdge from a public repo · MIT license. All credit goes to the author.
What is this skill?
This skill turns disconnected GitHub issues, PRs, and Linear tasks into one execution flow.
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
Use it when the problem is coordination, not coding.
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 |
| Close | wrong direction, stale, unsafe, or duplicated |
| Park | potentially useful, but not scheduled now |
3. Decide whether Linear is warranted
Create or update Linear only if:
- execution is actively planned
- multiple repos or workstreams are involved
- the work needs internal ownership or sequencing
- the issue is part of a larger program lane
Do not mirror everything mechanically.
4. Keep the two systems consistent
When work is active:
- GitHub issue/PR should say what is happening publicly
- Linear should track owner, priority, and execution lane internally
When work ships or is rejected:
- post the public resolution back to GitHub
- mark the Linear task accordingly
Review Rules
- Never merge from title, summary, or trust alone; use the full diff
- External-source features should be rebuilt inside ECC when they are valuable but not self-contained
- CI red means classify and fix or block; do not pretend it is merge-ready
- If the real blocker is product direction, say so instead of hiding behind tooling
Output Format
Return:
PUBLIC STATUS
- issue / PR state
- CI / review state
CLASSIFICATION
- merge / port-rebuild / close / park
- one-paragraph rationale
LINEAR ACTION
- create / update / no Linear item needed
- project / lane if applicable
NEXT OPERATOR ACTION
- exact next move
Good Use Cases
- "Audit the open PR backlog and tell me what to merge vs rebuild"
- "Map GitHub issues into our ECC 1.x and ECC 2.0 program lanes"
- "Check whether this needs a Linear issue or should stay GitHub-only"
Install this skill
- 1
Get the skill — it’s free
Use the Get this skill panel. Unlocked skills stay in My skills. - 2
Download or clone the files
Download the zip, or clone the repo and copy theskills/project-flow-opsfolder. - 3
Put it where your agent looks for skills
For Claude Code, use your personal skills folder (every project) or a project’s own folder:~/.claude/skills/project-flow-ops/SKILL.md # all projects .claude/skills/project-flow-ops/SKILL.md # this project only
- 4
Just ask
No command needed. The agent reads the skill’s description and loads it on its own when your request matches.
SKILL.md frontmatter
What your agent reads to decide when to load this skill.
--- name: project-flow-ops description: 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. ---
Files
Open any Markdown file to read it here.
Related skills
View all →- Govern Project DocsFreeYour AI maintains long-lived project documentation by assigning clear roles and linking active agents to canonical sources. It helps prevent doc rot, context loss, and repeated rediscovery by organizing existing docs without adding new root files.
- ai-film-directorFreeRoutes any AI film or AI video production request to the correct stage skill and enforces the order of the 7-step pipeline. Use this skill whenever the user wants to make an AI film, an AI short, a cinematic AI video, a music video, an ad, or a historical/story-driven video with AI tools, and also whenever they say 'help me make a video with AI', 'where do I start', 'my AI video looks bad', 'my character keeps changing face', 'my shots look flat', or ask which tool or model to use for a film. Load this first, before any other film skill, even if the user names only one stage.
- Unify Notification WorkflowsFreeYour AI consolidates notifications from GitHub, Linear, desktop alerts, and other tools into one clear workflow. It manages event severity, routing, and follow-up actions to reduce noise and improve alert handling.
- Control Response LengthFreeYour AI offers you choices on how long or detailed its answers should be before responding. It estimates input complexity and token usage to suggest brief, medium, or exhaustive responses based on your request.