ci: onboard multi-vendor AI PR review (OST-626 canary) - #1
Conversation
Add the three-lineage AI PR-review setup that every active BeliyDym repo inherits: - .github/workflows/ai-review.yml — thin caller of the reusable Claude reviewer at BeliyDym/.github@v1; on: pull_request [opened, reopened, synchronize]; enforce_bugfix_ledger: false (no BUGFIXES.md convention here); needs the ANTHROPIC_API_KEY repo secret. - .gemini/config.yaml — Gemini Code Assist review config, ignore_patterns tuned for this repo (docs, locales, assets, lockfiles). - .gemini/styleguide.md — review criteria tuned to the Python agent stack: exact-pin/uv.lock supply-chain gate, ruff PLW1514 encoding rule, provider credential handling, async correctness, pytest integration-marker discipline. Claude lens (this workflow) + Gemini Code Assist (App) + GitHub Copilot (App). Codex connector intentionally not part of the setup.
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
hermes-agent (self-improving multi-provider AI agent, Python) AI Review (Updated)Risk Level: HIGH Updated at 2026-06-03T08:41:50.323Z |
🔎 Lint report:
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 618747e56a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| jobs: | ||
| ai-review: | ||
| uses: BeliyDym/.github/.github/workflows/ai-review.yml@v1 |
There was a problem hiding this comment.
The new workflow executes BeliyDym/.github by the mutable @v1 ref while granting pull-requests: write, issues: write, and passing ANTHROPIC_API_KEY, so moving or hijacking that tag changes code this repo runs with write permissions and a secret. The repo's dependency policy requires GitHub Actions and reusable workflows to be pinned to a commit SHA with a version comment; use the current 40-character commit for v1 instead of the tag.
Useful? React with 👍 / 👎.
|
Closing — not merging. This internal-to-fork PR (base/head both BeliyDym/hermes-agent, isCrossRepository=false, so no upstream-leak surface) was opened during the initial canary attempt before IRON Council 3/3 re-pointed the Packet 2 canary to an independent repo (ovu-app, now PR NousResearch#20). Per the council decision (audits/ost626-fork-canary-scope/consensus.md), the 3 BeliyDym forks (hermes-agent, agent-orchestrator, GeoAgent) join the fleet in Packet 3 under a hardened internal-only contract: owner-gate The branch |
1 participant
Summary
OST-626 Packet 2 canary: onboard hermes-agent onto the three-lineage AI
PR-review setup that the rest of the BeliyDym fleet will inherit (Packet 3).
.github/workflows/ai-review.yml— thin caller of the reusable Claudereviewer at
BeliyDym/.github/.github/workflows/ai-review.yml@v1(
on: pull_request [opened, reopened, synchronize],enforce_bugfix_ledger: false)..gemini/config.yaml+.gemini/styleguide.md— Gemini Code Assist configand review criteria tuned to this Python agent stack (supply-chain pinning /
uv.lockgate, ruffPLW1514encoding rule, provider-credential handling,async correctness, pytest integration-marker discipline).
Three independent reviewers per PR: Gemini Code Assist (App) + Claude
(this reusable workflow) + GitHub Copilot (App). The OpenAI Codex connector
is intentionally not part of the setup.
Canary acceptance criteria (this PR is the test)
ANTHROPIC_API_KEYrepo secret — fails closed to HIGH +needs-human-reviewif absent, by design).repo).
Test plan
AI Reviewworkflow run appears under Actions for this PR.ANTHROPIC_API_KEY(SJ-owned) and re-run.