chore: improve update prompt with in-session action hint

[marcusquinn]

Summary

• Updates the update-available prompt to tell users they can run !aidevops update directly in the chat session, not just in a separate terminal
• Changes applied to both the template (templates/opencode-config-agents.md) and the generator script (.agents/scripts/generate-opencode-agents.sh)

Summary by CodeRabbit

• Documentation
  • Enhanced update notification messaging with improved clarity and detail for users. When updates are available, users now receive comprehensive guidance that covers multiple update methods—including terminal commands and in-app shortcuts—ensuring better accessibility and clearer pathways for maintaining their software installation.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the user experience for aidevops by making the update process more intuitive. It clarifies how users can update the tool by providing an in-session command option, alongside the existing terminal command, directly within the update notification message. This change aims to streamline the update workflow and reduce potential confusion for users.

Highlights

• Update Prompt Clarity: The update-available prompt now explicitly informs users that they can initiate an update by typing "!aidevops update" directly within the chat session, in addition to running "aidevops update" in a terminal.
• Consistent Messaging: This improved messaging has been applied to both the agent configuration template and the script responsible for generating these configurations, ensuring consistency across different contexts.

Changelog

• .agents/scripts/generate-opencode-agents.sh
  • Updated the update notification message to include instructions for in-session updates.
• templates/opencode-config-agents.md
  • Modified the update notification message to advise on both terminal and in-session update commands.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6fededf and 001674b.

📒 Files selected for processing (2)

• .agents/scripts/generate-opencode-agents.sh
• templates/opencode-config-agents.md

---

Walkthrough

Two files updated with expanded user guidance for update notifications. The message instructing users to run aidevops update now includes alternative options: running the command in a terminal session or using a magic command inline (via !aidevops update). No logic or control flow changes.

Changes

Cohort / File(s)	Summary
Update Notification Messaging .agents/scripts/generate-opencode-agents.sh, templates/opencode-config-agents.md	Expanded update availability notification to include multiple update paths: terminal session execution, magic command syntax, or both. Previous instruction focused solely on terminal execution.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• fix: use placeholder versions in AGENTS.md example #220: Modifies user-facing update notification text in .agents/scripts/generate-opencode-agents.sh with placeholder version handling.
• fix: pass --interactive flag to aidevops-update-check.sh in AGENTS.md greeting #2557: Updates agent greeting/template files to enhance update check presentation with --interactive flag.
• feat: add runtime context hint to session greeting #419: Touches the same UPDATE_AVAILABLE notification and greeting flow within agent templates.

Poem

✨ A message refined, now twice as kind,
Update paths revealed, for users to find,
Terminal or magic, take your pick with ease,
Guidance expanded to help and to please! 🚀

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: improving the update prompt by adding an in-session action hint, which matches the core objective of allowing users to run !aidevops update directly in chat.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/update-update-prompt-message

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

🔍 Code Quality Report

�[0;35m[MONITOR]�[0m Code Review Monitoring Report

�[0;34m[INFO]�[0m Latest Quality Status:
SonarCloud: 0 bugs, 0 vulnerabilities, 111 code smells

�[0;34m[INFO]�[0m Recent monitoring activity:
Mon Mar 2 16:22:43 UTC 2026: Code review monitoring started
Mon Mar 2 16:22:44 UTC 2026: SonarCloud - Bugs: 0, Vulnerabilities: 0, Code Smells: 111

📈 Current Quality Metrics

• BUGS: 0
• CODE SMELLS: 111
• VULNERABILITIES: 0

Generated on: Mon Mar 2 16:22:46 UTC 2026

---

Generated by AI DevOps Framework Code Review Monitoring

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[gemini-code-assist]

Code Review

This pull request improves the update notification prompt by adding a hint for in-session updates. The changes are consistently applied to both the agent generation script and the configuration template. The new prompt is clearer for users, informing them they can update directly within the chat session. The implementation is straightforward and correct.

_{Note: Security Review is unavailable for this PR.}