Skip to content

How to contribute

Belico Ecosystem is open source MIT and the LATAM community can adopt, contribute, and improve it. This guide summarizes the contribution flow.

Canonical source

The single source of truth for contributing is CONTRIBUTING.md at the repo root. This page is a task-oriented summary — on any difference, the root file wins.

What you can contribute

  • Code: harnesses, sub-agents, tools, fixes.
  • Domains: new scientific backends (config/domains/ + domains/ + skill).
  • Translations: the EN pages marked 🚧 translation pending.
  • Documentation: improvements to tutorials, how-tos, and explanations.
  • Reports: bugs and proposals via GitHub Issues.

Workflow (SDD)

Substantial changes follow the Spec-Driven Development pattern:

EXPLORE → PROPOSE → [SPEC ∥ DESIGN] → TASKS → IMPLEMENT → VERIFY → ARCHIVE

Each change lives in openspec/changes/<name>/ with proposal.md, design.md, tasks.md, and spec deltas. See SDD workflow.

Commit conventions

Conventional commits format:

feat(scope): short description
fix(scope): short description
docs(scope): short description
test(scope): short description

No AI attribution

Do not add Co-Authored-By or AI attribution to commits. Conventional commits only.

Before opening a PR

  1. Run the tests: pytest tests/ (after pip install -r requirements-dev.txt).
  2. Run the linter: ruff check . + ruff format --check . (see Ruff migration).
  3. Verify the docs build passes: mkdocs build --strict.
  4. If you touched the draft/pipeline/config, flag that the Verifier must validate.

Code review (GGA)

The GGA pre-commit hook enforces the 11 rules of AGENTS.md on any commit touching .py, .h, .sh. Configurable via .gga (PROVIDER="claude" | "gemini" | "openai").

See also