How to Contribute

Thank you for your interest in contributing to pair! This guide covers everything you need to get started as a contributor.

Ways to contribute

There are several ways you can help improve pair:

Code: Fix bugs, add features, or improve existing functionality across the monorepo.
Documentation: Improve docs, fix typos, add examples, or write guides.
Skills: Create new Agent Skills that extend the AI-assisted development workflow.
Knowledge Base: Add or improve guidelines, templates, and how-to files.
Bug reports: Open an issue with reproduction steps.
Feature requests: Propose ideas via GitHub Discussions.

Clone the repo, install dependencies, run tests, and set up your local environment.

Understand the monorepo structure, key packages, and data flow.

Create new Agent Skills following the open standard.

Add Knowledge Base content, guidelines, templates, and how-tos.

How versioning, changesets, and automated releases work.

The Claude Code workflows and agent definitions that drive a batch of cards.

Support a new engine for unattended runs, or a new tracker through the host adapter interface.

Adding a tracker or code host is a contributor task too: Custom PM tool explains the one adapter file to write.

Fork and branch: Create a feature branch from main (e.g., feature/#123-description).
Make changes: Follow the development setup guide.
Run quality gate: Execute pnpm quality-gate before pushing.
Open a PR: Reference the related issue. Fill in the PR template.
Review: A maintainer will review your PR. Address any feedback.
Merge: Once approved, the PR is squash-merged into main.

Response time: We aim to review PRs within a few business days. Larger PRs may take longer.
Code quality: All contributions must pass the quality gate (linting, tests, type checking, formatting).
Be respectful: Treat all contributors with kindness and professionalism.
Small PRs: Prefer focused, small PRs over large ones. They are easier to review and merge.