Skip to content

Contributor Guide

Use a focused branch and conventional commits. Preserve compatibility and safety contracts; keep each pull request logically reviewable.

Quality gate

  1. Requirements and architecture impact documented.
  2. Existing managers reused; no unapproved core abstraction.
  3. Implementation and tests complete.
  4. Documentation, schemas, help, and examples updated.
  5. Security, performance, and compatibility assessed.
  6. Tests, audit, benchmark, and release verification pass.

Issues should include version, platform, redacted output, reproduction, expected behavior, and risk. Never attach credentials, prompts, responses, or private repository content. See CONTRIBUTING, Code review, and Issue triage.