Release tooling built with
determinism and restraint.
Proprietary CLI tools for teams where release correctness is a requirement, not a convention. Explicit interfaces. Traceable history. Bounded purpose.
AutoChangelog
Changelogs should be as reliable as the software they document.
AutoChangelog validates and enforces Keep a Changelog structure on CHANGELOG.md files. Run as a pipeline gate, a non-zero exit means the release does not proceed.
Malformed entries, out-of-sequence versions, and missing Unreleased sections are caught before they reach a release artifact. The changelog is a release-critical file.
- Validates Keep a Changelog format compliance on every run
- Enforces release sequencing — no version regressions or duplicate entries
- Manages the Unreleased section through each release cycle
- Machine-readable output with distinct exit codes — no manual inspection required in CI
autochangelog init
autochangelog add --section Added --message "Initial release"
autochangelog release --version 1.0.0 --date 2026-04-14
autochangelog validate CHANGELOG.md AutoVersion
Version authority from package.json. Read, validate, and bump without ambiguity or parallel version files.
BuildStamp
Provenance attached to every build artifact. Immutable evidence downstream of version authority, not metadata theater.
AutoVersion and BuildStamp product pages are forthcoming. Direct inquiries welcome at contact@solcogito.com.
AutoChangelog — plans from $29.99 / month. See plans on pkgstore →
Private software for internal operations. See how we work →