jonradoff

Vibectl — DevOps skill for Claude Code

DevOps community

Manage all your agentic engineering projects (i.e., vibe coding) for Claude Code in one place.

How to install Vibectl

This entry records only its repository, not the path inside it, so there is no exact command to give. Open jonradoff/vibectl and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Vibectl does

Manage all your agentic engineering projects (i.e., vibe coding) for Claude Code in one place. Orchestrate, deploy, manage github, and coordinate issues and feedback into your workflow.

Alternatives in DevOps

Composio Split — Manage Split feature flags and experiments 44.6k ★
Skypilot — Run, manage, and scale AI workloads on any AI infrastructure 9.7k ★
Skill Claw — OpenClaw instance administration — manage hosts across macOS, Ubuntu/Debian, Docker, OCI, and Proxmox 2.8k ★

README

VibeCtl

**Command-and-control for the agentic coding era.**

VibeCtl is a self-hosted project management system built for the way software is actually made today: AI agents doing the coding, humans directing strategy. It unifies issue tracking, deployment management, health monitoring, productivity analytics, and product feedback into one integrated workflow designed around Claude Code.

*We're entering software's creator era — where the gap between idea and working product has collapsed. VibeCtl is the cockpit for that new reality.*

![VibeCtl Dashboard](docs/screenshot.png)

Why VibeCtl

Modern agentic development creates a new coordination problem: you're running multiple AI-assisted projects simultaneously, context windows are finite, and the pace is fast. Jira is too heavyweight. Linear doesn't know about your deployments. GitHub Issues doesn't understand your architecture.

VibeCtl provides:

A VIBECTL.md file per project — the single source of truth that agents read before every session
An MCP server that agents use directly, without leaving Claude Code
Productivity analytics that measure developer output by intent, not lines of code — with per-developer attribution
A feedback pipeline that converts user reports into triaged issues and actionable prompts via Claude
Flexible deployment modes — run solo, run a team server, or connect your local dev environment to a central instance
Health checks that know the difference between "frontend is down" and "backend /healthz is degraded"
Multi-user access via GitHub OAuth with role-based permissions per project

Deployment Modes

VibeCtl supports four deployment configurations. Choose the one that fits your workflow:

Standalone (Solo Developer)

The default mode. Everything runs on one machine against one MongoDB instance. You get the full UI, Claude Code sessions, issue tracking, feedback, analytics — all local.

**Best for:** Individual developers ma