Sc lint version adoption

Skill randlee/sc-lint/.claude/skills/sc-lint-version-adoption

Guide a consuming repository through `sc-lint-version` adoption using the authoritative consumer-integration workflow, existing CLI testability seams, existing simulators or transcripts, and only thin normalization hooks when unavoidable.From its SKILL.md

Install

npx -y skills add randlee/sc-lint --skill sc-lint-version-adoption

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.2 KB, as published. Nobody here has run it

sc-lint-version Adoption

Use this skill when a consuming repository is adopting the planned sc-lint-version interface-checking line.

Required Reference

Always use:

docs/sc-lint/version-adoption.md

That document is the authoritative adoption guide. Do not replace it with spread-out repo notes or ad hoc instructions.

Scope

This skill is narrowly scoped to sc-lint-version adoption only.

It covers:

Rust public API family adoption
CLI interface family adoption
RPC/socket interface family adoption when present
harness, fixture, simulator/transcript, and normalization responsibilities

It does not cover:

general release policy
broad repo process policy
marketplace publication
unrelated sc-lint feature planning

Adoption Rules

Define enabled interface families under [version.families.<family>].
Reuse existing CLI testability surfaces where available.
Reuse existing simulators or transcript fixtures where available.
Keep normalization hooks thin and use them only when unstable values cannot be removed from the canonical artifact generator.
Keep canonical machine-readable artifacts as the source of truth.

Expected Consumer Inputs

The consuming repo should provide:

baseline source definitions for enabled families
CLI fixtures for stable command surfaces
simulator or transcript fixtures for RPC/socket surfaces when present
any repo-local template override config under [reporting.templates.<report_kind>]

Expected Outcome

The consuming repo can run the planned interface-check flow and produce:

canonical interface artifacts
shared HTML/XHTML/JSON reports
hard-fail verdicts for breaking drift