multi-version-compliance

Applies and reviews multi-version support compliance for first-party Nx plugins.

29.3k|3.0k|Updated Aug 11, 2017
One-click install
npx skills add https://github.com/nrwl/nx --skill multi-version-compliance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-version-compliance
Source: https://github.com/nrwl/nx/tree/main/.claude/skills/multi-version-compliance
Command: npx skills add https://github.com/nrwl/nx --skill multi-version-compliance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

First-party Nx plugins must keep working across their declared third-party support windows (Angular, Cypress, Playwright, Jest, Vitest, ESLint, etc.) so that nx migrate --first-party-only is safe. This Skill drives the audit, fix, and review of that compliance work, using Linear tasks (NXC-XXXX) as the source of truth for scope.

Core Features & Use Cases

  • Fix mode: Fetches a Linear task, surfaces findings and "Needs human decision" items, then implements the canonical shape (floor asserts, peer dep alignment, requires migration gates, executor feature gating) after user approval.
  • Review mode: Compares a compliance PR diff against its Linear task and the canonical patterns, producing blocker/non-blocker findings anchored at file:line with a structured verdict block.
  • No-task discovery: Runs the A–F rubric against a plugin's code and produces a filing-ready findings doc when no Linear task exists.
  • Use Case: Run it with NXC-4384 to implement multi-version compliance for @nx/cypress, or with review #35670 to audit an open compliance PR.

Quick Start

Ask the assistant to run multi-version compliance for a specific Linear task such as NXC-4384 or to review a compliance PR by number.

Frequently Asked Questions about multi-version-compliance

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

FAQPage Schema
How do I fix multi-version compliance for an Nx plugin?

Invoke the skill with a Linear task ID (e.g., NXC-4384) or a plugin name like @nx/cypress. It fetches the task findings, surfaces open decisions, and implements the canonical patterns after your explicit approval.

How do I review an Nx multi-version compliance PR?

Run the skill with `review #<PR-number>`. It fetches the PR diff, derives the Linear task from the branch name, and checks the code against canonical-shape and anti-pattern references, outputting blockers and non-blockers anchored at file:line.

What happens if no Linear task exists for a plugin?

The skill runs discovery against the A–F rubric, derives the support window from upstream LTS policy, and writes a findings doc to tmp/ shaped like a Linear task body so you can file it in milestone NXC-4072 before any edits.

Does the skill make code changes without approval?

No. Phases 1–2 are read-only: discovery, finding classification, and decision surfacing happen on the current branch with no edits or branch creation. Implementation only starts in Phase 3 after explicit user approval.

What tools does the multi-version compliance skill require?

It uses Bash, Read, Edit, Write, Glob, Grep, and the GitHub CLI for PR inspection. Linear-driven mode requires the Linear MCP server (mcp__linear-server__get_issue); without it, the skill falls back to no-task discovery.