oca-module-governance
Verify OCA module adoption quality gates — maturity level, 19.0 CI status, test install, no EE deps, manifest registration
来源信息
- 仓库
- Insightpulseai/odoo
- 最近来源活动
- 2026年4月10日 07:16
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 6
- 分支
- 2
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- OCA Module Governance
- description
- Verify OCA module adoption quality gates — maturity level, 19.0 CI status, test install, no EE deps, manifest registration
# OCA Module Governance Skill
## When to use
When adding, updating, or reviewing any OCA module in `addons/oca/`.
## Quality gates checklist
Before adding any OCA module to the install baseline:
1. Verify 19.0 branch exists and CI is green on the OCA repo
2. Check `development_status` >= `Stable` in `__manifest__.py`
3. Test install in disposable DB: `test_<module>`
4. Verify no conflicts with existing `ipai_*` modules
5. Document in `config/addons.manifest.yaml` with repo, tier, and provenance
6. Confirm no Enterprise dependencies or odoo.com IAP calls
## Porting workflow (18.0 → 19.0)
```bash
oca-port origin/18.0 origin/19.0 <module> --verbose --dry-run
odoo-bin upgrade_code --addons-path <path>
odoo-bin -d test_<module> -i <module> --stop-after-init --test-enable
```
Never port without running `upgrade_code`. Odoo 18 changed `tree` to `list` globally.
## Hard rules
- Never modify OCA source — create `ipai_*` override module
- Never copy OCA files into `addons/ipai/` — use `_inherit`
- Stable modules cannot depend on Beta modules
- Never skip test install
- OCA path is always `addons/oca/` (slash, never hyphen)
在 GitHub 查看