Makefile command reference
This page summarizes the repository-level Makefile commands that are most relevant for installation, development, testing, docs, and release work.
The commands below are grouped by usage scenario rather than by where they are defined, so you can find the right entrypoint faster during day-to-day work.
| Command | Purpose |
|---|
make init | Install backend and frontend dependencies and enable pre-commit |
make init_db | Create the target database when needed, then initialize schema and exported init data |
make export_db_init_data | Export filtered initialization data from PostgreSQL |
| Command | Purpose |
|---|
make backend | Run the backend in development mode |
make backend_start | Run the backend without dependency sync |
make frontend | Install dependencies and run the frontend in development mode |
make frontendc | Clean-install frontend dependencies and then run the frontend development server |
make run_frontend | Start the frontend development server directly |
make run_cli | Start SkillFlaw quickly with a built static frontend |
make run_clic | Start SkillFlaw after cleaning and rebuilding frontend assets |
make run_cli_debug | Start the CLI in a debug-oriented mode |
make setup_env | Prepare environment variables |
Use make frontend when you want the Vite development server workflow, and use make run_cli / make run_clic when you want a production-style local runtime with built frontend assets served by the backend.
| Command | Purpose |
|---|
make install_frontend | Install frontend dependencies with npm install |
make install_frontendci | Install frontend dependencies with npm ci |
make install_frontendc | Reinstall frontend dependencies after cleaning node_modules and lock artifacts |
make build_frontend | Build frontend static assets and copy them to the backend frontend directory |
make storybook | Start the Storybook development server |
make storybook_build | Build static Storybook assets |
make storybook_network | Start Storybook so it is reachable on the local network |
| Command | Purpose |
|---|
make format | Run backend and frontend formatting |
make format_backend | Format backend code with Ruff |
make format_frontend_check | Run Biome checks on frontend files |
make lint | Run backend type and lint checks |
make codespell | Run spelling checks |
make fix_codespell | Auto-fix spelling issues where possible |
| Command | Purpose |
|---|
make tests | Run the combined test workflow |
make unit_tests | Run backend unit tests |
make integration_tests | Run backend integration tests |
make integration_tests_no_api_keys | Run integration tests that do not need API keys |
make integration_tests_api_keys | Run integration tests that require API keys |
make tests_frontend | Run frontend e2e tests |
make test_frontend | Run frontend Jest unit tests |
make template_tests | Run starter project template tests |
| Command | Purpose |
|---|
make docs_install | Install docs dependencies with repository-local Yarn cache |
make docs | Start the docs development server on port 3030 |
make docs_build | Build production docs output |
make docs_serve | Build and serve docs locally |
| Command | Purpose |
|---|
make build | Build project artifacts |
make patch v=1.0.0b1 | Update the root VERSION file and synchronize consumers |
make sync_version | Synchronize versioned files from the root VERSION |
make check_version_sync | Verify versioned files match the root VERSION |
make publish | Publish packages when the release pipeline is ready |
The Makefile already groups many commands through help targets:
Use these first when you are not sure which entry point belongs to a workflow.
This workflow uses the frontend development server. If you want a production-style local runtime instead, use make run_cli or make run_clic.