Skip to content

feat: add /setup-aidevops command#11

Merged
marcusquinn merged 1 commit intomainfrom
chore/add-setup-aidevops-command
Jan 7, 2026
Merged

feat: add /setup-aidevops command#11
marcusquinn merged 1 commit intomainfrom
chore/add-setup-aidevops-command

Conversation

@marcusquinn
Copy link
Owner

@marcusquinn marcusquinn commented Jan 7, 2026

Summary

Add /setup-aidevops command to quickly deploy latest agent changes locally.

Usage

/setup-aidevops

Runs ~/Git/aidevops/setup.sh to:

  1. Deploy agents to ~/.aidevops/agents/
  2. Update OpenCode commands
  3. Regenerate agent configurations
  4. Copy VERSION file

User still needs to restart OpenCode after setup to load new config.

Summary by CodeRabbit

  • New Features
    • Added /setup-aidevops command for deploying the latest aidevops agent changes locally, with accompanying documentation detailing the setup process and post-deployment steps.

✏️ Tip: You can customize this high-level summary in your review settings.

- Runs setup.sh to deploy latest agent changes locally
- Useful after pulling updates or making local changes
- Reminds user to restart OpenCode after setup
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 7, 2026

Walkthrough

A new OpenCode command /setup-aidevops is introduced with accompanying documentation that guides deployment of latest aidevops agent changes locally. The command is added to the script's generated command catalog and appears in onboarding-related sections, resulting in duplicate entries in the final command listings.

Changes

Cohort / File(s) Summary
OpenCode Command Addition
setup-aidevops.md, .agent/scripts/generate-opencode-commands.sh
New /setup-aidevops command with documentation added to the script's command generation logic. Command entries appear in two distinct output sections (onboarding and available commands list), creating duplicate command references in generated output.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Poem

New automation blooms, a setup command takes flight 🚀
DevOps gardens grow with aidevops delight ✨
One feature planted twice—a duplicate surprise,
But tidy shells and zero debt before our eyes 🌟

🚥 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 clearly and directly summarizes the main change: adding a new /setup-aidevops command to the codebase.
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

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

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

@gemini-code-assist
Copy link

Summary of Changes

Hello @marcusquinn, I'm Gemini Code Assist1! 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 introduces a new "/setup-aidevops" command designed to significantly streamline the local development workflow for AI agents. By automating the deployment of agent changes, updating OpenCode commands, and regenerating configurations, it aims to reduce manual effort and ensure developers can quickly and consistently work with the latest agent versions.

Highlights

  • New Command Introduction: A new command, "/setup-aidevops", has been added to simplify the local deployment of the latest AI agent changes.
  • Automated Setup Process: This command automates the deployment of agents, updates OpenCode commands, regenerates agent configurations, and copies the VERSION file, all by executing "~/Git/aidevops/setup.sh".
  • Post-Setup Requirement: Users are reminded that a restart of OpenCode is necessary after running the setup command to load the newly deployed configurations and 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.

@sonarqubecloud
Copy link

sonarqubecloud bot commented Jan 7, 2026

@github-actions
Copy link

github-actions bot commented Jan 7, 2026

🔍 Code Quality Report

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

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

