n8n:community-pr-readiness-check

Assess GitHub pull requests for community compliance and triage actions.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/Rub-git/n8n-auto --skill n8n-community-pr-readiness-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n8n:community-pr-readiness-check
Source: https://github.com/Rub-git/n8n-auto/tree/main/.agents/skills/community-pr-readiness-check
Command: npx skills add https://github.com/Rub-git/n8n-auto --skill n8n-community-pr-readiness-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, node, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the assessment of community pull requests to ensure they meet the necessary criteria for human review.

Core Features & Use Cases

  • PR Readiness Assessment: Checks for CLA signature, PR title format, description completeness, test coverage, and cubic-dev-ai issues.
  • Triage Recommendations: Suggests the appropriate Linear team for review or recommends closing the PR if it doesn't meet the criteria.
  • Actionable Output: Provides a detailed JSON output with the review results and recommended actions.

Quick Start

Check the readiness of a pull request using the command: /community-pr-readiness-check <PR number>

Frequently Asked Questions about n8n:community-pr-readiness-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub pull request triage for community contributions?

Automating GitHub pull request triage involves checking community contributions against contribution guidelines, verifying PR formatting, and outputting actionable JSON recommendations for human review or closure.

What is community pull request readiness assessment?

Community pull request readiness assessment is the process of verifying PR title format, description completeness, test coverage, and CLA signature to ensure contributions meet criteria before human review.

How do I check if a community PR meets contribution guidelines before reviewing?

You can check contribution guidelines compliance by running an automated assessment script that inspects the PR via the GitHub API and returns a detailed JSON output with review results.

Do I need GitHub API access to assess pull request readiness?

Yes, you need GitHub API access to inspect pull request content and verify formatting, alongside having the gh command line tool and node installed to execute the readiness check scripts.

Can I automate Linear ticket management based on pull request triage results?

Yes, the pull request triage assessment provides recommendations for the appropriate Linear team to handle the review, or suggests closing the PR if it fails the predefined readiness criteria.

What limitations exist when automating PR formatting and content verification?

Automated PR formatting verification is limited to predefined criteria such as CLA signature, title format, description completeness, and test coverage, requiring human judgment for complex edge cases.