go-work-sync

Reconcile Go workspace lock data after go.mod, go.sum, or go.work edits.

49|15|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/block/proto-fleet --skill go-work-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go-work-sync
Source: https://github.com/block/proto-fleet/tree/main/.claude/skills/go-work-sync
Command: npx skills add https://github.com/block/proto-fleet --skill go-work-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The go-work-sync Skill helps maintain a consistent Go module workspace by reconciling workspace lock data after edits to go.mod, go.sum, and root go.work. It ensures dependencies across server, plugin, and tests stay aligned with the repository's root workspace configuration.

Core Features & Use Cases

  • Reconciles go.work, go.work.sum, and module dependencies to keep the mono-repo lock data consistent.
  • Encourages committing resulting workspace changes alongside module edits.
  • Scopes changes to server/, plugin/, tests/, and root workspace files to prevent drift.

Quick Start

Run go work sync from the repository root to reconcile workspace lock data after dependency edits.

Frequently Asked Questions about go-work-sync

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

FAQPage Schema
How do I keep a Go mono-repo workspace in sync after editing module dependencies?

To keep a Go mono-repo workspace in sync, run the go work sync command from the repository root to reconcile workspace lock data after edits to go.mod or go.sum files.

What does go work sync do for mono-repo lock data?

The go work sync command reconciles workspace lock data by aligning dependencies across server, plugin, and tests modules with the root go.work configuration to ensure consistency.

When should I reconcile my go.work file in a mono-repo?

You should reconcile your go.work file whenever you edit go.mod or go.sum files under server/, plugin/, or tests/ directories to prevent dependency drift across the workspace.

Can I use go work sync to update dependencies across server, plugin, and tests directories?

Yes, you can use go work sync to update dependencies by scoping changes to server/, plugin/, tests/, and root workspace files to ensure all modules stay aligned with the root go.work.

Do I need to commit go.work and go.work.sum after reconciling workspace dependencies?

Yes, you need to commit go.work and go.work.sum after reconciling workspace dependencies to ensure the resulting workspace changes are saved alongside your module edits.