Hey everyone!

Do you remember the massive spreadsheets and hundreds of slack threads you had to keep track off when dealing with log4j? Or the nervousness you had before pushing a EOL language upgrade to your legacy load bearing repository?

We're a team of DevOps/Engineering productivity folks that have built Kaydence to help you orchestrate changes like those across a whole GitHub org instead of one repo at a time!

Here's how Kaydence works:

You show it merged pull requests that have already performed the desired change.
Kaydence extracts the repeatable rules into a playbook. For every rule, Kaydence determines if the change is safely deterministic or needs judgement from our agents and routes it accordingly.
Kaydence then runs that playbook across applicable repos in your GitHub org, creating a PR for each proposed change.

Ready Made Playbooks:

JUnit 4 to 5
Adopt AssertJ fluent assertions
Migrate Apache Commons Lang 2 to 3
Migrate Joda-Time to java.time
Mockito 3 to Mockito 5
Modernize Python string formatting to f-strings
Migrate Enzyme to React Testing Library
Log4J to SLF4J
Migrate javax to jakarta namespace
...Or create your own!

Build Your Own Playbooks:

Kaydence is more than a tech debt tool, it's built to help perform code changes across an entire GitHub org. Here's some ideas of the playbooks you could create

UI Refreshes
- Component library swaps
- Design token changes
Swapping out deprecated internal SDKs or libraries
Enforcing naming logging or import conventions across your whole codebase
Syntax upgrades for Infra

Please give it a whirl and let us know if you have any questions, comments, concerns or violent objections!