Tools for Maintainers

1970 days ago, 0 views.


I created generator-git 4 years ago and it was my first way for automatizing my daily workflow.

In those moments my need was created the necessary scaffold for publishing small npm packages.

My code style evolved with the passage of the time and that was reflected in generator-git as well

Nowadays, it supports different libraries and settings and still, I use it.


automate-release is a recent addition into my workflow.

The idea behind the project is automatize some maintenance stuff associated with your projects for removing as much as possible the human factor.

Let me an example: When I created a project, I usually connect it with greenkeeper to ensure keep the dependencies of the project up to date.

The service will create a new PR every time it detects one of the dependencies of the project has been updated. Then, if your tests pass on green you can conveniently merge the PR a release a new version of your project.

Although this sounds a good idea, if you have a lot of projects, it adds you a lot of noise.

That’s the thing that automate-release solves: Remove me (the human factor) from the equation.

When a PR is integrated and your tests pass on green, automatically a new version of your project will be released with all release things related, this means:

Best of all, automate-release has been designed to make it easy to integrate with a current project, making possible use generator-git and automate-release together.


I recently discovered scritch and I started loving it.

It’s no the first time I see a tool with that purpose. I remember seeing the same from GitHub and Slack engineers, but the tool was written in Ruby and more difficult to extend.

Also, scritch allows you to define scripts in any scripting language, that’s super cool.


I included in this section things that I have not tried yet but what I would use if I had the opportunity.

Kiko Beats

Kiko Beats