copilotkit-contribute
Use when contributing to the CopilotKit open-source project — forking, cloning, setting up the monorepo, creating branches, running tests, and submitting pull requests against CopilotKit/CopilotKit.
What this skill does
# Contributing to CopilotKit > **Important:** CopilotKit's internal v2 packages use the `@copilotkit/*` namespace. The public API that users install is `@copilotkit/*`. When contributing, you work with `@copilotkit/*` source but users never see that namespace. ## Live Documentation (MCP) This plugin includes an MCP server (`copilotkit-docs`) that provides `search-docs` and `search-code` tools for querying live CopilotKit documentation and source code. - **Claude Code:** Auto-configured by the plugin's `.mcp.json` -- no setup needed. - **Codex:** Requires manual configuration. See the [copilotkit-debug skill](../copilotkit-debug/SKILL.md#mcp-setup) for setup instructions. ## Workflow 1. **Fork and clone** the CopilotKit/CopilotKit repository. 2. **Install dependencies** with `pnpm install` (requires pnpm v9.x and Node 20+). 3. **Build once** with `pnpm build` to bootstrap all packages. 4. **Create a branch** using the naming convention: `feat/<ISSUE>-<name>`, `fix/<ISSUE>-<name>`, or `docs/<ISSUE>-<name>`. 5. **Develop** with `pnpm dev` (watches all packages) or target a specific package with `nx run @copilotkit/<pkg>:dev`. 6. **Write and run tests** with `nx run @copilotkit/<pkg>:test`. All v2 packages use Vitest. 7. **Lint and format** with `pnpm run lint --fix && pnpm run format`. 8. **Commit** using conventional commit format: `<type>(<scope>): <subject>` (enforced by commitlint). 9. **Push and open a PR** against the `main` branch. CI builds all packages and publishes preview packages via pkg-pr-new. ## Before Opening a PR - Reach out to the maintainers first for any significant work (file an issue or ask on Discord). - Run `pnpm run test` to verify all tests pass. - Run `pnpm run build` to verify the full build succeeds. - Run `pnpm run check-prettier` to verify formatting. - Ensure commit messages follow the `<type>(<scope>): <subject>` format. ## Quick Reference | Task | Command | |---|---| | Install dependencies | `pnpm install` | | Build all packages | `pnpm build` | | Dev mode (all) | `pnpm dev` | | Dev mode (v2 only) | `pnpm dev:next` | | Run all tests | `pnpm run test` | | Run v2 tests only | `pnpm test:next` | | Run single package tests | `nx run @copilotkit/core:test` | | Test with coverage | `pnpm run test:coverage` | | Lint | `pnpm run lint` | | Format | `pnpm run format` | | Check formatting | `pnpm run check-prettier` | | Type check | `pnpm run check-types` | | Package quality checks | `pnpm run check:packages` | | Dependency graph | `pnpm run graph` | ## Key Architecture Points - V2 (`@copilotkit/*`) is the real implementation. V1 (`@copilotkit/*`) wraps V2. - New features always go in V2 packages under `packages/v2/`. - Communication between frontend and runtime uses the AG-UI protocol (SSE-based events). - The monorepo uses Nx for task orchestration and pnpm workspaces. ## Reference Documents - [Contribution Guide](references/contribution-guide.md) — full onboarding walkthrough - [Repo Structure](references/repo-structure.md) — package layout and architecture - [Testing Guide](references/testing-guide.md) — Vitest setup, running tests, coverage - [PR Guidelines](references/pr-guidelines.md) — CI checks, review process, expectations
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.