Repository navigation
docs(OMN-14105): genericize onex skills — strip internal operating detail for public exposure - #1869
Conversation
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 52 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (91)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
| Verdict | Meaning | Blocks merge? |
|---|---|---|
passed |
No critical/error findings | No |
blocked |
CRITICAL or ERROR findings found | Yes |
degraded |
All models unavailable (infra) | No (pilot) |
Powered by omniintelligence.review_pairing.cli_review — node-based adversarial review via HandlerLlmCliSubprocess (OMN-8524)
47e1d3e to
b0145f7
Compare
…tail for public exposure Scrub OmniNode-internal operating context from plugins/onex/skills/** before the public article drives readers to the repo: a contractor's real name, operator identity/email/ssh-user, LAN IPs + host nicknames, internal memory-doc citations, specific OMN ticket numbers, and machine paths (/Volumes/PRO-G40, omni_home) -> env-parameterized or generic placeholders. Preserves functional identifiers ($OMNI_HOME, OmniNode-ai org, node_* names, OMN-XXXX/regex placeholders, topics). Adds a public-skill-hygiene gate (scripts/check_public_skill_hygiene.py + allowlist + pre-commit hook + CI workflow "Public Skill Hygiene") so internal detail cannot regress into the public skills — detection wired as enforcement in the same change. Evidence: hygiene gate green (464 scanned, 0 blocked, 54 allowlisted keeps).
b4940f2 to
5a573ee
Compare
…x + routine) (#1879) ## omniclaude dev→main promotion Promotes `dev` (5fa434d) to `main` (currently e614e57). 9 commits, all routine previously-merged/reviewed ci/build/docs/fix work. The load-bearing change is the OMN-14244 deploy-gate matcher fix, which callers (omnibase_core/omnibase_infra/omnimarket) resolve from omniclaude `@main` — this promotion is required to unblock omnibase_infra#2245 (OMN-14190 Piece-4). Promotion branch tree equals `origin/dev` (`-s ours --allow-unrelated-histories` merge of `origin/main` for mergeability only — `origin/main` and `origin/dev` have no common git ancestor in this repo's history; verified `git diff origin/dev` on the promotion branch is empty). dev-head (5fa434d) is an ancestor of this branch so the cited OCC receipt binds. Tracked under a dedicated promotion ticket (OMN-14249, following the OMN-13828 promotion-ticket precedent) so the OCC receipt binds cleanly to this PR's number without superseding the already-merged OMN-14244/OMN-14190 contracts. Branch renamed from an earlier `promotion/omn-14244-...` attempt (#1878, closed) because the repo's DoD Evidence Check hard gate derives its required ticket from the branch name. ### Commits (origin/main..origin/dev) - `5fa434d06` fix(OMN-14244): narrow deploy-gate runtime-path matcher (stop false-positiving non-deploy CLIs, catch real deploy CLIs) (#1876) - `1b74ec1f0` feat(OMN-14190): wire OCC stamp/validate pre-commit hook (#1875) - `62308da2e` docs(OMN-14105): genericize onex skills — strip internal operating detail for public exposure (#1869) - `60cfec6fd` ci(OMN-14176): keep hostile reviewer on dev torch-free path (#1873) - `df599a05c` docs(OMN-13961): handoff skill writes canonical docs/handoff/ (singular) not docs/handoffs/ (#1864) - `8e19db1b2` build(OMN-14178): bump omniintelligence pin to torch-free base (post-#768 rl split) (#1874) - `a6272b37d` ci(OMN-13502): flip no-faked-boundary gate report-only -> enforcing (#1860) - `b94d846db` ci(OMN-13902): sibling-lock-refresh workflow (fan-out) (#1857) - `12fe25f4d` fix(OMN-13940): unquarantine executable merge sweep cron (#1861) ### Note on `a6272b37d` (no-faked-boundary: report-only -> enforcing) This is a hardening flip, not a behavior regression — omniclaude's self-scan was burned to zero findings before the flip (OMN-13500/#1849) and the job is not yet a required branch-protection context (documented as a deliberate follow-up in #1860's own body), so it cannot wedge this or any other PR. ### Why this is not a prod/runtime action This is a `dev -> main` release-branch promotion for the omniclaude repo (a Claude Code plugin repo). It does not touch `.201`, any prod compose lane, or any live runtime. Operator-authorized (OMN-14190 Piece-4 chain). promotion-receipt: OCC-3791 Evidence-Source: OCC#3791 Evidence-Ticket: OMN-14249 Evidence-Commit: 40b994cd457bdd5cc71b123c8787114ea891c0ce Refs OMN-14249, OMN-14244, OMN-14190, OMN-13502. Supersedes #1877/#1878 (closed). --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: jonahgabriel <jonahgabriel@users.noreply.github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Summary
Genericizes
plugins/onex/skills/**to remove OmniNode-internal operating context before the public "Fable Going Behind API Pricing" article drives readers to the repo.Closes OMN-14105.
What changed (85 skill files + new gate)
--authorgit-filter →${OPERATOR_*}/${GIT_AUTHOR}/<user>placeholders..201/.200host nicknames → generic;/Volumes/PRO-G40machine paths →$OMNI_HOME.feedback_*/project_*/reference_*memory-doc citations → inlined principle, doc name dropped.OMN-<number>→<TICKET>;omni_homeprose/vars → "workspace".$OMNI_HOMEenv,OmniNode-aiorg,node_*names,OMN-XXXX/OMN-\d+placeholders, topic strings.Enforcement in the same change (Rule #5)
scripts/check_public_skill_hygiene.py+scripts/public_skill_hygiene_allowlist.yaml— detects 9 leak classes, allowlists 4 documented keeps (golden-path fixtures, denylist guard IP, generic SSRF test IPs, canonical interpreter path).dod_evidence
464 scanned, 0 blocked, 54 allowlisted..pyfiles clean — see OCC companion.OCC companion
Evidence-Source: OCC#3676
Evidence-Ticket: OMN-14105