Skip to content

feat: add /runners-check command for quick queue health diagnostics#676

Merged
marcusquinn merged 1 commit intomainfrom
feature/queue-check-command
Feb 8, 2026
Merged

feat: add /runners-check command for quick queue health diagnostics#676
marcusquinn merged 1 commit intomainfrom
feature/queue-check-command

Conversation

@marcusquinn
Copy link
Owner

@marcusquinn marcusquinn commented Feb 8, 2026

Summary

  • Adds /runners-check slash command for quick supervisor queue diagnostics
  • Shows batch status, open PRs needing merge, stuck tasks, system resources, and cron health
  • Groups with /runners in autocomplete for discoverability
  • Supports --fix flag for auto-resolving simple issues (merge green PRs, clean stale worktrees)
  • Updated AGENTS.md orchestration row to reference the new command

Usage

/runners-check           # Check active batch
/runners-check --fix     # Auto-fix simple issues
/runners-check --all     # Show all batches

Summary by CodeRabbit

Release Notes

  • New Features

    • Added a new health-check diagnostic tool for monitoring queue status, worker health, and system resources.
  • Documentation

    • Added comprehensive reference documentation for the diagnostic utility with configuration options, parallel diagnostic steps, and unified reporting format.

Lightweight slash command that shows batch status, open PRs needing
merge, stuck tasks, system resources, and cron pulse health. Groups
with /runners in autocomplete. Supports --fix flag for auto-resolving
simple issues (merge green PRs, clean stale worktrees).
@gemini-code-assist
Copy link

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 8, 2026

Walkthrough

This pull request adds a new /runners-check command documentation and updates the AGENTS.md index to reference it. The new documentation outlines a health-check workflow for the batch queue, including parallel diagnostics and a unified report format. No code logic changes are introduced.

Changes

Cohort / File(s) Summary
Documentation Index
.agents/AGENTS.md
Updated Orchestration section to include /runners-check alongside supervisor-helper.sh for quick queue status visibility.
New Command Documentation
.agents/scripts/commands/runners-check.md
New command documentation describing parallel health-check workflow for batch queue, workers, PRs, worktrees, and system resources with unified report format and configuration arguments.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Poem

🏃 Swift runners check their beat,
Batch and workers, diagnose neat,
Health reports sing crystal clear,
Queue thrives bright without a fear! ✨

🚥 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 specifically summarizes the main change: adding a new /runners-check command for queue health diagnostics, which directly aligns with the PR's core objective and the files changed.
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 unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feature/queue-check-command

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.

@sonarqubecloud
Copy link

sonarqubecloud bot commented Feb 8, 2026

@github-actions
Copy link

github-actions bot commented Feb 8, 2026

🔍 Code Quality Report

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

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

�[0;34m[INFO]�[0m Recent monitoring activity:
Sun Feb 8 22:08:22 UTC 2026: Code review monitoring started
Sun Feb 8 22:08:22 UTC 2026: SonarCloud - Bugs: 0, Vulnerabilities: 0, Code Smells: 41

📈 Current Quality Metrics

  • BUGS: 0
  • CODE SMELLS: 41
  • VULNERABILITIES: 0

Generated on: Sun Feb 8 22:08:25 UTC 2026


Generated by AI DevOps Framework Code Review Monitoring

@marcusquinn marcusquinn merged commit 77c5851 into main Feb 8, 2026
9 of 11 checks passed
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: 1

🤖 Fix all issues with AI agents
In @.agents/scripts/commands/runners-check.md:
- Line 35: Add a blank line immediately before each level-3 heading (the lines
starting with "###") so headings like "### Batch Status" and the other h3
headings referenced are surrounded by a blank line above them to satisfy MD022;
update every "###" heading in the document accordingly.
🧹 Nitpick comments (1)
.agents/scripts/commands/runners-check.md (1)

11-29: Consider showing explicit parallel execution syntax.

Line 13 instructs to "Run these commands in parallel" but shows sequential command examples. For true parallel execution, consider adding a note about using background jobs or the parallel command:

# Option 1: Background jobs
supervisor-helper.sh status 2>&1 &
gh pr list ... &
git worktree list 2>/dev/null &
supervisor-helper.sh db "..." &
wait

# Option 2: GNU parallel (if available)
parallel ::: \
  "supervisor-helper.sh status 2>&1" \
  "gh pr list ..." \
  "git worktree list 2>/dev/null" \
  "supervisor-helper.sh db '...'"

However, if the intent is for the Build+ agent to execute these conceptually in parallel (via its own orchestration), the current format is acceptable as documentation.


Present results as a concise dashboard:

### Batch Status
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Fix markdown heading format (MD022 violations).

Headings should be surrounded by blank lines. Add a blank line before each of these h3 headings:

📝 Proposed fix for markdown formatting
 Present results as a concise dashboard:
+
 ### Batch Status
 - Batch name, total/completed/queued/running/failed counts
 - Any tasks stuck in retrying or evaluating for >10 minutes
+
 ### Action Items
 Flag these for the user (most important first):
 1. **PRs ready to merge** — all CI green, no review comments
 2. **PRs with CI failures** — need investigation
 3. **Tasks stuck** — in retrying/evaluating too long
 4. **Tasks at max retries** — need manual intervention or re-queue
 5. **Stale worktrees** — for tasks already deployed/merged
+
 ### System Health
 - Load, memory, worker count
 - Cron pulse status: `~/.aidevops/agents/scripts/supervisor-helper.sh cron status 2>&1`

Also applies to: 39-39, 47-47

🧰 Tools
🪛 GitHub Check: Codacy Static Code Analysis

[notice] 35-35: .agents/scripts/commands/runners-check.md#L35
Expected: 1; Actual: 0; Below

🪛 markdownlint-cli2 (0.20.0)

[warning] 35-35: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

🤖 Prompt for AI Agents
In @.agents/scripts/commands/runners-check.md at line 35, Add a blank line
immediately before each level-3 heading (the lines starting with "###") so
headings like "### Batch Status" and the other h3 headings referenced are
surrounded by a blank line above them to satisfy MD022; update every "###"
heading in the document accordingly.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant