gt-update

Sync Gas Town forks with upstream and deploy updated Go binaries.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/justSteve/GasTownOperations --skill gt-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gt-update
Source: https://github.com/justSteve/GasTownOperations/tree/main/.claude/skills/gt-update
Command: npx skills add https://github.com/justSteve/GasTownOperations --skill gt-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps a fork of Gas Town synchronized with upstream, automates building and installing the updated binary, and verifies runtime health so manual maintenance is minimized and visible.

Core Features & Use Cases

  • Automated upstream fetch and fast-forward sync of the justSteve/gastown fork from steveyegge/gastown.
  • Build and install the Go gt binary to the system path with appropriate sudo actions, ensuring versions are recorded.
  • Run gt doctor as the gtuser with automated fixes, attempt targeted repairs up to two times, initialize dashboard terminals, and attach services to the mayor.
  • Produce a concise final status report that lists version changes, commits pulled, doctor warnings and failures, manual fixes attempted, and remaining human-action items.

Quick Start

Sync the justSteve/gastown fork with upstream, build and install the new gt binary as gtuser, run doctor with fixes, and save the summarized status report to /root/projects/gtOps/CurrentStatus.md.

Frequently Asked Questions about gt-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep a Gas Town fork synced with upstream and deploy the updated binary?

To sync a Gas Town fork, fetch upstream changes, fast-forward the fork, build the Go binary, install it with sudo, run doctor checks, and generate a status report summarizing version changes and manual fixes needed.

What do I need to set up before syncing and building the Gas Town Go binary?

Syncing and building Gas Town requires git access to upstream and origin repositories, Go build capabilities, and sudo access to install binaries and run gt commands as the gtuser.

What does the gt doctor check do during Gas Town maintenance?

The gt doctor check verifies runtime health, applies automated fixes, attempts targeted repairs up to two times, initializes dashboard terminals, and attaches services to the mayor.

How does automated fork synchronization handle failed health checks after a build?

Automated fork synchronization handles failed health checks by running gt doctor with automated fixes, attempting targeted repairs up to two times, and logging remaining human-action items in the final status report.

Why does my Gas Town fork maintenance still require manual action after running an automated sync?

Manual action is required when automated doctor fixes fail after two attempts, leaving unresolved warnings or failures that are explicitly listed as human-action items in the final summarized status report.

Can I use this automated Gas Town sync process for forks other than justSteve/gastown?

This sync process is specifically designed for maintaining the justSteve/gastown fork against steveyegge/gastown, handling daily updates, builds, doctor checks, and service restarts for that repository configuration.