-
Notifications
You must be signed in to change notification settings - Fork 0
Contributing
hypersdk edited this page Aug 7, 2026
·
1 revision
Dev setup and conventions for extending the agent. Deep: CONTRIBUTING.md.
cp .env.example .env
make install
make lint # ruff + tsc
zyvor-qa test # smoke
zyvor-qa run --source local| Tree | Role |
|---|---|
orchestrator/graph.py |
Node wiring + routing |
orchestrator/nodes/ |
Thin PipelineState → PipelineState wrappers |
agents/* |
Real logic per capability |
agents/common/ |
Pydantic models + LLM factory |
tests/manual/ |
Hand-owned — never overwritten by generate |
tests/generated/ |
Disposable |
prompts/ |
LLM system prompts |
templates/ |
Jinja fallback test + HTML report |
See Project Structure · Architecture.
-
Python: Ruff, py310+,
from __future__ import annotations; feature flags read at call time from env -
LLM-with-fallback: every LLM stage must degrade without a key (except
zyvor-qa create) -
Quality gate: generated TS must pass
agents/generator/quality.pybefore write -
Don’t pass ad-hoc dicts through
PipelineState— use Pydantic models inagents/common/models.py
- Implement logic under
agents/<capability>/ - Add
orchestrator/nodes/<name>.pywrapper - Wire in
graph.py(+ routing if needed) - Document flag in
docs/configuration.md/.env.example - Prefer a tutorial or wiki note for operators
- Include tests or a smoke path when possible
- No secrets in commits
- Match existing style; run
make lint
Related: Tutorials Index · Releases
Start: Home · Getting Started · Tutorials · Workflows · Admin · Dashboard
Tutorials: Spec→Test · NL · GitHub · Coverage · Visual · Notify · External CI · Agent CI · zyvor.dev · Specs
Build: Architecture · Config · Authoring · Structure · Multi-browser · Rust
Actions: Mission Control · Journeys · API/Auth · Probes · Schedules · Ask Zyvor · Autofix
Ship: API · Webhooks · Security · CI/CD · Deploy · Releases · Enterprise
More: Troubleshoot · FAQ · Glossary · Contributing · Demos · Docs
Guides