copilotkit-contribute

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

Updated May 9, 2026

Search Tags:#vitest #contribution #pull request #pnpm #monorepo #copilotkit #open-source

Ready to run

npx skills add https://github.com/SebastienGt/LivingMargin-Google-Deepmind-Hackathon --skill copilotkit-contribute-sebastiengt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: copilotkit-contribute
Source: https://github.com/SebastienGt/LivingMargin-Google-Deepmind-Hackathon/tree/main/.cursor/skills/copilotkit-contribute
Command: npx skills add https://github.com/SebastienGt/LivingMargin-Google-Deepmind-Hackathon --skill copilotkit-contribute-sebastiengt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Contributing to the CopilotKit open-source monorepo requires knowing its pnpm/Nx workspace setup, V1-wraps-V2 package architecture, branch naming rules, commitlint-enforced commit format, and CI expectations. This Skill consolidates that contributor workflow into one guided reference. ## Core Features & Use Cases - End-to-End Contribution Workflow: Walks through forking, cloning, installing with pnpm v9, bootstrapping with Nx builds, and creating correctly named branches (feat/fix/docs). - Testing and Quality Commands: Documents Vitest test commands per package, coverage runs, lint/format checks, and pre-commit lefthook hooks. - PR and CI Guidance: Explains conventional commit format, PR checklist, CI pipeline behavior, and pkg-pr-new preview publishing. - Use Case: A developer wants to add a new hook to @copilotkit/react. The Skill directs them to the v2 package, the correct nx test command, the commit message format, and the PR submission steps. ## Quick Start Help me set up the CopilotKit repository locally and open a pull request for a bug fix in the runtime package.

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 and clone CopilotKit/CopilotKit, install dependencies with pnpm install, run pnpm build to bootstrap packages, then create a branch named feat/<ISSUE>-<name> or fix/<ISSUE>-<name>. After developing and testing, push 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, and tests depend on upstream packages being built first.

What commit message format does CopilotKit require?▼

CopilotKit enforces conventional commits via commitlint: <type>(<scope>): <subject>, with a 120-character header limit. Valid types include feat, fix, docs, style, refactor, perf, test, and chore, with the scope being the package name.

Where should new features go in the CopilotKit repo, v1 or v2?▼

New features always go in v2 packages under packages/v2/, since v2 is the real implementation. V1 packages wrap v2, so only add a v1 wrapper if backward compatibility is needed.

Why do CopilotKit pre-commit hooks fail on my commit?▼

Lefthook runs check-binaries, sync-lockfile, lint-fix, and test-and-check-packages in parallel on every commit. Failures usually come from lint errors, failing tests, oversized files, or an out-of-date lockfile; fix the issue rather than using --no-verify.