skillassets

README

vigilante

vigilante is a local control plane for autonomous software delivery. It watches repositories, selects eligible work items, prepares isolated git worktrees, launches a supported coding-agent CLI, and keeps the issue tracker updated while the work moves toward a pull request.

It is the orchestration layer around agents such as codex, claude, and gemini, not the model itself. Vigilante owns scheduling, worktree isolation, backend coordination, and recovery so a repository checkout behaves like a controlled worker instead of a loose collection of scripts.

Docs · Closed Issues · Releases · Contributing

Start here: install vigilante, run vigilante setup, then register a repo with vigilante watch /path/to/repo.

Install

Install with Homebrew:

brew install vigilante

Requirements:

• git
• gh authenticated against the GitHub account Vigilante should operate with
• one supported coding-agent CLI installed locally: codex, claude, or gemini

Recommended machine setup:

vigilante setup --provider codex

Quick Start

Register a repository and let Vigilante manage it:

vigilante watch ~/path/to/repo

Useful follow-up commands:

vigilante list
vigilante status
vigilante service restart
vigilante daemon run --once

Typical first-run flow:

brew install vigilante
vigilante setup --provider codex
vigilante watch ~/hello-world-app
vigilante daemon run --once

What Vigilante Does

• Treats project-management work items as the queue for autonomous software delivery.
• Selects eligible issues using repository configuration, assignees, labels, and concurrency limits.
• Creates one isolated git worktree per issue so the main checkout stays stable.
• Chooses the right execution skill from repository shape and local context.
• Launches a supported coding-agent CLI under a consistent lifecycle.
• Tracks progress, failures, and pull-request state through the issue tracker and local session state.
• Recovers, resumes, redispatches, and cleans up runs without duplicating work.

How It Works

At a high level, Vigilante runs this loop for each watched repository:

1. Resolve the repository and discover its remote.
2. Read the configured issue-tracking backend and fetch open work items.
3. Filter to issues that are eligible and not already being handled.
4. Create an isolated worktree and issue branch.
5. Launch the selected coding-agent CLI with the repo-aware implementation skill.
6. Track progress locally and post execution updates back to the issue tracker.
7. Monitor the linked pull request and clean up or recover the session as needed.

GitHub is the only fully implemented backend today. The architecture already separates issue tracking, pull requests, labels, and rate limits so backends such as Linear and Jira can be added without rewriting the orchestration loop.

Key Commands

• vigilante setup: verify dependencies, install bundled skills, and install the managed service
• vigilante watch <path>: register a local repository for issue monitoring
• vigilante list: show watched repositories
• vigilante status: show service health, watched repos, active sessions, and rate-limit state
• vigilante logs: inspect local daemon and per-issue logs
• vigilante cleanup, vigilante redispatch, vigilante resume: recover or restart stuck work safely
• vigilante daemon run: run the watcher loop in the foreground

For command details and full flags, see DOCS.md.

Architecture At A Glance

Vigilante keeps orchestration backend-neutral through a small set of interfaces:

• IssueTracker: work item listing, details, comments, and operator commands
• PullRequestManager: PR discovery, merge state, and branch lifecycle
• LabelManager: repository and issue label synchronization
• RateLimiter: optional API quota awareness

That lets a watch target mix concerns such as issue tracking on one system and pull requests on another while keeping the execution loop stable.

More Docs

The full reference moved to DOCS.md, including:

• installation details and development mode
• full command reference and expected behaviors
• local state layout and logs
• issue selection, labeling, and pull-request maintenance
• headless agent execution contract
• GitHub integration, worktree strategy, and service behavior
• CI, releases, and implementation status notes

Documentation

Index

• Variables

Variables

var LabelsManifest embed.FS

LabelsManifest contains the canonical Vigilante repository label definitions.

var Skills embed.FS

Skills contains built-in runtime skill files for installed binaries.