linearizability-checker
Check linearizability of concurrent data structure implementations
Profile →npx skills add a5c-ai/babysitter --skill linearizability-checker --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Linearizability Checker ## Purpose Provides expert guidance on verifying linearizability of concurrent data structures through testing and proof. ## Capabilities - History linearization algorithms - Linearization point identification - Counterexample generation for violations - Concurrent history visualization - Linearizability proof templates - Testing framework integration ## Usage Guidelines 1. **History Collection**: Record concurrent operation histories 2. **Linearization**: Check if history is linearizable 3. **Counterexample Analysis**: Analyze non-linearizable executions 4. **Proof Construction**: Build linearizability proofs 5. **Testing**: Systematic testing for violations ## Tools/Libraries - LineUp - Wing-Gong algorithm - Lincheck - JCStress
- Purpose
- Capabilities
- Usage Guidelines
- Tools/Libraries
What does the linearizability-checker skill do?
Check linearizability of concurrent data structure implementations
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill linearizability-checker --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.