report-incident
Draft a terse GitHub issue for an incident in the Odoo dev suite (odoo-dev, odoo-orchestrator, dispatcher), with a current environment block and no private data. Files it only after you approve. Use when a tool or workflow failed.
- License 许可
- MIT
- 最近更新
- 2026-11-02
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- report-incident
- description
- Draft a terse GitHub issue for an incident in the Odoo dev suite (odoo-dev, odoo-orchestrator, dispatcher), with a current environment block and no private data. Files it only after you approve. Use when a tool or workflow failed.
- user-invocable
- true
03 SKILL.md 正文
Report an incident
Turn one incident into a GitHub issue in Crpaxton4/devcontainer-features.
The argument is an optional description. When it is present, use it as the first draft of the Summary.
1. Read the environment
Run each command on its own. If a command fails, write unknown for that field.
odoo-dev --version
claude --version
claude plugin list
claude plugin list shows the installed plugin names and versions. Use only odoo-dev and odoo-orchestrator.
The version of this plugin is also in ${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json.
If the incident is in the orchestrator or the dispatcher, also run these. ODOO_ORCHESTRATOR_CHECKOUT is the checkout that holds stack/compose.yaml.
git -C "$ODOO_ORCHESTRATOR_CHECKOUT" rev-parse --short HEAD
grep -m1 '^version' "$ODOO_ORCHESTRATOR_CHECKOUT/libraries/dispatcher/pyproject.toml"
Build this block. Use n/a for transport when no Odoo call was involved.
<environment>
<suite_version>odoo-dev <version> (host), main at <checkout commit or n/a></suite_version>
<python_version><version> (host)</python_version>
<claude_code_version><version></claude_code_version>
<plugins>odoo-dev <version>, odoo-orchestrator <version></plugins>
<transport><xmlrpc, jsonrpc or n/a></transport>
</environment>
For an orchestrator incident, add the dispatcher version to suite_version.
Get the Python version from python3 --version.
2. Draft the issue
Write the body with these sections, in this order. Keep it terse, for a reader who is an AI.
- Summary: 1-2 sentences.
- Symptoms: bullets of the errors or behavior you saw.
- Environment: the block from step 1, verbatim.
- Steps to reproduce: if they are known.
- Context: the relevant tool calls, responses or state from this session.
Write the title as <component>: <problem stated as a fact>.
3. CRITICAL: privacy rules
NEVER put any of these in the title or the body:
- The Odoo server URL.
- The database name.
- A username, password or API key.
- A customer name.
- Any other identifying detail.
Before you show the draft, read it again and remove or generalize each match.
4. Approve, then file
- Show the full draft (title and body) to the user.
- Wait. Do not file until the user approves. Apply the edits the user asks for and show it again.
- Write the body to a file with the Write tool, for example
/tmp/report-incident-body.md. - File the issue with the body file. Never pass the body inline: the shell truncates it at the first special character.
gh issue create -R Crpaxton4/devcontainer-features --title "<component>: <problem stated as a fact>" --body-file <path>
- Give the user the issue URL that
ghprints.
04 同仓库更多 Skills
principles
Engineering principles indexed as one-liners: safety and correctness, design and architecture, composition and interfaces, code structure, performance, visibility. Use when writing new code, reviewing a diff, or justifying a design choice.
odoo-upgrade
Plan and run code upgrades of custom Odoo modules between major versions (16.0→17.0→18.0→19.0). Use to migrate or port a module or addon, for breaking changes, a module inventory, or an upgrade estimate or plan.
odoo-upgrade-project
Human SOP for a whole Odoo upgrade project past the code port: staging database upgrade through upgrade.odoo.com, on-prem restore, cutover, go-live, support tickets and functional requirements. A planning reference.
odoo-test-run
Run an Odoo module's unit tests and HttpCase browser tours on a throwaway database and return machine-checkable evidence: tests executed, tours executed, failure lines. Use before a PR, after a fix, or when a green run never said how many tests ran.
odoo-task-env
Stand up the working environment for one Odoo task: find work that already exists, create or reuse an isolated git worktree on the task branch, bring a runnable stack up. Use at the START of implementing any task, and whenever one is picked back up.
odoo-session-db
Give one session its own throwaway test database name, so two sessions on one task in one project cannot land on the same database. Use before odoo-dev:odoo-test-run whenever more than one session can work in the same project, and when a test database vanished mid-run.