gc-city
City lifecycle — status, start, stop, init
65
78%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./internal/bootstrap/packs/core/skills/gc-city/SKILL.mdCity Lifecycle
A city is a directory containing city.toml and .gc/ runtime state.
Initialization
gc init # Initialize city in current directory
gc init <path> # Initialize city at pathStarting and stopping
gc start # Start city under the supervisor
gc start <path> # Start city at path under the supervisor
gc supervisor run # Run the supervisor in the foreground
gc start --dry-run # Preview what would start
gc stop # Stop the current city
gc restart # Stop then startgc init and gc start register the city with the machine supervisor,
ensure it is running, and trigger an immediate reconcile. Interactive
sessions are created separately with gc session new <template>.
Status
gc status # City-wide overview
gc session list # Session / agent status
gc rig status <name> # Rig statusSuspending
gc suspend # Suspend entire city
gc resume # Resume suspended cityConfiguration
gc config show # Show resolved configuration
gc config explain # Show config layering and provenance
gc doctor # Run health checksEvents
gc events # Tail the event log
gc event emit <type> [data] # Emit a custom eventDashboard
See gc skills dashboard for full dashboard reference.
Packs
Packs extend Gas City with additional commands, prompts, formulas, and
doctor checks. Pack commands appear as top-level gc <pack> <command>
subcommands.
gc pack list # List installed packs
gc pack fetch # Fetch remote packs- Repository
- crypt0nerd1/gascity
- Commit
f530008
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.