copilotkit-contribute

Guides forking, building, testing, and submitting pull requests to the CopilotKit monorepo.

Updated May 9, 2026
One-click install
npx skills add https://github.com/franciscogar94/CrisisOS --skill copilotkit-contribute-franciscogar94
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: copilotkit-contribute
Source: https://github.com/franciscogar94/CrisisOS/tree/main/.cursor/skills/copilotkit-contribute
Command: npx skills add https://github.com/franciscogar94/CrisisOS --skill copilotkit-contribute-franciscogar94

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Contributing to the CopilotKit open-source project requires navigating a pnpm/Nx monorepo with V1 and V2 package layers, enforced commit conventions, pre-commit hooks, and CI checks. This Skill consolidates the entire contribution workflow so developers avoid setup mistakes, failed CI runs, and rejected pull requests. ## Core Features & Use Cases - Monorepo Onboarding: Walks through forking, cloning, installing with pnpm v9, and bootstrapping the Nx build graph for all V1 and V2 packages. - Testing and Quality Gates: Explains Vitest configuration per package, coverage commands, lint/format checks, and the lefthook pre-commit pipeline. - PR Submission Standards: Details branch naming conventions, conventional commit format enforced by commitlint, CI preview packages via pkg-pr-new, and review expectations. - Use Case: A developer wants to add a new React hook to CopilotKit. The Skill directs them to create a feat/<ISSUE>-<name> branch, implement the feature in packages/v2/react, run nx run @copilotkit/react:test, and open a compliant PR against main. ## Quick Start Ask the assistant to walk you through setting up the CopilotKit repository locally and creating your first contribution branch.

Frequently Asked Questions about copilotkit-contribute

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

FAQPage Schema
How do I contribute to the CopilotKit open-source project?▼

Fork CopilotKit/CopilotKit on GitHub, clone your fork, run pnpm install and pnpm build, then create a branch named feat/<ISSUE>-<name> or fix/<ISSUE>-<name>. Develop with pnpm dev, test with Vitest, and open a PR against main.

How do I run tests in the CopilotKit monorepo?▼

Run pnpm run test for all packages, pnpm test:next for V2 only, or nx run @copilotkit/core:test for a single package. All packages use Vitest with globals enabled, and Nx caches results for unchanged code.

What is the difference between CopilotKit V1 and V2 packages?▼

V2 packages under packages/v2/ contain the real implementation, while V1 packages under packages/v1/ are public API wrappers around V2. New features always go in V2; V1 wrappers are added only when backward compatibility is needed.

Why does my CopilotKit commit get rejected by commitlint?▼

CopilotKit enforces conventional commits via a lefthook commit-msg hook. Messages must follow the format <type>(<scope>): <subject> with a valid type like feat, fix, docs, or test, a package-name scope, and a header under 120 characters.

What Node and pnpm versions does CopilotKit require?▼

CopilotKit requires Node.js 20.x or later and pnpm v9.x installed globally. Windows users must also enable Developer Mode for symlink support before running pnpm install.