skillboardUpdated every 6 hours
skillboardChecks 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.
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 ( / ) → 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 ( ) → action path B — triage to team . 4. One or more checks fail → action path A (if title is minor…
Full body not shown for this license – view the source on GitHub →Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/community-pr-readiness-check · pinned to the source commit
git clone https://github.com/n8n-io/n8n.git
cd n8n
git checkout b4d91bfe8a293106815b308a841e210562002735
mkdir -p ".claude/skills/community-pr-readiness-check"
cp -r ".agents/skills/community-pr-readiness-check" ".claude/skills/community-pr-readiness-check"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit b4d91bfe8a29. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
References parent-directory traversal, which can escape a target directory.
Evidence: ../· fingerprint fa08499e14d0113b