Agent skill · marketing growth · n8n-io
n8n:community-pr-readiness-check
Checks if a community pull request is ready for human review. Verifies CLA signature, PR title format, description completeness, test coverage, and cubic-dev-ai issues, then triages to the right Linear team or recommends a close. Use when given a PR number or branch name to review, or when the user says /community-pr-readiness-check, or asks to check if a PR is ready for review.
Why this skill is useful
Adds specific commands and workflows for automating the PR readiness check process that the AI wouldn't reliably generate on its own.
What it needs
Requires gh installed locally. Requires linear account access. About 12k tokens when loaded. Last updated 2026-08-07. 199,638 stars on the source repository.
What this skill does
Community PR Readiness Check Given a PR number or branch name, determine whether it is ready for human review and take the right follow-up action. Decision tree 1. Bot author (n8n-cat-bot / aikido-autofix) → cleanup-only, no review. See "Internal automation PRs" below. 2. Auto-rejection screen matches (typo-only / unsanctioned new node / low-value) → action path D — close with the matching template. 3. All checks pass (readyForReview === true) → action path B — triage to team. 4. One or more checks fail → action path A (if title is minor-fix only) then C — post comment. Step 1 — Resolve the PR If given a branch name, find the PR number first: Step 2 — Fetch and pre-process Internal automation PRs (bot authors) If author.login is one of n8n's internal bots — n8n-cat-bot / app/n8n-cat-bot or aikido-autofix / app/aikido-autofix — skip the PR entirely and perform the cleanup actions below. Do not emit any JSON output. 1. Relabel the PR (both bots): swap community → n8n team: 2. Update the linked Linear ticket (extract GHC-XXXX per step 5): n8n-cat-bot — cancel: use the available Linear MCP issue-update tool with state: "Canceled", no labels. aikido-autofix — route to Dev Platform: use the available Linear MCP issue-update tool with team: "Developer Platform", state: "Triage", no labels. When reviewing a batch, omit the skipped PR from the output. For a single PR, emit a one-line note (e.g. Skipped & cleaned up #30591 (n8n-cat-bot): relabeled to n8n team, cancelled GHC-8398.). Collision guard If triage:in-progress is already on the PR, another reviewer is mid-triage — bail out to avoid double-processing. Emit a one-line note (e.g. Skipped #30205: already has triage:in-progress) and move on to the next PR. Do not run the checks, do not modify labels, do not touch Linear. If the user explicitly asks to re-process a PR that's stuck on triage:in-progress (e.g. a previous run crashed), they can clear the label manually and re-invoke. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills n8n-io/community-pr-readiness-check