CoProgrammer is itself developed with the collaboration style it proposes.
- Keep protocol changes, tool changes, dependency upgrades, and formatting-only changes in separate PRs.
- Any change to
protocols/,schemas/, or.github/must explain the compatibility impact. - Any CLI behavior change must include or update tests.
- Large AI-generated branches should include a branch digest before review.
- Avoid broad rewrites unless the PR is explicitly about architecture cleanup.
Every non-trivial PR should include:
- task intent;
- files touched;
- shared contracts changed;
- validation run;
- known risks;
- integration notes.
Use .github/PULL_REQUEST_TEMPLATE.md and templates/branch-digest.md.
python -m pip install -e .
python -m unittest discover -s tests
python -m coprogrammer config validate
python -m coprogrammer manifest validate templates/change-manifest.json