Repository navigation
feat: add EventRelay Gemini change verification command - #2423
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
🟡 Changes recommended
Immutable worktree binding and rewritten-history handling are incomplete, allowing verification against stale or incorrect scopes.
2 open findings
What changed in this PR
Adds /verify-change to the repository-owned Gemini CLI extension for fail-closed, evidence-layered change verification.
Changes:
- Adds the verification prompt and four verdicts.
- Documents command usage and bumps the extension to 0.3.0.
- Adds focused prompt-contract tests.
| File | Description |
|---|---|
.gemini/extensions/eventrelay-engineering/commands/verify-change.toml |
Defines verification scope, evidence rules, and verdicts. |
.gemini/extensions/eventrelay-engineering/README.md |
Documents /verify-change. |
.gemini/extensions/eventrelay-engineering/gemini-extension.json |
Bumps version to 0.3.0. |
tests/unit/test_eventrelay_gemini_extension.py |
Tests the new command contract. |
🧠 Review effort: Balanced
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|

Closes #2422
Outcome
Adds
/verify-changeto the repository-owned Gemini CLI extension. The command verifies one bounded EventRelay change and requested claim at an immutable target, keeps artifact, local, provider, merge, deployment, and production evidence separate, and returns exactly one fail-closed verdict:VERIFIED,FAILED,STALE, orUNVERIFIED.Scope
/verify-changeTOML prompt; exact-SHA and worktree-state binding; repository-derived local commands; read-only provider evidence rules; deterministic verdict precedence; non-mutation and secret-safety boundaries; evidence-ledger output; version 0.3.0; documentation; focused extension contracts.Risk
Verification
Exact head:
6e72c5b0f467cad62f05b252b7e4be33f3cfaf94python3 -m unittest -v tests.unit.test_eventrelay_gemini_extension— 25 passed on Python 3.14./opt/homebrew/bin/python3.12 tests/unit/test_eventrelay_gemini_extension.py— 25 passed on Python 3.12.gemini extensions validate .gemini/extensions/eventrelay-engineering— passed.git diff --cached --checkbefore commit and committed diff checks — passed; PR contains four expected files, 351 additions, and 1 deletion.Evidence boundary
Current evidence proves the exact local artifact, focused contract behavior, manifest validity, isolated extension discovery, changed-scope secret scan, and exact-head provider checks and review. It does not prove merge persistence, deployment, production behavior, a Gemini model response, or a user-global installation.
Agent handoff
/verify-changeimplementation.