�[0;34m[INFO]�[0m Recent monitoring activity:
Wed Jan 7 21:30:36 UTC 2026: Code review monitoring started
Wed Jan 7 21:30:36 UTC 2026: SonarCloud - Bugs: 0, Vulnerabilities: 0, Code Smells: 142
Wed Jan 7 21:30:36 UTC 2026: Qlty - 0 issues found, auto-formatting applied
Wed Jan 7 21:30:38 UTC 2026: Codacy analysis completed with auto-fixes
Wed Jan 7 21:30:39 UTC 2026: Applied 1 automatic fixes

📈 Current Quality Metrics

  • BUGS: 0
  • CODE SMELLS: 142
  • VULNERABILITIES: 0

Generated on: Wed Jan 7 21:31:11 UTC 2026


Generated by AI DevOps Framework Code Review Monitoring

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a new /setup-aidevops command for OpenCode, designed to help developers quickly apply local changes to their aidevops setup. The implementation is straightforward, but I've identified a potential robustness issue with a hardcoded path in the command. My review includes a suggestion to dynamically locate the repository, making the new command more reliable for developers who may have cloned the repository to a non-standard location. Otherwise, the changes look good.


**Command:**
```bash
cd ~/Git/aidevops && ./setup.sh

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The command to run the setup script uses a hardcoded path ~/Git/aidevops. This will fail if a developer has cloned the repository to a different location. To improve robustness, the command should dynamically locate the repository.

A reliable way to do this is by resolving the aidevops CLI symlink, which points into the repository. This ensures the command works regardless of where the repository is cloned.

Suggested change
cd ~/Git/aidevops && ./setup.sh
cd "$(dirname "$(readlink -f "$(which aidevops)")")" && ./setup.sh

@augmentcode
Copy link

augmentcode bot commented Jan 7, 2026

🤖 Augment PR Summary

Summary: Adds a /setup-aidevops OpenCode command to redeploy the latest aidevops agents locally.

Changes:

  • Generate setup-aidevops.md in ~/.config/opencode/command/ via .agent/scripts/generate-opencode-commands.sh.
  • Command runs cd ~/Git/aidevops && ./setup.sh to redeploy agents, refresh OpenCode commands, regenerate configs, and copy VERSION.
  • Expose /setup-aidevops in the command list printed at the end of command generation.
Technical Notes: OpenCode needs a restart after setup to load the updated commands/config.

🤖 Was this summary useful? React with 👍 or 👎

Copy link

@augmentcode augmentcode bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review completed. No suggestions at this time.

Comment augment review to trigger a new review at any time.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
.agent/scripts/generate-opencode-commands.sh (1)

1037-1069: Consider adding pre-checks and verification to the command documentation.

The command documentation is clear and well-structured. However, it could be more robust by including:

  1. Pre-flight check: Verify ~/Git/aidevops/setup.sh exists before running
  2. Status feedback: Mention that the script will show progress during execution
  3. Post-setup verification: Suggest checking the deployed version or listing updated commands

This would align better with the coding guidelines emphasis on reliability, clear logging, and feedback.

♻️ Proposed enhancement
 **Command:**
 ```bash
+# Verify setup script exists
+if [ ! -f ~/Git/aidevops/setup.sh ]; then
+  echo "Error: Setup script not found at ~/Git/aidevops/setup.sh"
+  exit 1
+fi
+
 cd ~/Git/aidevops && ./setup.sh
+
+# Verify deployment
+if [ -f ~/.aidevops/agents/VERSION ]; then
+  echo "Deployed version: $(cat ~/.aidevops/agents/VERSION)"
+fi

What this does:

  1. Deploys agents to ~/.aidevops/agents/
  2. Updates OpenCode commands in ~/.config/opencode/command/
  3. Regenerates agent configurations
  4. Copies VERSION file for version checks

After setup completes:
+- Verify no errors were reported during deployment
+- Check deployed version matches source: cat ~/.aidevops/agents/VERSION

  • Restart OpenCode to load new commands and config
  • New/updated commands will be available

</details>

Based on learnings, the `~/Git/aidevops/` path is the authoritative repository location.

</blockquote></details>

</blockquote></details>

<details>
<summary>📜 Review details</summary>

**Configuration used**: Path: .coderabbit.yaml

**Review profile**: CHILL

**Plan**: Pro

<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between 913b2d1c4df31bb0d945e766cf8965b9e4cbcdf0 and 9254b0ec9f2b038c37a6502a1b3149a038a65c2a.

</details>

<details>
<summary>📒 Files selected for processing (1)</summary>

* `.agent/scripts/generate-opencode-commands.sh`

</details>

<details>
<summary>🧰 Additional context used</summary>

<details>
<summary>📓 Path-based instructions (1)</summary>

<details>
<summary>.agent/scripts/*.sh</summary>


**⚙️ CodeRabbit configuration file**

> `.agent/scripts/*.sh`: Automation scripts - focus on:
> - Reliability and robustness
> - Clear logging and feedback
> - Proper exit codes
> - Error recovery mechanisms
> 

Files:
- `.agent/scripts/generate-opencode-commands.sh`

</details>

</details><details>
<summary>🧠 Learnings (7)</summary>

<details>
<summary>📓 Common learnings</summary>

Learnt from: CR
Repo: marcusquinn/aidevops PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-01-06T15:57:56.007Z
Learning: Applies to **/setup.sh : Deploy agents locally using ./setup.sh script


Learnt from: CR
Repo: marcusquinn/aidevops PR: 0
File: templates/home/AGENTS.md:0-0
Timestamp: 2025-12-22T01:24:53.937Z
Learning: Reference the authoritative repository at ~/Git/aidevops/ for all detailed AI assistant instructions and configurations


Learnt from: CR
Repo: marcusquinn/aidevops PR: 0
File: templates/home/AGENTS.md:0-0
Timestamp: 2025-12-22T01:24:53.937Z
Learning: Follow all security protocols and working directory specifications defined in ~/Git/aidevops/AGENTS.md


Learnt from: CR
Repo: marcusquinn/aidevops PR: 0
File: templates/home/AGENTS.md:0-0
Timestamp: 2025-12-22T01:24:53.937Z
Learning: Use the helper script at ~/Git/aidevops/.agent/scripts/setup-local-api-keys.sh to manage secure storage of API keys rather than manual configuration


Learnt from: CR
Repo: marcusquinn/aidevops PR: 0
File: AGENT.md:0-0
Timestamp: 2025-11-29T04:34:42.033Z
Learning: Maintain all AI assistant instructions, documentation, and operational guidance in AGENTS.md as the single source of truth


Learnt from: CR
Repo: marcusquinn/aidevops PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-11-29T04:34:27.158Z
Learning: All instructions, documentation, and operational guidance should be maintained in AGENTS.md as the single source of truth


Learnt from: CR
Repo: marcusquinn/aidevops PR: 0
File: GEMINI.md:0-0
Timestamp: 2025-11-29T04:34:30.742Z
Learning: Maintain all instructions, documentation, and operational guidance in AGENTS.md as the single source of truth


</details>
<details>
<summary>📚 Learning: 2026-01-06T15:57:56.007Z</summary>

Learnt from: CR
Repo: marcusquinn/aidevops PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-01-06T15:57:56.007Z
Learning: Applies to **/setup.sh : Deploy agents locally using ./setup.sh script


**Applied to files:**
- `.agent/scripts/generate-opencode-commands.sh`

</details>
<details>
<summary>📚 Learning: 2025-12-22T01:24:53.937Z</summary>

Learnt from: CR
Repo: marcusquinn/aidevops PR: 0
File: templates/home/AGENTS.md:0-0
Timestamp: 2025-12-22T01:24:53.937Z
Learning: Follow all security protocols and working directory specifications defined in ~/Git/aidevops/AGENTS.md


**Applied to files:**
- `.agent/scripts/generate-opencode-commands.sh`

</details>
<details>
<summary>📚 Learning: 2025-11-29T04:34:27.158Z</summary>

Learnt from: CR
Repo: marcusquinn/aidevops PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-11-29T04:34:27.158Z
Learning: All instructions, documentation, and operational guidance should be maintained in AGENTS.md as the single source of truth


**Applied to files:**
- `.agent/scripts/generate-opencode-commands.sh`

</details>
<details>
<summary>📚 Learning: 2025-11-29T04:34:30.742Z</summary>

Learnt from: CR
Repo: marcusquinn/aidevops PR: 0
File: GEMINI.md:0-0
Timestamp: 2025-11-29T04:34:30.742Z
Learning: Maintain all instructions, documentation, and operational guidance in AGENTS.md as the single source of truth


**Applied to files:**
- `.agent/scripts/generate-opencode-commands.sh`

</details>
<details>
<summary>📚 Learning: 2025-12-22T01:24:53.937Z</summary>

Learnt from: CR
Repo: marcusquinn/aidevops PR: 0
File: templates/home/AGENTS.md:0-0
Timestamp: 2025-12-22T01:24:53.937Z
Learning: Reference the authoritative repository at ~/Git/aidevops/ for all detailed AI assistant instructions and configurations


**Applied to files:**
- `.agent/scripts/generate-opencode-commands.sh`

</details>
<details>
<summary>📚 Learning: 2025-12-22T01:24:53.937Z</summary>

Learnt from: CR
Repo: marcusquinn/aidevops PR: 0
File: templates/home/AGENTS.md:0-0
Timestamp: 2025-12-22T01:24:53.937Z
Learning: Use the helper script at ~/Git/aidevops/.agent/scripts/setup-local-api-keys.sh to manage secure storage of API keys rather than manual configuration


**Applied to files:**
- `.agent/scripts/generate-opencode-commands.sh`

</details>

</details>

</details>

<details>
<summary>⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)</summary>

* GitHub Check: Codacy Static Code Analysis

</details>

<details>
<summary>🔇 Additional comments (1)</summary><blockquote>

<details>
<summary>.agent/scripts/generate-opencode-commands.sh (1)</summary><blockquote>

`1112-1112`: **LGTM - Summary listing is appropriate.**

The command is correctly listed in the Utilities section, consistent with other operational commands like `/onboarding` and `/agent-review`.

**Note**: The AI summary mentions "duplicate entries in the final command listings," but I only see this command listed once in the summary output (line 1112). The command file generation (lines 1042-1066) and summary listing are the expected two occurrences, not duplicates.

</blockquote></details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->

@marcusquinn marcusquinn merged commit 7d94b85 into main Jan 7, 2026
9 checks passed
@marcusquinn marcusquinn deleted the chore/add-setup-aidevops-command branch January 7, 2026 21:35
marcusquinn added a commit that referenced this pull request Feb 21, 2026
…ess (t1287)

- ai-actions.sh: add park_task to AI_VALID_ACTION_TYPES, validate_action_fields,
  execute_single_action, _extract_action_target, and implement _exec_park_task
  which appends a -needed blocker tag to a task line in TODO.md
- ai-reason.sh: add park_task capability (#11) to build_reasoning_prompt,
  add human-action blocker analysis (#11) to analysis framework, add park_task
  example to output format, add park_task rules, update simplified retry prompt
  to include park_task in valid action types list
@marcusquinn marcusquinn added the needs-review Flagged for human review by AI supervisor label Feb 22, 2026
@marcusquinn
Copy link
Owner Author

Flagged for Human Review

Reason: t011 (Evaluate Tambo AI generative UI SDK) has ~8h estimate requiring subtask breakdown, but is marked 'not-in-db' — cannot safely create subtasks due to cross-repo collision risk. Human needs to register this task in the supervisor DB first, then subtask it for dispatch.

This issue has been flagged by the AI supervisor for human review. Please assess and take appropriate action.


Flagged by AI Supervisor (automated reasoning cycle)

@marcusquinn
Copy link
Owner Author

marcusquinn commented Feb 23, 2026

Flagged for Human Review

Reason: Task t011 (Evaluate Tambo AI generative UI SDK) has ~8h estimate requiring subtasking, but is marked 'not-in-db: task not registered in supervisor DB — cannot create subtasks safely (cross-repo collision risk)'. Human needs to register this task in the supervisor DB (via claim-task-id.sh or manual DB insert for a managed private repo repo) before it can be broken down and dispatched.

This issue has been flagged by the AI supervisor for human review. Please assess and take appropriate action.


Flagged by AI Supervisor (automated reasoning cycle)

@marcusquinn
Copy link
Owner Author

Flagged for Human Review

Reason: t011 (Evaluate Tambo AI SDK) is marked not-in-db in the supervisor — cannot safely create subtasks due to cross-repo collision risk. Task is ~8h and needs subtasking before dispatch. Human should register it in supervisor DB via claim-task-id or manual DB insert, then subtask it.

This issue has been flagged by the AI supervisor for human review. Please assess and take appropriate action.


Flagged by AI Supervisor (automated reasoning cycle)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-review Flagged for human review by AI supervisor

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant