Repo Agents

Lifecycle-Innovations-Limited/claude-ops

Claude Code plugin that turns the terminal into a business ops dashboard: briefings, unified inbox, PR merging, AWS monitoring, revenue, marketing, voice and auto-fix hooks.

  • 541 GitHub stars
  • Shell
  • ⚖️ MIT
  • 🎯 Advanced
View on GitHub (opens in a new tab) Setup guide
Lifecycle-Innovations-Limited/claude-ops preview image

What it is

claude-ops is a Claude Code plugin, distributed through a marketplace, that adds many /ops:* slash commands and specialist agents. They cover infrastructure health, CI/CD, a unified inbox, PRs, sprint state, revenue (Stripe, RevenueCat, AWS), e-commerce, marketing and voice. A background launchd daemon pre-warms briefing data so /ops:go loads quickly, and v2 added an auto-fix subsystem plus always-on safety hooks. The installer can also mirror skills into other CLIs such as Codex, Gemini, OpenClaw, Hermes and OpenCode.

Who it's for

  • Solo founders and small teams who run engineering and business operations from Claude Code
  • Developers who want one morning briefing across infra, CI, PRs, inbox, sprint and revenue
  • Teams that want automated post-merge deploy verification and build-failure auto-fix

Requirements

Requirements

  • Claude Code with plugin marketplace support
  • gh CLI (GitHub features depend on it) and aws CLI (AWS monitoring depends on it)
  • API keys or tokens for the services you enable (e.g. Stripe, RevenueCat, Klaviyo, Meta, Bland, ElevenLabs, Twilio)
  • Node.js/npm for the optional cross-CLI installer
  • Optional: CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 for Agent Teams coordination

Setup

  1. Add the marketplace

    Add the claude-ops marketplace, which ships the ops plugin and the desktop-act companion.

    bash
    /plugin marketplace add Lifecycle-Innovations-Limited/claude-ops

  2. Install the ops plugin

    Install ops from the marketplace. desktop-act can optionally be installed explicitly, though /ops:setup also co-installs it by default.

    bash
    /plugin install ops@ops-marketplace

  3. Run the guided setup wizard

    The wizard installs the background daemon early (Step 2c), so briefing-pre-warm is already running every 2 minutes while you finish setup.

    bash
    /ops:setup

  4. Optional: cross-CLI install

    Clone the repo and run the installer to mirror skills and binstubs into every detected CLI from a central config at ~/.config/claude-ops-installer/config.yaml.

    bash
    git clone https://github.com/Lifecycle-Innovations-Limited/claude-ops.git
cd claude-ops/installer
npm install
node bin/claude-ops-installer.mjs install

Examples

Morning briefing

Prompt
prompt
/ops:go

Expected output: Shows a dashboard of infra, CI/CD, inbox, PRs, sprint and revenue. The daemon's warm cache lets it load in under 3 seconds after setup.

Enable the auto-fix subsystem

bash
bash
/plugin update ops@ops-marketplace
/ops:setup
/ops:deploy-fix configure
/ops:deploy-fix

What it does: Upgrades the plugin, runs the wizard for the v2 toggles, maps repos to deploy URLs in ~/.claude/config/post-merge-services.json, then shows status, budget and live runs.

Inbox, PRs and incidents

Prompt
prompt
/ops:inbox
/ops:merge
/ops:fires

Expected output: Unified inbox across channels, the autonomous PR merge pipeline, and an incident view covering AWS.

Join the next meeting

Prompt
prompt
/ops:voice join --at next

Expected output: Auto-joins the next calendar meeting with smart AV defaults. Outbound twilio and bland calls pass through a per-message approval gate.

Enable Agent Teams

bash
bash
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1

What it does: Setting this environment variable makes skills that spawn agents create named teams whose agents share context and accept mid-flight steering.

Pros & cons

Pros

  • Pro:One command surfaces infra, CI, inbox, PRs, sprint and revenue in a single briefing
  • Pro:Most integrations offer a zero-config MCP OAuth path or a CLI path with more features, chosen per integration in the wizard
  • Pro:Safety hooks (secret-scan, rm -rf anchor block, main push warning) and per-repo auto-fix budget caps (default 3/hour) limit runaway behaviour
  • Pro:Broad coverage: 22 integrations, AWS-wide probing, and a cross-CLI installer

Cons

  • Con:Many features need extra CLIs or API keys, and several integrations (e.g. WhatsApp, GitHub, AWS) have no MCP path and depend on a CLI
  • Con:Some features are macOS-specific (launchd daemon, Phone.app/FaceTime via Continuity)
  • Con:The README is inconsistent on counts and versions (66 vs 22 skills, v3.11.0 badge vs v3.6 section), so check the repo for current facts

Images

Lifecycle-Innovations-Limited/claude-ops preview image
Lifecycle-Innovations-Limited/claude-ops preview image · Lifecycle-Innovations-Limited/claude-ops on GitHub · MIT
Lifecycle-Innovations-Limited/claude-ops preview image