GitOps PR evidence replay
A PR that says 'fixes the crash loop' asks a reviewer to trust a summary. Evidence replay attaches the exact tool output the agent used, so the reviewer expands the same payloads instead of taking the conclusion on faith.
Start capture before you investigate
$ npx opskit evidence start --title "CrashLoop payment-service" # … investigation + /gitops-fix … $ npx opskit evidence bundle --out opskit-evidence.md $ npx opskit evidence attach-pr 42 --file opskit-evidence.md # needs gh auth
Capture only runs for the session where the hook is active — start it before the investigation begins, not after you've already seen the result.
What ends up in the PR
While the session is active, the evidence-capture hook stores redacted Kubernetes MCP tool output. evidence bundle collapses it into collapsible markdown sections and attaches it to the GitOps PR alongside the evidence summary, rollback plan, and verification checklist that k8s-fixer already generates.
Private GitOps repos
Public raw GitHub URLs return 404 without auth, so for private repos attach the evidence artifact directly on the PR or fetch it via an authenticated gh api download rather than linking to a raw file URL that reviewers can't open.
Optional: a terminal recording
Record the session with asciinema and attach the .cast file to the PR, or link an asciinema.org upload, for reviewers who want to watch the investigation happen rather than read the bundle.
Limitations
Evidence replay documents what the agent read and concluded — it doesn't substitute for a reviewer's own judgment on whether the patch is correct. Redaction removes obvious secrets from captured output, but treat the bundle as internal-review material, not something to paste into a public issue without a second look.
Ready to point it at your cluster?
Get OpsKit — $19