From bf82b92749d6bf1de3a51955de6f2fb89500024e Mon Sep 17 00:00:00 2001
From: B Whitt <bot@ambient-code.local>
Date: Tue, 19 May 2026 16:07:02 +0000
Subject: [PATCH] chore: add CVE fixer guidance file
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Generated by /onboard — teaches the CVE fixer workflow how to create
fix PRs matching this repo's conventions.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---
 .cve-fix/examples.md | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)
 create mode 100644 .cve-fix/examples.md

diff --git a/.cve-fix/examples.md b/.cve-fix/examples.md
new file mode 100644
index 00000000..06c94daf
--- /dev/null
+++ b/.cve-fix/examples.md
@@ -0,0 +1,22 @@
+<!-- last-analyzed: 2026-05-19 | cve-merged: 0 -->
+<!-- Insufficient PR history for full pattern extraction.
+     Update with /guidance.update after more CVE fixes are merged. -->
+
+## Titles
+- No CVE fix PRs found — use conventional commit format: `fix(deps): <description> (<CVE-ID>)`
+
+## Branches
+- No CVE fix PRs found — use: `fix/cve-YYYY-NNNNN-<package>`
+
+## Files
+- Likely Go-based operator — expect `go.mod`, `go.sum`, and possibly vendor directory changes
+
+## Co-upgrades
+- No data available
+
+## PR Description
+- Include CVE ID, severity, CVSS score
+- Reference Jira issue
+
+## Don'ts
+- No data available