AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents
TypeScript ai-agentai-agent-toolsai-agentsai-agents-frameworkmcpmcp-servermcp-toolsmcpsn8n-alternativeno-code-automationworkflowworkflow-automationworkflows
docs(ai-task): one approval puts a PR in the merge queue (#16842)
Hazem Adel3c2f8300aa12
diff --git a/.agents/skills/ai-task/SKILL.md b/.agents/skills/ai-task/SKILL.mdindex 8e73699e536..d74c0199a63 100644--- a/.agents/skills/ai-task/SKILL.md+++ b/.agents/skills/ai-task/SKILL.md@@ -341,7 +341,7 @@ Run these checks and fix what you can, then show one short summary of what chang- **When both pass:** mark it ready (`gh pr ready <n>`) and ask a reviewer from CODEOWNERS.Ship card line: `✓ Greptile 5/5 · ✓ CI green`, or the blocker, for example `✗ Greptile 3/5: 2 findings`.-11. **Approved?** If `gh pr view <n> --json reviewDecision` says `APPROVED`, don't merge yet. Run **Queue** below: it puts the ticket in Ready to merge and tells the user their place. Ship card line: `✓ Approved · #2 in queue, after AI-41`.+11. **Approved?** If at least one person approved the PR and nobody requested changes (see **Approved** under Queue), don't merge yet. Run **Queue** below: it puts the ticket in Ready to merge and tells the user their place. Ship card line: `✓ Approved · #2 in queue, after AI-41`.Ask before pushing, opening the PR, or posting to Linear or GitHub. Everything goes out under the user's name.@@ -351,10 +351,12 @@ Approved PRs wait in **Ready to merge** (between In Review and Done), and the **Runs on `/ai-task queue`, when Ship finds an approval, and inside Check.-1. **Fill the column.** Linear moves a ticket here on its own when its PR is approved and green. Move in any AI ticket in In Review whose PR is approved and green but got missed. One that drops back to In Review on a new push re-enters when it's approved again.+**Approved** means at least one person approved the PR and nobody has requested changes since. Read `gh pr view <n> --json latestReviews` and ignore bots like Greptile. Don't use `reviewDecision`: it stays `REVIEW_REQUIRED` until a CODEOWNERS team approves, so a PR an AI teammate approved would never count.++1. **Fill the column.** Move every AI ticket in In Review whose PR is approved and green into Ready to merge. Linear only does this on its own when GitHub's `reviewDecision` is `APPROVED`, so don't wait for it. One that drops back to In Review on a new push re-enters when it's approved again.2. **Gather** for every ticket in Ready to merge:- Linear: priority, labels, customer requests (`list_customer_needs`), `blocks` relations, when it entered the column (`stateHistory`);- - its PR: `gh pr view <n> --json number,author,files,additions,deletions,mergeable,reviewDecision,statusCheckRollup`.+ - its PR: `gh pr view <n> --json number,author,files,additions,deletions,mergeable,mergeStateStatus,latestReviews,reviewRequests,statusCheckRollup`.3. **Kick back first.** A card leaves the queue if its PR has conflicts, red CI, changes requested, or it's sat 5 working days without merging. Move it back to In Review with a one-line comment that says why and what unblocks it (mention the owner). A stale card at the bottom is worse than no card.4. **Rank the rest, top first.** One hard rule first: a PR always sits above every queued PR that needs it (`blocks`, or "merge after #n" in the PR), so the top card can always land. Then go down the list, and only use the next rule to break a tie:1. **Something's on fire:** the "Start here" urgent list (live automations broken with no workaround, data loss or wrong data, security, billing, many customers at once).@@ -367,7 +369,7 @@ Runs on `/ai-task queue`, when Ship finds an approval, and inside Check.- state changes and kick-back comments through the Linear MCP;- the order with `node .agents/skills/ai-task/linear.mjs order AI-41 AI-57 AI-60` (top first);- no key: say where to drag each card in **Merge queue** ("drag AI-57 under AI-41").-7. **Merging.** Only the owner of the top card merges, and only their own PR. Not on top? Wait, or ask in the channel. The one exception is an urgent fix (rule 4.1), which jumps the line and says so in the channel. After a merge, Linear moves it to Done; re-rank and tell the next owner if they need to rebase.+7. **Merging.** Only the owner of the top card merges, and only their own PR. If GitHub still blocks it (`mergeStateStatus` is `BLOCKED`) on a code-owner review, put the team still requested on the card ("needs @activepieces/platform"); the owner asks them, and the card keeps its place. Not on top? Wait, or ask in the channel. The one exception is an urgent fix (rule 4.1), which jumps the line and says so in the channel. After a merge, Linear moves it to Done; re-rank and tell the next owner if they need to rebase.Think the order is wrong? Say why in the ticket and re-run `/ai-task queue`, don't drag cards around it.