copilotkit-contribute

Guide contributions to the CopilotKit repository with pnpm and Nx workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the friction of contributing to the CopilotKit open-source repository by giving you a clear workflow for setup, development, testing, formatting, and pull request submission.

Core Features & Use Cases

  • Repository Onboarding: Fork, clone, and configure the monorepo correctly with the required Node.js and pnpm versions.
  • Development Workflow: Work confidently across the Nx-managed packages, including V1 wrappers and V2 implementation packages.
  • Quality Gates: Run tests, linting, formatting, and package checks before submitting changes.
  • Pull Request Preparation: Follow branch naming, commit message, and review expectations that match the project’s conventions.
  • Use Case: A contributor can pick a package, make a change, verify it locally, and open a clean PR that is ready for maintainer review.

Quick Start

Use this skill to guide me through contributing to CopilotKit, from local setup and branch creation to testing, formatting, and opening a pull request.

Frequently Asked Questions about copilotkit-contribute

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

FAQPage Schema
How do I set up the CopilotKit monorepo for local development?

Setting up the CopilotKit monorepo requires forking and cloning the repository, then installing dependencies using pnpm 9+ with Node.js 20+. This configures the Nx-managed workspace, enabling development across V1 and V2 implementation packages.

What's the best way to run tests and linting in a pnpm Nx monorepo before a pull request?

Running Nx and Vitest workflows is the best way to verify code before a CopilotKit pull request. This executes required tests, linting, formatting, and package checks to ensure changes meet project quality gates.

Do I need to use conventional commits for CopilotKit open-source contributions?

Yes, CopilotKit open-source contributions require conventional commits. Following branch naming and commit message conventions ensures your pull request matches maintainer expectations and is ready for review against the main branch.

How does the v2-first architecture affect CopilotKit package development?

The v2-first architecture directs development to focus primarily on V2 implementation packages while maintaining V1 wrappers. This approach, integrated with the AG-UI protocol, structures how features are built and tested within the Nx workspace.

Can I use pnpm 8 to contribute to the CopilotKit repository?

No, you cannot use pnpm 8 to contribute to the CopilotKit repository. The project explicitly requires pnpm 9+ and Node.js 20+ to ensure correct dependency resolution and successful Nx monorepo workflow execution.