Go: Distributed Systems

What you can ask

• Review this for consistency, ordering, retries, and partial-failure risk. Report concrete, causal findings.Copy

  · Review Go Distributed Change skill

• Diagnose this prod issue from evidence. Find the failure mechanism, violated invariant and recovery.
• Design or implement this change. Bound concurrency, retries, and ownership; preserve safety under ambiguity and failure.

Skills

6 in the ChatGPT listing

• Go Concurrency LifecycleUse for in-process Go concurrency ownership, cancellation, races, leaks, synchronization, and bounds.
• Go Data ConsistencyUse for Go transaction, cache, migration, and DB/broker consistency.
• Go Distributed CoordinationUse for Go cross-process ownership, leases, fencing, failover, sagas, and recovery.
• Go Message ProcessingUse for Go broker delivery, ACK, replay, ordering, poison recovery, outbox, or inbox.
• Go Service ResilienceUse for cross-service Go deadlines, retries, admission, shedding, and recovery.
• Review Go Distributed ChangeUse to review Go diffs/PRs for distributed failures in transactions, brokers, retries, leases, or effects.