New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Vibe Concurrent Test Safety

by ash1794 in ash1794/vibe-engineering

Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering.

MITAuto-check passedDevelopment

Install Vibe Concurrent Test Safety

skills CLI
$ npx skills add ash1794/vibe-engineering --skill vibe-concurrent-test-safety -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ash1794/vibe-engineering vibe-concurrent-test-safety --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-concurrent-test-safety .claude/skills/vibe-concurrent-test-safety && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
vibe-concurrent-test-safety
GitHub stars
163
Token cost
~665 tokens
SKILL.md length
193 words
Files
1
Skills in repo
33
Repo updated
First seen
Licence
MIT

At a glance

Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering.

  • Works in 3 steps: Direct Mock State Access → Missing Context Cancellation Before… → Assertions on Timing
  • Writing tests that involve goroutines
  • SKILL.md covers When to Use This Skill, When NOT to Use This Skill, Common Concurrency Bugs in Tests and Audit Checklist, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Vibe Concurrent Test Safety is an agent skill from ash1794/vibe-engineering. Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering. Use when writing tests that involve goroutines, async operations, or shared mutable state.

Its SKILL.md is about 670 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Async programming. The repository describes itself as: 33 engineering discipline skills for Claude Code, OpenAI Codex & Gemini CLI + a CLI for CI/CD enforcement. Extracted from real-world multi-agent system development. Born from… The licence is MIT.

When your agent uses it

  • Writing tests that involve goroutines
  • Async operations
  • Shared mutable state

Example prompts

  • “Use the vibe-concurrent-test-safety skill to audit tests for concurrency safety — race conditions, shared mock state, cleanup ordering”
  • “/vibe-concurrent-test-safety”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Direct Mock State Access
  2. Missing Context Cancellation Before Cleanup
  3. Assertions on Timing

What it can do on your machine

Read from SKILL.md and the folder at commit 8f1d71b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are go).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Vibe Concurrent Test Safety loads about 665 tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 193 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~53
When it runs · the whole SKILL.md, loaded when a task matches
~665

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ash1794/vibe-engineering at commit 8f1d71b, republished under its MIT licence (© ash1794). 193 words, ~665 tokens.

