One definition of protected
Accepted Unity Version Control state is authoritative. Stale, failed, or raced status results cannot fabricate safety.
Unity Editor tool · Asset Store submission
SBCheckpoint
Asset Store listing submittedA quiet safety instrument for Unity Version Control. SBCheckpoint watches the work between protected states, turns structural risk and exposure into one clear recommendation, and helps you checkpoint before a productive session becomes an expensive recovery.
- Local by design
- Read-only UVCS intelligence
- 257 / 257 EditMode tests
SBCheckpoint
Protection awarenessCurrent stateCHECKPOINT RECOMMENDED
Broad mixed work is building protection debt.
Exposure47m
Changes12
RiskHigh
Debt65
Detected workHydrology + World GenerationProject settings and destructive serialized changes are weighted more heavily than harmless asset volume.
RecommendedCreate a protected checkpoint.
The problem
A timer cannot tell you how dangerous the current change set is.
Five quiet minutes in one script and forty-five minutes touching manifests, settings, serialized assets, and core systems are not the same kind of exposure. SBCheckpoint uses the state of the workspace—not just elapsed time—to decide when a checkpoint is becoming worthwhile.
One meaningful change snapshot
Paths, operations, asset/meta relationships, and destructive changes are normalized into a stable structural view used by every downstream decision.
One recommendation
The window, reminders, notifications, recovery view, and timeline all consume the same checkpoint recommendation instead of calculating competing answers.
What it does
Enough intelligence to be useful. Not enough machinery to become another project manager.
Protection debt
Combines observed exposure, meaningful change breadth, critical project files, destructive operations, and structural risk into a readable sense of how expensive the current unprotected work is becoming.
Risk-aware reminders
Low-risk localized work gets more breathing room. High-risk structural work can escalate sooner. Snooze suppresses delivery—not the underlying severity—and repeated identical nags are avoided.
Recovery orientation
When work is unprotected, SBCheckpoint keeps the last trusted state visible and summarizes what has changed since then so you know where safety actually lies before making another decision.
Smart checkpoint comments
Generates an editable comment suggestion from the stable meaningful-change snapshot and detected work areas, without pretending to semantically understand your source code.
Experiment Mode
Anchors an experiment to a clean, identified baseline and requires strong evidence before automatically considering it resolved. Ambiguous external changes degrade to review instead of pretending certainty.
Flight Recorder
Keeps a bounded local timeline of meaningful protection, risk, reminder, experiment, and recovery transitions—useful context without a cloud dashboard or permanent analytics system.
Deliberately bounded
SBCheckpoint does not replace version control.
Its job is orientation: understand the current workspace well enough to tell you when protection matters and hand you back to the tools that already own source control.
DoesRead
cm status and cm log through a read-only integration.DoesInfer structural work areas, protection debt, risk reasons, and a checkpoint recommendation locally.
Does notCreate a second source-control model, branch automatically, revert files, or silently perform rollback.
Does notUse cloud services, LLMs, semantic source parsing, or telemetry.
Release candidate
Built around explicit truth boundaries and tested against failure cases.
The Asset Store submission was rebuilt from the verified source into a clean release package, then compiled and exercised again in its release layout before upload.
257 / 257EditMode tests passed
0Asset Store Validator failures
Unity 6000.3.8f1release validation environment
Current requirements
Release compatibility
- Unity 6000.3
- Unity Version Control package
- External
cmclient available to the project environment - Identified UVCS workspace for trusted recovery and experiment actions
The current Asset Store submission was validated on Unity 6000.3.8f1. Compatibility is intentionally stated against the build that was actually tested rather than broadened speculatively.
FAQ
What SBCheckpoint is—and what it is not.
Will SBCheckpoint automatically check in my work?
No. Check-in, branch, history, review, and recovery actions stay with Unity Version Control. SBCheckpoint provides the recommendation and context, then hands control back to the version-control workflow.
Is this just a checkpoint timer?
No. Time is one contributor. The recommendation also considers the meaningful change snapshot, structural risk, destructive operations, project-level files, breadth, activity, and the known protected baseline.
Does it upload my code or use AI to read it?
No. The current product is deliberately local, structural, and deterministic. It does not use cloud services, telemetry, LLMs, or semantic source parsing.
When can I buy it?
The Asset Store package has been submitted and its permanent listing URL is reserved. The store page becomes publicly purchasable as soon as Unity publishes the submission.
SBCheckpoint
Protect the useful state before you need to reconstruct it.
SBCheckpoint now has a permanent Unity Asset Store listing. Public purchase begins when Unity publishes the submitted package.
View on Unity Asset StoreListing submitted