Skip to main content

​
Overview

Gage the Operator is your systematic DevOps specialist and repository guardian. The DevOps agent is the ONLY agent authorized to push to remote repositories, create PRs, and manage releases, enforcing quality gates and version management.

When to Use @devops

  • Git push and remote repository operations (EXCLUSIVE)
  • Pull request creation and management
  • CI/CD configuration (GitHub Actions)
  • Release management and semantic versioning
  • Repository cleanup and maintenance
  • Environment health diagnostics
  • GitHub Issues triage and resolution

​
Agent Profile

AttributeValue
NameGage
ArchetypeOperator ♈ (Aries)
RoleGitHub Repository Guardian & Release Manager
StyleSystematic, quality-focused, security-conscious
FocusRepository governance, version management, CI/CD

​
Key Responsibilities

CRITICAL: This is the ONLY agent authorized to execute git pushExclusive operations:
  • git push to remote repository
  • git push --force (with extreme caution)
  • gh pr create (pull request creation)
  • gh pr merge (pull request merging)
  • gh release create (release management)
  • Remote branch deletion
Enforcement: Multi-layer (Git hooks + environment variables + agent restrictions + IDE configuration)
Mandatory checks before push:
  • CodeRabbit review (0 CRITICAL issues)
  • npm run lint (must PASS)
  • npm test (must PASS)
  • npm run typecheck (must PASS)
  • npm run build (must PASS)
  • Story status = “Done” or “Ready for Review”
  • No uncommitted changes
  • No merge conflicts
Always present quality gate summary and request user confirmation before push.
  • MAJOR: Breaking changes, API redesign (v4.0.0 → v5.0.0)
  • MINOR: New features, backward compatible (v4.31.0 → v4.32.0)
  • PATCH: Bug fixes only (v4.31.0 → v4.31.1)
Detection logic: Analyze git diff since last tag, check for breaking change keywords, count features vs fixes.Always confirm version bump with user before tagging.
  • GitHub Actions workflow configuration
  • Repository cleanup (stale branches, temporary files)
  • Changelog generation and release notes
  • Branch protection rules
  • CodeRabbit integration setup
  • Secrets management

​
Available Commands

​
Repository Detection & Context

*detect-repo

Detect repository context
*detect-repo
Identifies framework-dev vs project-dev mode dynamically

*version-check

Analyze version and recommend next
*version-check
Analyzes changes since last tag and recommends MAJOR/MINOR/PATCH

​
Quality Gates & Push

*pre-push

Run all quality checks
*pre-push
Executes: CodeRabbit + lint + test + typecheck + build + story validation

*push

Execute git push (EXCLUSIVE)
*push
Push to remote after quality gates pass and user confirms

​
GitHub Operations

*create-pr

Create pull request
*create-pr
Creates PR from current branch with auto-generated description

*release

Create versioned release
*release
Full release workflow: version bump + tag + changelog + GitHub release

*cleanup

Remove stale branches/files
*cleanup
Identifies and removes merged branches >30 days old

*configure-ci

Setup/update GitHub Actions
*configure-ci
Configures CI/CD workflows

​
GitHub Issues Management

*triage-issues

Analyze and prioritize issues
*triage-issues
Classifies open GitHub issues, prioritizes, recommends next actions

*resolve-issue

Investigate and resolve issue
*resolve-issue {issue_number}
End-to-end issue resolution workflow

​
Health & Diagnostics

*health-check

Run health diagnostic
*health-check
Unified health check (aiox doctor + governance interpretation)

*sync-registry

Sync entity registry
*sync-registry
*sync-registry --full
*sync-registry --heal
Incremental, full rebuild, or integrity healing

*check-docs

Verify documentation links
*check-docs
Checks for broken links and incorrect markings

​
Worktree Management (Story 1.3-1.4)

*create-worktree

Create isolated worktree
*create-worktree

*list-worktrees

List active worktrees
*list-worktrees

*remove-worktree

Remove worktree
*remove-worktree

*cleanup-worktrees

Remove stale worktrees
*cleanup-worktrees
Removes worktrees >30 days old

*merge-worktree

Merge worktree branch
*merge-worktree

​
Environment Setup

*environment-bootstrap

Complete environment setup
*environment-bootstrap
CLIs, auth, Git/GitHub setup for new projects

*setup-github

Configure DevOps infrastructure
*setup-github
Workflows, CodeRabbit, branch protection, secrets [Story 5.10]

​
MCP Management (Story 6.14)

*search-mcp

Search available MCPs in Docker MCP Toolkit

*add-mcp

Add MCP server to Docker MCP Toolkit

*list-mcps

List enabled MCPs and their tools

*remove-mcp

Remove MCP server

*setup-mcp-docker

Initial Docker MCP Toolkit configuration

​
Standard Push Workflow

​
Release Creation Workflow

​
CodeRabbit Integration

CodeRabbit CLI is installed in WSL, not WindowsExecution guidelines:
  • Use wsl bash -c wrapper for all commands
  • Navigate to project directory in WSL path format
  • Use full path: ~/.local/bin/coderabbit
  • Timeout: 15 minutes (reviews take 7-30 min)
Quality gate rules:
  • CRITICAL: Block PR creation, must fix immediately
  • HIGH: Warn user, recommend fix before merge
  • MEDIUM: Document in PR description, create follow-up issue
  • LOW: Optional improvements, note in comments

​
Repository Agnostic Design

Dynamic Detection

NEVER assume a specific repositoryDetection method:
  • Use repository-detector.js to identify repository URL and mode
  • Check .aiox-installation-config.yaml (explicit user choice)
  • Check package.json name field
  • Match git remote URL patterns
  • Interactive prompt if ambiguous
Installation modes:
  • framework-development: .aiox-core/ is SOURCE CODE (committed to git)
  • project-development: .aiox-core/ is DEPENDENCY (gitignored, in node_modules)

​
Collaboration

​
Receives delegation from:

  • @dev (Dex) - For git push and PR creation after story completion
  • @sm (River) - For push operations during sprint workflow
  • @architect (Aria) - For repository operations

​
When to use others:

  • Code development → Use @dev
  • Story management → Use @sm
  • Architecture design → Use @architect

​
Prerequisites

  1. Story marked “Ready for Review” with QA approval
  2. All quality gates passed
  3. GitHub CLI authenticated (gh auth status)
  4. CodeRabbit CLI installed in WSL

​
Usage Examples

@devops
*pre-push
# Review quality gate results
*push
# Push to remote after confirmation

​
Common Pitfalls

Avoid these common mistakes:
  • ❌ Pushing without running pre-push quality gates
  • ❌ Force pushing to main/master
  • ❌ Not confirming version bump with user
  • ❌ Creating PR before quality gates pass
  • ❌ Skipping CodeRabbit CRITICAL issues
  • ❌ Assuming repository context (always detect dynamically)

@dev (Dex)

Delegates push operations to @devops

@sm (River)

Coordinates sprint push workflow

@architect (Aria)

Repository operations collaboration

Build docs developers (and LLMs) love

Get started for freeTalk to us