See which consumers need another check.
Traverse an explicit reverse-dependency manifest from a changed file to the tests, documentation, packages, and other consumers that require re-verification.
How it actually works
Exactly what it does — and when.
The manifest connects the schema to its parser tests, API guide, package builder, and consumer fixture. Change Impact returns that focused recheck list and leaves an unregistered example as a gap for the maintainer to map.
Use it to…
Real ways people put Genesis Change Impact to work.
Change a shared library
Trace the file to its declared tests and package consumers.
Update an API
Find the documentation and examples declared against that interface.
Rebuild a download
Surface the release archive and consumer verification that depend on changed source.
- A shared edit reaches several consumers
- Only the changed file is checked
- Unmapped dependencies look green
- Turn a shared-file change into a focused recheck list
- Keep unmapped paths visible as gaps
- Preserve unaffected branches instead of reopening everything
What's inside
Who it's for
Monorepo maintainers
need targeted re-verification across shared code
Documentation owners
need API changes to reach their guides
Release engineers
need downloadable consumers included in impact checks
Questions, answered
Ready to put Genesis Change Impact to work?
Instant download · one-time price · own forever · all sales final