القائمة
City lifecycle — status, start, stop, init
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | gc-city |
| description | City lifecycle — status, start, stop, init |
A city is a directory containing city.toml and .gc/ runtime state.
gc init # Initialize city in current directory
gc init <path> # Initialize city at path
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 start
gc 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>.
gc status # City-wide overview
gc session list # Session / agent status
gc rig status <name> # Rig status
gc suspend # Suspend entire city
gc resume # Resume suspended city
gc config show # Show resolved configuration
gc config explain # Show config layering and provenance
gc doctor # Run health checks
gc events # Tail the event log
gc event emit <type> [data] # Emit a custom event
See gc skills dashboard for full dashboard reference.
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
Project conventions for writing, editing, restructuring, or reviewing the Gas City user documentation — the Mintlify site under docs/. Use this whenever you touch anything in docs/ (pages, tutorials, guides, reference, concept pages, diagrams, navigation) or write/edit prose about Gas City, even when the request is just "fix the docs", "write a docs page", "the docs are wrong/confusing", "rename X across the docs", or an edit to a file under docs/. It defines the canonical six-primitive model, required terminology (orchestrator not controller, platform not SDK, formulas v2 as the value), the prose / emphasis / diagram conventions, the information architecture, the rule that generated docs are edited at their source, and the gates to run before docs work is done.
Routing work to agents with gc sling and formulas
Finding, creating, claiming, and closing work items (beads)
API server and web dashboard — config, start, monitor
Managing agents — list, peek, nudge, suspend, drain
Sending and reading messages between agents