[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75TPJCBY374BJMX3N1XT8R8":3,"skill-same:01M75TPJCBY374BJMX3N1XT8R8":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M75TPJCBY374BJMX3N1XT8R8","odoo-repo-map",null,"Resolve an Odoo project to its git repo, base branch, Odoo series, and environment chain (dev → staging → production). Use before cutting a worktree, opening a PR, or planning a release, and when a project is added or renamed.","Crpaxton4\u002Fdevcontainer-features","Crpaxton4","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10190720?v=4","01M75TNGAF4N2K56AS0WDN38AM","Chris Paxton","01M75TNGB1E99BTJEGPXPQDRAB",0,"MIT","https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-dev\u002Fskills\u002Fodoo-repo-map\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: odoo-repo-map\ndescription: \"Resolve an Odoo project to its git repo, base branch, Odoo series, and environment chain (dev → staging → production). Use before cutting a worktree, opening a PR, or planning a release, and when a project is added or renamed.\"\nuser-invocable: false\n---\n# Odoo Repo Map\n\nOne answer to \"this Odoo project: which repo, which branch, which series, what comes after\nthis branch?\". Nothing is inferred from a checkout: the GitHub default branch is not the\nbase, the folder name is not the project name, and the chain lives nowhere in git.\n\nThe scripts here are thin wrappers over `odoo-dev repo-map`. The CLI validates, backs up\nand writes the map.\n\n## The data\n\n`${ODOO_DEV_HOME:-$HOME\u002F.config\u002Fodoo-dev}\u002Frepo-map.json`. The devcontainer sets\n`ODOO_DEV_HOME`. The first write creates the file. A map that does not parse exits 4 naming\nthe complaint. It is never reseeded.\n\nThe file holds `defaults` and one entry per exact Odoo `project.project` name:\n\n| Key | Meaning |\n|-----|---------|\n| `repo` | A folder name under the repos tree, or an absolute path to the checkout |\n| `odoo_version` | The series this project runs, e.g. `18.0` |\n| `aliases` | Other `project.project` names that resolve to this entry. Never an entry name. Each alias appears once in the map |\n| `branch_flow` | Ordered environment chain, e.g. `[\"task\",\"UAT\",\"main\"]`. Empty means `defaults.branch_flow` |\n| `upgrade_branch` | Object of target series to branch, e.g. `{\"19.0\":\"19-upgrade\"}`. A series with no key uses the last element of the flow |\n| `release_assignee` | GitHub login a release PR is assigned to. Empty means the default |\n| `release_reviewer` | GitHub login the release PR requests review from, or `none`. Empty means the default |\n\n`defaults` holds `branch_flow` (initially `[\"task\",\"E2E\",\"UAT\",\"main\"]`), `release_assignee`\nand `release_reviewer`. Change them with `odoo-dev repo-map defaults`.\n\nFacts:\n\n- `task` is only ever element 0 of `branch_flow`. It stands for the per-task branch.\n- The base branch of a task is the first element after `task` that exists on `origin`.\n  A missing branch is skipped.\n- The last element of `branch_flow` is production.\n- The keys of older maps that no longer exist are dropped by the reader. The default branch\n  is derived from the flow, never stored.\n- A `.odoo-repos-dir` marker file declares a repos tree that holds one clone. It outranks\n  the two-git-subdirectories sweep. `REPOS_DIR` is the per-shell equivalent.\n\n## Scripts\n\nWrite every path in full.\n\n| Script and arguments | Prints | Exit |\n|---|---|---|\n| `repos-dir.sh [--raw]` | `{\"repos_dir\"}` from `$REPOS_DIR`, then the marker, then the sweep | 0 · 1 no tree (an absolute `repo` skips it) |\n| `repo-map.sh get \"\u003Cname>\" \\| list \\| validate \\| remove \"\u003Cname>\"` [`--json`] | the CLI output of the same verb | 0 · 2 usage · 3 unmapped · 4 map invalid |\n| `repo-map.sh add \"\u003Cname>\" \u003Crepo> --odoo-version V [--aliases A,B] [--branch-flow task,UAT,main] [--upgrade-branch 19.0=BRANCH]... [--release-assignee X] [--release-reviewer Y]` | `odoo-dev repo-map set` | 0 · 2 usage or already mapped · 4 invalid |\n| `repo-map.sh set \"\u003Cname>\" [--repo R] [--odoo-version V] [same fields]` | `odoo-dev repo-map set`, keeping every field not named | 0 · 2 · 3 · 4 |\n| `repo-map.sh set-flow \"\u003Cname>\" \"task,UAT,main\"` | `set` with `--branch-flow`. `--flow-confirmed` is accepted and ignored | 0 · 2 · 3 · 4 |\n| `repo-map.sh set-release-owners \"\u003Cname>\" \u003Cassignee> \u003Creviewer\\|none>` | `set` with the two logins | 0 · 2 · 3 · 4 |\n| `project-resolve.sh \"\u003Cproject\\|alias\\|repo>\" [--next-after \u003Cbranch>] [--series NN.0]` | `{\"project\",\"repo\",\"repo_root\",\"origin\",\"odoo_version\",\"branch_flow\",\"base_branch\",\"upgrade_branch\",\"next_env\",\"at_production\",\"release_assignee\",\"release_reviewer\"}` | 0 · 2 usage or a `--series` that is not `NN.0` · 3 unmapped · 4 `--next-after` names a branch not in the flow · 6 ambiguous |\n| `project-bootstrap.sh \"\u003Ccheckout path>\" [--project NAME]` | the entry it wrote, as JSON | 0 · 2 not a git checkout or no series found · 3 already mapped (entry printed) |\n\nJSON helper: `plugins\u002Fodoo-dev\u002Fscripts\u002Fjson-get.sh '\u003Cexpression on d>'` reads JSON on stdin.\nUse it to read one field from any output above.\n\n### Resolve\n\n```bash\n\u003Cbase directory>\u002Fscripts\u002Fproject-resolve.sh \"B&K Logistics Support\"\n\u003Cbase directory>\u002Fscripts\u002Fproject-resolve.sh \"B&K Logistics Support\" --next-after task   # -> next_env: \"UAT\"\n```\n\n`--next-after` takes an element of the chain. The first hop is `--next-after task`. `repo_root`\nand `base_branch` are `null` when no checkout is on this machine. `branch_flow` is the\neffective flow (the entry's own, else the defaults). The two `release_*` fields fall back to the\ndefaults and are `null` when neither is set.\n\n- `exit 3` — unmapped → run `project-bootstrap.sh \"\u003Ccheckout>\"`, then resolve again by\n  the project name it printed; still 3 → stop, report the path and the output.\n- `exit 4` — the branch is not in the flow → stop; report the flow.\n- `exit 6` — ambiguous: one repo folder maps to several projects → stop; list the\n  candidate project names; never pick one.\n- `exit 2` — usage → fix the call.\n\n### Bootstrap an unmapped checkout\n\n```bash\n\u003Cbase directory>\u002Fscripts\u002Fproject-bootstrap.sh \u002Fmnt\u002Fextra-addons --project \"ACME Support\"\n```\n\nIt records `repo` and `odoo_version` from the checkout. The flow is left empty, so the entry\nuses the defaults. `repo` is the folder name when the repos tree holds it, else the absolute\npath.\n\n- `exit 3` — this checkout is already mapped by the printed entry → resolve by that\n  project name; never add a second entry.\n\n### Edit\n\n```bash\n\u003Cbase directory>\u002Fscripts\u002Frepo-map.sh add \"New Client - Phase 1\" newclient \\\n  --odoo-version 18.0 --branch-flow \"task,UAT,main\" \\\n  --release-assignee alice --release-reviewer bob\n\u003Cbase directory>\u002Fscripts\u002Frepo-map.sh set \"New Client - Phase 1\" --odoo-version 19.0\n\u003Cbase directory>\u002Fscripts\u002Frepo-map.sh set \"New Client - Phase 1\" --aliases \"New Client - Support,New Client - Care\"   # \"\" removes them\n\u003Cbase directory>\u002Fscripts\u002Frepo-map.sh set \"New Client - Phase 1\" --upgrade-branch 19.0=19-upgrade   # repeatable; 19.0= removes that series\n\u003Cbase directory>\u002Fscripts\u002Frepo-map.sh set-flow \"New Client - Phase 1\" \"task,UAT,main\"\n\u003Cbase directory>\u002Fscripts\u002Frepo-map.sh set-release-owners \"New Client - Phase 1\" alice bob\n\u003Cbase directory>\u002Fscripts\u002Frepo-map.sh add \"Client - Support\" \u002Fmnt\u002Fextra-addons --odoo-version 18.0\n```\n\n- `add` only creates and refuses a duplicate. It does not check that the repo folder exists.\n  `set` keeps the fields you do not name.\n- Never `remove` then re-`add` to change a field.\n- One entry per customer repo. A second Odoo project on the same repo and chain is an\n  alias, not an entry. `set`, `set-flow`, `set-release-owners` and `remove` take the\n  entry name or, for `set*`, an alias.\n- The CLI writes atomically and keeps one `.bak`.\n\n## Rules\n\n- An unknown project is a stop, never a guess. Bootstrap first, then stop on what remains.\n- An entry is added only with explicit user confirmation of repo, series and chain.\n- One repo with several projects is normal. Those entries can disagree on\n  `odoo_version` and `branch_flow`. Name the project.\n- Never hand-edit the map file.\n- `base_branch` is what a task PR targets. It is often not the GitHub default branch.\n","# Odoo Repo Map\n\nOne answer to \"this Odoo project: which repo, which branch, which series, what comes after\nthis branch?\". Nothing is inferred from a checkout: the GitHub default branch is not the\nbase, the folder name is not the project name, and the chain lives nowhere in git.\n\nThe scripts here are thin wrappers over `odoo-dev repo-map`. The CLI validates, backs up\nand writes the map.\n\n## The data\n\n`${ODOO_DEV_HOME:-$HOME\u002F.config\u002Fodoo-dev}\u002Frepo-map.json`. The devcontainer sets\n`ODOO_DEV_HOME`. The first write creates the file. A map that does not parse exits 4 naming\nthe complaint. It is never reseeded.\n\nThe file holds `defaults` and one entry per exact Odoo `project.project` name:\n\n| Key | Meaning |\n|-----|---------|\n| `repo` | A folder name under the repos tree, or an absolute path to the checkout |\n| `odoo_version` | The series this project runs, e.g. `18.0` |\n| `aliases` | Other `project.project` names that resolve to this entry. Never an entry name. Each alias appears once in the map |\n| `branch_flow` | Ordered environment chain, e.g. `[\"task\",\"UAT\",\"main\"]`. Empty means `defaults.branch_flow` |\n| `upgrade_branch` | Object of target series to branch, e.g. `{\"19.0\":\"19-upgrade\"}`. A series with no key uses the last element of the flow |\n| `release_assignee` | GitHub login a release PR is assigned to. Empty means the default |\n| `release_reviewer` | GitHub login the release PR requests review from, or `none`. Empty means the default |\n\n`defaults` holds `branch_flow` (initially `[\"task\",\"E2E\",\"UAT\",\"main\"]`), `release_assignee`\nand `release_reviewer`. Change them with `odoo-dev repo-map defaults`.\n\nFacts:\n\n- `task` is only ever element 0 of `branch_flow`. It stands for the per-task branch.\n- The base branch of a task is the first element after `task` that exists on `origin`.\n  A missing branch is skipped.\n- The last element of `branch_flow` is production.\n- The keys of older maps that no longer exist are dropped by the reader. The default branch\n  is derived from the flow, never stored.\n- A `.odoo-repos-dir` marker file declares a repos tree that holds one clone. It outranks\n  the two-git-subdirectories sweep. `REPOS_DIR` is the per-shell equivalent.\n\n## Scripts\n\nWrite every path in full.\n\n| Script and arguments | Prints | Exit |\n|---|---|---|\n| `repos-dir.sh [--raw]` | `{\"repos_dir\"}` from `$REPOS_DIR`, then the marker, then the sweep | 0 · 1 no tree (an absolute `repo` skips it) |\n| `repo-map.sh get \"\u003Cname>\" \\| list \\| validate \\| remove \"\u003Cname>\"` [`--json`] | the CLI output of the same verb | 0 · 2 usage · 3 unmapped · 4 map invalid |\n| `repo-map.sh add \"\u003Cname>\" \u003Crepo> --odoo-version V [--aliases A,B] [--branch-flow task,UAT,main] [--upgrade-branch 19.0=BRANCH]... [--release-assignee X] [--release-reviewer Y]` | `odoo-dev repo-map set` | 0 · 2 usage or already mapped · 4 invalid |\n| `repo-map.sh set \"\u003Cname>\" [--repo R] [--odoo-version V] [same fields]` | `odoo-dev repo-map set`, keeping every field not named | 0 · 2 · 3 · 4 |\n| `repo-map.sh set-flow \"\u003Cname>\" \"task,UAT,main\"` | `set` with `--branch-flow`. `--flow-confirmed` is accepted and ignored | 0 · 2 · 3 · 4 |\n| `repo-map.sh set-release-owners \"\u003Cname>\" \u003Cassignee> \u003Creviewer\\|none>` | `set` with the two logins | 0 · 2 · 3 · 4 |\n| `project-resolve.sh \"\u003Cproject\\|alias\\|repo>\" [--next-after \u003Cbranch>] [--series NN.0]` | `{\"project\",\"repo\",\"repo_root\",\"origin\",\"odoo_version\",\"branch_flow\",\"base_branch\",\"upgrade_branch\",\"next_env\",\"at_production\",\"release_assignee\",\"release_reviewer\"}` | 0 · 2 usage or a `--series` that is not `NN.0` · 3 unmapped · 4 `--next-after` names a branch not in the flow · 6 ambiguous |\n| `project-bootstrap.sh \"\u003Ccheckout path>\" [--project NAME]` | the entry it wrote, as JSON | 0 · 2 not a git checkout or no series found · 3 already mapped (entry printed) |\n\nJSON helper: `plugins\u002Fodoo-dev\u002Fscripts\u002Fjson-get.sh '\u003Cexpression on d>'` reads JSON on stdin.\nUse it to read one field from any output above.\n\n### Resolve\n\n```bash\n\u003Cbase directory>\u002Fscripts\u002Fproject-resolve.sh \"B&K Logistics Support\"\n\u003Cbase directory>\u002Fscripts\u002Fproject-resolve.sh \"B&K Logistics Support\" --next-after task   # -> next_env: \"UAT\"\n```\n\n`--next-after` takes an element of the chain. The first hop is `--next-after task`. `repo_root`\nand `base_branch` are `null` when no checkout is on this machine. `branch_flow` is the\neffective flow (the entry's own, else the defaults). The two `release_*` fields fall back to the\ndefaults and are `null` when neither is set.\n\n- `exit 3` — unmapped → run `project-bootstrap.sh \"\u003Ccheckout>\"`, then resolve again by\n  the project name it printed; still 3 → stop, report the path and the output.\n- `exit 4` — the branch is not in the flow → stop; report the flow.\n- `exit 6` — ambiguous: one repo folder maps to several projects → stop; list the\n  candidate project names; never pick one.\n- `exit 2` — usage → fix the call.\n\n### Bootstrap an unmapped checkout\n\n```bash\n\u003Cbase directory>\u002Fscripts\u002Fproject-bootstrap.sh \u002Fmnt\u002Fextra-addons --project \"ACME Support\"\n```\n\nIt records `repo` and `odoo_version` from the checkout. The flow is left empty, so the entry\nuses the defaults. `repo` is the folder name when the repos tree holds it, else the absolute\npath.\n\n- `exit 3` — this checkout is already mapped by the printed entry → resolve by that\n  project name; never add a second entry.\n\n### Edit\n\n```bash\n\u003Cbase directory>\u002Fscripts\u002Frepo-map.sh add \"New Client - Phase 1\" newclient \\\n  --odoo-version 18.0 --branch-flow \"task,UAT,main\" \\\n  --release-assignee alice --release-reviewer bob\n\u003Cbase directory>\u002Fscripts\u002Frepo-map.sh set \"New Client - Phase 1\" --odoo-version 19.0\n\u003Cbase directory>\u002Fscripts\u002Frepo-map.sh set \"New Client - Phase 1\" --aliases \"New Client - Support,New Client - Care\"   # \"\" removes them\n\u003Cbase directory>\u002Fscripts\u002Frepo-map.sh set \"New Client - Phase 1\" --upgrade-branch 19.0=19-upgrade   # repeatable; 19.0= removes that series\n\u003Cbase directory>\u002Fscripts\u002Frepo-map.sh set-flow \"New Client - Phase 1\" \"task,UAT,main\"\n\u003Cbase directory>\u002Fscripts\u002Frepo-map.sh set-release-owners \"New Client - Phase 1\" alice bob\n\u003Cbase directory>\u002Fscripts\u002Frepo-map.sh add \"Client - Support\" \u002Fmnt\u002Fextra-addons --odoo-version 18.0\n```\n\n- `add` only creates and refuses a duplicate. It does not check that the repo folder exists.\n  `set` keeps the fields you do not name.\n- Never `remove` then re-`add` to change a field.\n- One entry per customer repo. A second Odoo project on the same repo and chain is an\n  alias, not an entry. `set`, `set-flow`, `set-release-owners` and `remove` take the\n  entry name or, for `set*`, an alias.\n- The CLI writes atomically and keeps one `.bak`.\n\n## Rules\n\n- An unknown project is a stop, never a guess. Bootstrap first, then stop on what remains.\n- An entry is added only with explicit user confirmation of repo, series and chain.\n- One repo with several projects is normal. Those entries can disagree on\n  `odoo_version` and `branch_flow`. Name the project.\n- Never hand-edit the map file.\n- `base_branch` is what a task PR targets. It is often not the GitHub default branch.\n",{"name":5,"description":7,"user-invocable":20},"main","043a283d6e259355cd1601e000c45e1ee8ebd8bd","plugins\u002Fodoo-dev\u002Fskills\u002Fodoo-repo-map","https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features","https:\u002F\u002Fgithub.com\u002FCrpaxton4","Computer Science\r\nMiami University","2026-11-02 22:38:24",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Crpaxton4\u002Fdevcontainer-features --skill odoo-repo-map",{"tool":37,"command":38},"bunx","bunx skills add Crpaxton4\u002Fdevcontainer-features --skill odoo-repo-map",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Crpaxton4\u002Fdevcontainer-features --skill odoo-repo-map","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-dev\u002Fskills\u002Fodoo-repo-map\u002FSKILL.md",true,[45,51,55,59,63,67],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"scripts\u002Fproject-bootstrap.sh","SCRIPT","脚本",4478,"https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-dev\u002Fskills\u002Fodoo-repo-map\u002Fscripts\u002Fproject-bootstrap.sh",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"scripts\u002Fproject-resolve.sh",5664,"https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-dev\u002Fskills\u002Fodoo-repo-map\u002Fscripts\u002Fproject-resolve.sh",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"scripts\u002Frepo-map.sh",5883,"https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-dev\u002Fskills\u002Fodoo-repo-map\u002Fscripts\u002Frepo-map.sh",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"scripts\u002Frepos-dir.sh",4070,"https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-dev\u002Fskills\u002Fodoo-repo-map\u002Fscripts\u002Frepos-dir.sh",{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"scripts\u002Ftests\u002Frepo-map.test.sh",10670,"https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-dev\u002Fskills\u002Fodoo-repo-map\u002Fscripts\u002Ftests\u002Frepo-map.test.sh",{"path":68,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":69,"sourceHtmlUrl":70},"scripts\u002Ftests\u002Frepos-dir.test.sh",6122,"https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-dev\u002Fskills\u002Fodoo-repo-map\u002Fscripts\u002Ftests\u002Frepos-dir.test.sh",[72,79,86,93,100,107],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M75TQ56QVZX3Q680X89RT6FT","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.","https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-orchestrator\u002Fskills\u002Freport-incident\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M75TQ2RBNTA4EXJ4BQ3HRYXY","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.","https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-dev\u002Fskills\u002Fprinciples\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M75TQ0DVV793EWKKFN26408W","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.","https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-dev\u002Fskills\u002Fodoo-upgrade\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M75TPXTR66V72DA42QSDQDPM","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.","https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-dev\u002Fskills\u002Fodoo-upgrade-project\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M75TPVQ93TAY7KDB6XYDTVMK","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.","https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-dev\u002Fskills\u002Fodoo-test-run\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M75TPR5N29G38HDSCKYEC350","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.","https:\u002F\u002Fgithub.com\u002FCrpaxton4\u002Fdevcontainer-features\u002Fblob\u002Fmain\u002Fplugins\u002Fodoo-dev\u002Fskills\u002Fodoo-task-env\u002FSKILL.md",[],[]]