Kerex it! Install Developer Tools Into Any Repo With One Click

Installing a developer tool should not require cloning a repo, running a CLI, committing files, pushing a branch, and opening a pull request. That is five steps too many when you are evaluating whether a tool is worth adopting.

We built install.kerex.app to eliminate that friction entirely.

The problem with tool installation

Most developer tools have a setup step. Even simple ones. Take Doxla, a tool that turns in-repo markdown into a GitHub Pages documentation site. Setup is one command:

npx doxla init

That creates a GitHub Actions workflow and some config. Simple. But to actually get it into a repository, you still need to:

Clone the repo locally
Run the command
Check what changed
Create a branch
Commit the changes
Push to GitHub
Open a pull request

For someone evaluating Doxla across multiple repos, or for a team lead recommending it to 20 teams, that loop adds up fast. The tool is simple. The process around it is not.

How "Kerex it!" works

Go to install.kerex.app/doxla. Paste a GitHub repository URL. Click "Kerex it!"

A Kerex agent spins up, clones the repository, runs doxla init, commits the result to a new branch, pushes it, and opens a pull request. You get a link to the PR within seconds.

No local environment. No CLI. No account needed. Paste a URL, get a PR.

The PR contains everything you need: the GitHub Actions workflow file, the package.json config, and clear instructions for enabling GitHub Pages. Merge it and your docs site deploys automatically on the next push to main.

What Doxla does

Doxla discovers all .md and .mdx files in your repository and builds a searchable documentation site. It supports:

Automatic file discovery (respects .gitignore patterns)
MDX with custom React components
Full-text search
Syntax highlighting
GitHub Flavored Markdown

The setup PR from Kerex includes:

.github/workflows/doxla.yml — A GitHub Actions workflow that builds and deploys docs to GitHub Pages on every push to main
package.json config — Configuration for custom MDX component support

After merging, your documentation site is live. No ongoing maintenance.

Private repositories

"Kerex it!" works with private repositories too. When you paste a private repo URL, we prompt you to install the Kerex GitHub App. The app requests only the permissions needed: contents write (to push the branch) and pull requests write (to open the PR).

Once installed, the flow is identical. The agent gets a short-lived token scoped to that specific repository, does its work, and the token expires.

What's next

Doxla is the first tool on install.kerex.app, but the architecture is built for more. The site uses path-based routing — /doxla today, /next-tool tomorrow. Any tool with a deterministic setup process can be added.

The pattern is straightforward: if a tool's installation can be scripted, it can be "Kerex-ified". No LLM needed. Just a reliable script, a clean PR, and zero friction for the user.

Try it

Install Doxla on any repository right now:

install.kerex.app/doxla

Paste a URL. Get a PR. Ship docs.