race-check

Run the Go race detector and analyze WARNING: DATA RACE patterns.

23|1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/PeterBooker/veloria --skill race-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: race-check
Source: https://github.com/PeterBooker/veloria/tree/main/.claude/skills/race-check
Command: npx skills add https://github.com/PeterBooker/veloria --skill race-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers identify and fix data races in concurrent Go code, preventing subtle bugs and improving application stability.

Core Features & Use Cases

  • Automated Race Detection: Leverages Go's built-in race detector to find concurrency issues.
  • Targeted Analysis: Can scan specific packages or the entire project.
  • Use Case: After modifying goroutines or mutexes in the internal/repo/ package, run this skill to ensure no new data races were introduced.

Quick Start

Run the race detector on the internal repo package.

Frequently Asked Questions about race-check

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

FAQPage Schema
How do I detect data races in concurrent Go code?

To detect data races in concurrent Go code, execute the Go race detector to identify WARNING: DATA RACE patterns within packages containing tests or user-specified paths. It analyzes output and suggests fixes using synchronization primitives like RWMutex and atomic operations.

What is the best way to find concurrency issues in a specific Go package?

The best way to find concurrency issues in a specific Go package is to run a targeted race detector scan on user-specified paths. This identifies data races introduced after modifying goroutines or mutexes and suggests common synchronization fixes.

How does the Go race detector suggest fixes for data races?

The Go race detector suggests fixes for data races by analyzing WARNING: DATA RACE patterns in the output and recommending common synchronization primitives like RWMutex, UpdateMutex, and atomic operations to resolve the concurrent access conflicts.

Can I scan my entire Go project for data races?

Yes, you can scan your entire Go project for data races. The race detector can target the entire project or scan specific packages with tests to ensure no new concurrency issues were introduced during development.

Why should I run a race detector after modifying goroutines?

You should run a race detector after modifying goroutines to prevent subtle bugs and improve application stability. It identifies concurrent data access conflicts and suggests appropriate mutex or atomic operation fixes to ensure thread safety.