gig

gig is a remote-first release audit CLI for one critical question:

Did we miss any change for this ticket?

Start Here

Read these first if you are new:

  1. Quick Start
  2. Demo Guide
  3. Portfolio Guide
  4. CLI Guide

Core Workflow

  • inspect collects the full ticket story across repositories and branches
  • verify returns a safe, warning, or blocked verdict
  • manifest generate exports a release packet in Markdown or JSON

AI briefings stay optional. The source of truth stays inside gig.

Fastest Path

gig
gig login github
gig inspect ABC-123 --repo github:owner/name
gig verify --ticket ABC-123 --repo github:owner/name
gig manifest generate --ticket ABC-123 --repo github:owner/name

Why Teams Reach For It

gig is a good fit when:

  • one ticket can touch backend, frontend, database, scripts, or low-code assets
  • follow-up fixes arrive after QA or client review
  • release confidence depends on what actually reached the target branch
  • teams need the same evidence in terminal output, JSON, and release packets without reopening every repo

Documentation Map