Download SKILL.mdSave it as .claude/skills/vibe-concurrent-test-safety/SKILL.md (or your agent's skills folder).
name
vibe-concurrent-test-safety
description
Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering. Use when writing tests that involve goroutines, async operations, or shared mutable state.
user-invocable
true

vibe-concurrent-test-safety

Flaky tests are almost always concurrency bugs in the test, not the code.

When to Use This Skill

  • Writing tests that launch goroutines or async operations
  • Tests use shared mock objects accessed by multiple goroutines
  • Tests that fail intermittently ("flaky")
  • After adding -race flag and getting failures
  • Tests that involve daemon/server startup and shutdown

When NOT to Use This Skill

  • Purely synchronous tests with no concurrency
  • Tests that are already race-free (verified with -race flag)
  • Simple mock-based tests with single-threaded access

Common Concurrency Bugs in Tests

1. Direct Mock State Access
go
// BAD: Race condition -- mock.Requests accessed while goroutine writes
go daemon.Run(ctx)
time.Sleep(100 * time.Millisecond)
assert.Equal(t, 3, len(mock.Requests)) // RACE!

// GOOD: Thread-safe accessor
go daemon.Run(ctx)
time.Sleep(100 * time.Millisecond)
assert.Equal(t, 3, mock.RequestCount()) // Safe
2. Missing Context Cancellation Before Cleanup
go
// BAD: Close bus while daemon goroutine still using it
go daemon.Run(ctx)
defer bus.Close() // daemon may still be writing!

// GOOD: Cancel context first, wait, then cleanup
go daemon.Run(ctx)
defer func() {
    cancel()          // Signal daemon to stop
    <-daemon.Done()   // Wait for it
    bus.Close()        // Now safe
}()
3. Assertions on Timing
go
// BAD: Relies on timing
go startServer()
time.Sleep(50 * time.Millisecond) // May not be enough
resp := callServer()

// GOOD: Wait for readiness
go startServer()
waitForReady(server) // Poll or use channel
resp := callServer()

Audit Checklist

  • No direct access to shared mock fields (use accessors)
  • Context cancelled before resource cleanup
  • Goroutines joined before test ends (<-done or wg.Wait())
  • No time.Sleep for synchronization (use channels, waitgroups, or polling)
  • Assertions use Eventually or polling for async results
  • Test passes with -race flag
  • Test passes when run 100 times (-count=100)

Output Format

Concurrent Test Safety Audit: [Test File]

Issues Found: X

#IssueLineFix
1Direct mock access:42Use mock.RequestCount()
2Missing cancel before Close:15Add cancel() before defer
Suggested Fixes

[Code snippets for each fix]

© ash1794, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/vibe-engineering/skills/vibe-concurrent-test-safety of ash1794/vibe-engineering.

Open the folder on GitHubat commit 8f1d71b

Compare with similar skills

Vibe Concurrent Test Safety next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Vibe Concurrent Test Safety compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vibe Concurrent Test Safety this skillash1794/vibe-engineering163—~665Automated safety check: PassMIT
YugabyteDB ASH Instrumentationyugabyte/yugabyte-db11k—~4.5kAutomated safety check: PassCustom licence
Mirage VFS Adapter Authoringstrukto-ai/mirage3.7k—~2.5kAutomated safety check: PassApache-2.0
Golang Patternsantoniopaya22/go-rest-template1729 repos~3.5kAutomated safety check: PassNone
Rust Async Patternsdiodeme/Gold-Band14310 repos~3.1kAutomated safety check: PassAGPL-3.0
Swift Concurrencyhenrypldev/react-native-nitro-mlx1003 repos~3.1kAutomated safety check: PassMIT

Similar skills

  • YugabyteDB ASH Instrumentation

    yugabyte/yugabyte-db

    Procedure for adding or changing YugabyteDB Active Session History wait states in TServer and DocDB C++ code, including the macro to use for sync and async paths.

    11k GitHub stars~4.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Mirage VFS Adapter Authoring

    strukto-ai/mirage

    Builds or extends a custom Mirage virtual filesystem adapter for an API, database, object store or app data, with a working mount configuration and filesystem tests.

    3.7k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Golang Patterns

    antoniopaya22/go-rest-template

    Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable Go applications.

    172 GitHub starsUsed in 9 repos~3.5k tokens
    DevelopmentAuto-check passed

  • Rust Async Patterns

    diodeme/Gold-Band

    Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns.

    143 GitHub starsUsed in 10 repos~3.1k tokens
    DevelopmentAuto-check passed

  • Swift Concurrency

    henrypldev/react-native-nitro-mlx

    Diagnose Swift Concurrency issues, refactor callback-based code to async/await, and guide Swift 6 migration when working with tasks, actors, @MainActor, Sendable, data races, thread safety, or…

    100 GitHub starsUsed in 3 repos~3.1k tokens
    DevelopmentAuto-check passed

  • Rust Engineer

    farm-fe/farm

    Writes, reviews, and debugs idiomatic Rust code with memory safety and zero-cost abstractions.

    5.6k GitHub starsUsed in 1 repo~1.5k tokens
    DevelopmentAuto-check passed

More from ash1794/vibe-engineering

All 33 skills in this repo

  • Vibe Fuzz Parser Inputs

    ash1794/vibe-engineering

    Generates fuzz test scaffolding for parsers handling external input (YAML, JSON, config files, user input).

    163 GitHub stars~722 tokensUpdated 3 days ago
    Auto-check passed

  • Vibe Golden File Testing

    ash1794/vibe-engineering

    Implements snapshot/golden file tests with temporal normalization so tests don't break daily.

    163 GitHub stars~669 tokensUpdated 3 days ago
    Auto-check passed

  • Vibe Parallel Task Decomposition

    ash1794/vibe-engineering

    Analyzes large tasks for independent subtasks that can be safely parallelized.

    163 GitHub stars~717 tokensUpdated 3 days ago
    Auto-check passed

  • Vibe Slop Filter

    ash1794/vibe-engineering

    Strips AI-generation "smell" from prose before it ships (READMEs, docs, release notes, PR descriptions, posts, emails).

    163 GitHub stars~2.3k tokensUpdated 3 days ago
    Auto-check passed

  • Vibe Spec Sync

    ash1794/vibe-engineering

    Keeps specification documents and code in agreement. An agent skill from ash1794/vibe-engineering.

    163 GitHub stars~2.2k tokensUpdated 3 days ago
    Auto-check passed

  • Vibe Adversarial Test Generation

    ash1794/vibe-engineering

    Generates edge case, failure mode, and spec-driven test cases.

    163 GitHub stars~1.4k tokensUpdated 3 days ago
    Auto-check passed

Categories

Questions about Vibe Concurrent Test Safety

What does Vibe Concurrent Test Safety do?

Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering. Vibe Concurrent Test Safety is an agent skill from ash1794/vibe-engineering. Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering.

When should I use Vibe Concurrent Test Safety?

Vibe Concurrent Test Safety fits situations like: writing tests that involve goroutines; async operations; shared mutable state.

How do I install Vibe Concurrent Test Safety in Claude Code?

Run `npx skills add ash1794/vibe-engineering --skill vibe-concurrent-test-safety -a claude-code`. Or copy the skill folder (plugins/vibe-engineering/skills/vibe-concurrent-test-safety in ash1794/vibe-engineering) into .claude/skills/vibe-concurrent-test-safety in your project. Claude Code loads it when a task matches its description.

How do I install Vibe Concurrent Test Safety in Codex?

Run `npx skills add ash1794/vibe-engineering --skill vibe-concurrent-test-safety -a codex`. Or copy the skill folder (plugins/vibe-engineering/skills/vibe-concurrent-test-safety in ash1794/vibe-engineering) into .agents/skills/vibe-concurrent-test-safety in your project. Codex loads it when a task matches its description.

Can I use Vibe Concurrent Test Safety in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ash1794/vibe-engineering --skill vibe-concurrent-test-safety -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vibe-concurrent-test-safety, .gemini/skills/vibe-concurrent-test-safety, .github/skills/vibe-concurrent-test-safety and .opencode/skills/vibe-concurrent-test-safety in your project.

What does Vibe Concurrent Test Safety need to run?

SKILL.md names no scripts, command-line tools or credentials: Vibe Concurrent Test Safety is instructions for the agent only.

Does Vibe Concurrent Test Safety access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Vibe Concurrent Test Safety safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Vibe Concurrent Test Safety use?

Vibe Concurrent Test Safety is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Vibe Concurrent Test Safety use?

About 665 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Vibe Concurrent Test Safety?

Skills that share tags, products or a category with Vibe Concurrent Test Safety: YugabyteDB ASH Instrumentation (yugabyte/yugabyte-db, 11k stars), Mirage VFS Adapter Authoring (strukto-ai/mirage, 3.7k stars), Golang Patterns (antoniopaya22/go-rest-template, 172 stars) and Rust Async Patterns (diodeme/Gold-Band, 143 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vibe Concurrent Test Safety?

ash1794 (a GitHub user) maintains it in ash1794/vibe-engineering, which has 163 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 7, 2026.

Source: ash1794/vibe-engineering on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.