Skip to main content

Adding Codemods To Intuita’s Codemod Registry

· 6 min read
Mohab Sameh

Codemod champions build high-quality and useful codemods that could potentially save hours, weeks, or even months of mundane work from their teammates or the community. But, we have heard that one of their biggest challenges in scaling the impact of their great work is to find those target users at the right time and distribute their codemod to them.

That's why at Intuita, we are building the world’s largest registry of high-quality codemods to address the problem of codemod discoverability and distribution.

Once a codemod is added to Intuita codemod registry, it will automatically get picked up by Intuita IDE extensions (starting with VS Code Extension) and intelligently pushed to all the devs who have the extension installed.

In this article, we explain what would it take to add your codemod to Intuita’s codemod registry. (Estimated Time: 6 Minutes)


  • Before getting into this tutorial, you should first have built a high-quality codemod that passes Intuita’s guidelines and governance and is ready to be shared with the community.

How to Add Codemods to the Registry

Now let’s walk through the steps of adding your amazing new codemod to the registry. To do so, we will go through the following steps:

  1. Creating a branch for your codemod
  2. Familiarizing yourself with the registry’s structure
  3. Adding your codemod files
  4. Creating a PR to merge to the main repository

#1 Creating A Branch For Your Codemod

To have a ready environment, you must first have a local copy of the codemod registry where you can make changes before merging those changes into the main repository.

To do this, all you need to do is:

  1. Fork Intuita’s codemod registry.

  2. Clone your forked repository by using: git clone

  3. Open the codemod registry directory in your code editor of choice.

  4. Then, you’ll need to create a new branch where you will do your changes (adding your codemod to the registry).

    To do this, you can create and switch to a new branch using git checkout -b <branch-name>.

#2 Familiarizing Yourself With the Registry’s Structure

Now that you have a local environment set up, you’re ready to add your codemod files to the registry.

Let’s first take a look at the codemod registry structure.

codemod registry directory structure

You’ll find that the registry has 2 main directories:

  1. Codemods
  2. Sets


The codemods directory will include all the codemod files used available in the registry, categorized by codemod engine > framework/library > version > codemod name.

For example, a codemod named replace-use-router to upgrade Next.js to v13 will be in the following directory:



Sets are a group of related codemods. Usually, sets are used as a group of codemods that collaboratively migrate a codebase from one dependency version to another.

In Intuita’s codemod registry, sets are also used to seamlessly integrate your codemods into the registry with other products available on Intuita’s platform. For example, if you add a codemod to an existing or new set, your codemod will be eloquently integrated into Intuita’s VS Code Extension under an existing or new codemod set.

intutia vs code extension integration with codemod registry

#3 Adding Codemod Files

Now that we have our environment set up, we can begin by creating our codemod files. As of now, the codemod registry supports the JSCodeshift engine due to its popularity. If you want us to support more codemod engines, feel free to submit an issue on the registry with your request.

For this tutorial, we will follow the steps of adding a JSCodeshift codemod. To do so, we will:

  1. Navigate to the /codemods/jscodeshift directory.

  2. Run npm install.

  3. Add the codemod directory. Let’s say, for example, we’re adding a codemod called isiterable-to-iscollection that upgrades Immutable JS to v4. In this case, you should look for (if the set directory exists) or create a directory that’s structured /codemods/jscodeshift/immutable/4/isterable-to-iscollection/. As you can see, we follow the convention of /jscodeshift/library/version/codemod-name whether we’re creating a new codemod or adding a codemod to an existing set.

    adding your codemod directory to the codemod registry

  1. In your new directory, you’ll add an index.ts file and a config.json file (also preferably a test file, read more on testing your codemods here. The index.ts file will include the codemod you’ve written while the config.json file will include metadata about your codemod.

  2. Add our codemod to index.ts. In this example, we’ll be using an existing codemod we’ve written for Immutable JS. At this step, you can add any codemod you’ve written.

    adding your codemod files in index.ts

  1. Now, let’s add some simple metadata about our codemod in the config.json file. In this file, enter the metadata relevant and corresponding to the codemod you’re adding to the registry, including the codemod name, engine, required dependency version, etc.

    adding codemod metadata in config.json

  1. Finally, you should just add your new codemod to a new/existing codemod set. To do this, navigate to the /sets directory, then look for an existing (if applicable) or create a new codemod set. If you’re adding a new codemod set to the registry, create a directory with the following convention: framework_version. In our example, we added a codemod for Immutable JS v4, then we should expect to add our codemod to the immutable_4 set. Now we should simply just add our new codemod directory into the set’s config.json file as shown below.

    adding your codemod in the codemod sets to config.json

#3 Merging Your Codemod Into The Registry

Now your amazing new codemod is fully prepared to be merged into the registry.

To merge your codemod, we’ll start by committing all the changes in your new branch using git add -A && git commit -m "<your message>". Then, we publish the branch using git push --set-upstream origin <branch-name>.

Now, if you open your forked repository, you'll see your new amazing codemod added to your repository.

your new codemod&#39;s branch

All you need to do now is simply open a pull request by clicking “Compare & pull request”.

opening a pull request for your new codemod

And finally, add a description of your added codemod and create the PR.

creating the pull request to add your codemod to the registry

Once you create your PR, it will be shortly reviewed before getting merged into the codemod registry to be integrated into our platform and used by codemod enthusiasts around the world!

Final Words

Intuita's codemod registry is an excellent resource for developers looking to automate code updates. By adding your codemods to the registry, you can help other developers, gain recognition, and improve your codemods. If you have created a useful codemod, we encourage you to share it with the community by adding it to Intuita's registry.