ci: add PR brief generation job using AI

[donhardman]

• New workflow job generates brief summaries for PRs
• Triggers on pull_request events (opened and synchronize)
• Uses octomind-action with ollama:glm-5.1 model
• Posts full comment with change analysis

[github-actions]

Octomind — developer:brief (ollama:glm-5.1)

The diff is a single commit adding a new CI job. Let me verify the full context of the CI workflow to understand how this job fits in.

📦 Brief: Add AI-powered PR brief generation job to CI workflow

Overall risk: 🟡 MEDIUM · Cards: 1

#	Change	Risk	Confidence
1	New brief CI job auto-generates PR summaries using an external AI action	🟡	●●●

Card 1/1: New `brief` CI job auto-generates PR summaries using an external AI action · 🟡 · ●●●

INTENT
Automatically post AI-generated brief summaries as PR comments when a PR is opened or receives new pushes, so reviewers get an immediate overview of what changed.

WHAT CHANGED

• A new brief job is added to .github/workflows/ci.yml that runs only on pull_request events
• Two conditional steps: one fires on opened (full branch diff), one on synchronize (incremental commit diff)
• Both steps use muvon/octomind-action@master with ollama:glm-5.1 model and role: developer:brief
• The "New PR" step compares the head branch to the base branch; the "Push" step compares github.event.before to github.event.after
• Both steps post a full comment to the PR (the action's comment: 'full' option)
• Checkout uses fetch-depth: 0 to ensure full git history is available for diffing

IMPACT RADIUS

• All future PRs to master/main/develop will trigger this job and receive an AI-generated comment
• The OLLAMA_API_KEY secret must be configured in the repository — the job will fail at runtime if it's missing
• The muvon/octomind-action@master is pinned to the master branch (not a tagged release), so any push to that action's master could change behavior without warning

RISK
🟡 MEDIUM. Two practical concerns:

1. Action pinned to @master — this means every run pulls the latest commit from muvon/octomind-action's master branch. A breaking change or malicious commit to that repo would immediately affect this workflow. Pinning to a release tag or SHA would be more stable.
2. Missing secret = silent failure — if OLLAMA_API_KEY isn't configured in the repo/org secrets, the action will fail. There's no pre-check or early validation; the failure happens at the step level.

QUESTIONS

• Is ollama:glm-5.1 the intended model? GLM-5.1 is not a widely known model identifier — is this a custom Ollama model or a typo for a different model family?

DIVERGENCE
🧩 Incomplete change — The brief job only handles opened and synchronize actions, but pull_request events also fire for reopened, ready_for_review, and labeled/unlabeled (if configured). A reopened PR won't get a brief. This may be intentional, but it's worth noting.

📎 Source

• .github/workflows/ci.yml#L197-L226 — New brief job definition

📂 Files changed (1 file, ~32 lines)

• .github/workflows/ci.yml — CI workflow; adds brief job for AI-generated PR summaries

---

_{{tokens:205653,cost:0.20875500000000002}}