odoo-wt

Files (1)

• SKILL.md

SKILL.md (first lines)

# odoo-wt

CLI: `odoo-wt` (install from https://github.com/erpipe-org/odoo-worktree).
Config: `odoo-wt.toml` at the **Odoo addons repo** root. State: `~/.odoo-wt/`.

## When to use

- Agent session = git worktree and needs to run/upgrade/test Odoo without touching the canonical stack.
- User asks for a separate Odoo + DB for a branch.

## When not to

- Read-only code edits / unit tests that do not need a live Odoo.
- Canonical UI at the reserved host/ports in `[guard]`.

## Rules

1. Do **not** `docker compose up` the project's canonical compose file from a worktree.
2. Do **not** `TEMPLATE` / `odoo db duplicate` the live canonical database.
3. Do **not** bind reserved ports or compose project names from `odoo-wt.toml` `[guard]`.
4. `odoo-wt up` only inside a **linked worktree**. Primary checkout requires `--on-primary`.
5. When the session ends: `odoo-wt down`. If the agent died: `odoo-wt gc`. If the git worktree folder is gone, `up`/`gc` must purge that runtime. Hourly timer is optional: `odoo-wt timer install`.
6. If `[seed].require_filestore`: never SQL-only seed; never bind-mount the live filestore.
7. One host port per worktree until `odoo-wt down`. Lookup: `odoo-wt ports` (writes `~/.odoo-wt/ports.txt` — generated, do not edit).

## Related skills

- Start stack → `odoo-wt-up`
- Seed dump → `odoo-wt-seed`
- Teardown → `odoo-wt-cleanup`

From erpipe-org/odoo-worktree, MIT.

More from erpipe-org/odoo-worktree