?

Overview

The authoritative contributor guide lives at CONTRIBUTING.md in the source tree. This page is a docs-flavoured summary and the entry point when you're reading docs first, code second.

Ground rules

  • Commit style: Conventional Commits. feat(slack): …, fix(whatsapp): …, docs(concepts): …, refactor: ….
  • Every exported identifier has a godoc comment.
  • No interface{} / any in exported APIs without a written justification.
  • Every fact in the docs is code-truthful. Cite the file when possible.

Quality gates (run locally before opening a PR)

make check mirrors the CI matrix:

make check

Under the hood:

  • go vet ./...
  • golangci-lint run (18 linters)
  • go test -race -count=1 -covermode=atomic ./...
  • govulncheck ./...

Coverage floor is 75% total. Core packages sit 85–100% — keep them there.

Sending a patch

git clone git@github.com:<you>/rousseau-agent
cd rousseau-agent
git checkout -b feat/awesome
# … edit …
make check
git commit -m "feat(<area>): <what changed>"
git push -u origin feat/awesome
# open PR against sebastienrousseau/rousseau-agent:main

CI runs the same gates. Every commit must pass.

Contribution shapes

Reproduce first. Add a failing test. Fix. Verify the test passes. Send the PR with both the fix and the test in the same commit.

Filing a bug

Include, at minimum:

  • rousseau version output.
  • rousseau doctor output.
  • The exact command you ran.
  • The stderr you got.
  • What you expected.

Use the GitHub Issues bug-report template — it prompts for exactly this.

Related pages

Type to search 150+ pages. Ranking: BM25 with title/description boost.