/hyperpower:init

/hyperpower:build runs this for you the first time. You only need it on its own to set up a repo without building anything.

First it looks at what you already have: package manager, test runner, type checker, build command, linter and folder layout. Then it asks at most six questions about what it could not work out. It writes hyperpower.yml and writes your project rules based on what it found. Last, it runs every check, such as your tests and type checker, once to confirm each one works.

You can run it again safely. It reads the config that is already there and only fills in the gaps, so you keep your settings.

--refresh writes your project rules again and leaves your config as it is. Use it when the code has changed and the rules no longer match. You usually notice this first in /hyperpower:usage, where checks start failing more often.

--no-interview detects your setup and skips the questions. Use it in CI, or in a repo you are only trying out.

Commit the config file so your team shares it. If one machine needs different settings, put them in hyperpower.local.yml. That file overrides the shared one and stays gitignored.