Let your agent set you up

# Install Codifix

You are installing Codifix for me. Work in the terminal, explain before using sudo, and stop before destructive changes.

## Goal

Install Codifix completely on this machine and configure it for the project I choose.

Repository: https://github.com/3vilM33pl3/codifix
GitHub Releases: https://github.com/3vilM33pl3/codifix/releases

## Rules

- Detect whether this is Linux/Debian-style or macOS.
- Do not invent secrets.
- PostgreSQL is required. Before running `codifix wizard --global`, find an existing database URL or ask me whether to use an existing/hosted PostgreSQL database or create a local one.
- If creating a local PostgreSQL database, create a dedicated database and user named `codifix` unless I ask for different names.
- Do not invent the database password; ask me for it or generate one only after confirming that is OK.
- Make sure the PostgreSQL server has pgvector installed and that the target database has `CREATE EXTENSION IF NOT EXISTS vector;` applied.
- Verify PostgreSQL with `psql "$DATABASE_URL" -c "SELECT 1;"` and verify pgvector with `psql "$DATABASE_URL" -c "SELECT extversion FROM pg_extension WHERE extname = 'vector';"` before configuring Codifix.
- Ask me for optional LLM or embedding API keys only if I want scan or semantic retrieval.
- Make sure Go is available on PATH so repo-local Codifix skills can run.
- Run health checks before saying the install is done.

## Linux / Debian path

1. Download the latest Codifix `.deb` from GitHub Releases.
2. Install the package for the machine architecture:
   - x86_64: `sudo dpkg -i codifix_<version>_amd64.deb`
   - arm64 / Raspberry Pi 4 or 5 with a 64-bit OS: `sudo dpkg -i codifix_<version>_arm64.deb`
3. Prepare PostgreSQL before configuring Codifix:
   - If using a hosted/existing database, verify that it accepts connections from this machine and supports pgvector.
   - If creating a local database, install PostgreSQL and the matching pgvector package for the server major version, for example `postgresql-16-pgvector` when the server is PostgreSQL 16.
   - Create or receive a database URL such as `postgres://codifix:<password>@127.0.0.1:5432/codifix`.
   - Run `psql "$DATABASE_URL" -c "CREATE EXTENSION IF NOT EXISTS vector;"`.
   - Verify with `psql "$DATABASE_URL" -c "SELECT 1;"` and `psql "$DATABASE_URL" -c "SELECT extversion FROM pg_extension WHERE extname = 'vector';"`.
4. Run `codifix wizard --global` and configure the verified database URL and optional LLM/embedding settings.
5. Go to my target project directory.
6. Run `codifix wizard --dry-run`, then `codifix wizard` for repo-local setup.
7. Start the backend with `sudo systemctl enable --now codifix.service`.
8. Run `codifix doctor`, `codifix health`, and then open `codifix tui`.

## macOS path

1. Run `brew tap 3vilM33pl3/codifix https://github.com/3vilM33pl3/codifix`.
2. Run `brew install 3vilM33pl3/codifix/codifix`.
3. Prepare PostgreSQL before configuring Codifix:
   - If using a hosted/existing database, verify that it accepts connections from this machine and supports pgvector.
   - If creating a local database, use Homebrew PostgreSQL and pgvector, then create a dedicated `codifix` database and user.
   - Create or receive a database URL such as `postgres://codifix:<password>@127.0.0.1:5432/codifix`.
   - Run `psql "$DATABASE_URL" -c "CREATE EXTENSION IF NOT EXISTS vector;"`.
   - Verify with `psql "$DATABASE_URL" -c "SELECT 1;"` and `psql "$DATABASE_URL" -c "SELECT extversion FROM pg_extension WHERE extname = 'vector';"`.
4. Run `codifix wizard --global` and configure the verified database URL and optional LLM/embedding settings.
5. Go to my target project directory.
6. Run `codifix wizard --dry-run`, then `codifix wizard` for repo-local setup.
7. Start the backend with `codifix service enable`.
8. Run `codifix doctor`, `codifix health`, and then open `codifix tui`.

## Finish

Report what was installed, where the config files are, whether the service is healthy, and what I should run next.

# Initialize Repository For Codifix

You are configuring an existing project for Codifix. Work in the terminal, explain before changing files, and stop before destructive changes.

## Goal

Create or refresh repo-local Codifix configuration so agents can write, query, and curate project memory safely.

## Rules

- Work in the target project directory I give you.
- Do not install the system package; this prompt is only for repo-local Codifix setup.
- Do not create or reinitialize git history.
- Do not delete existing `.codifix/`, `.agents/`, or Codifix config files.
- If `.codifix/project.toml`, legacy `.codifix/config.toml`, `.agents/codifix.toml`, or `.agents/skills/` already exist, inspect them and preserve local customizations.
- Ask me before overwriting files, rotating credentials, importing history, or running a write operation that was not previewed.
- Make sure the shared backend is configured and healthy before saying setup is done.
- Make sure Go is available on `PATH` because repo-local Codifix skills use the Go helper.

## Steps

1. Run `codifix health` and `codifix doctor`.
2. Run `codifix wizard --dry-run` in the target project to preview setup.
3. Run `codifix wizard` to create or refresh the user-local project config, `.codifix/project.toml`, and `.agents/` Codifix files.
4. Run `codifix doctor` again.
5. If commit history should be available as evidence, run `codifix commits sync --project <project-slug> --dry-run`, then run it for real only if the preview looks correct.
6. If an initial scan is wanted, run `codifix scan --project <project-slug> --dry-run`, then run it for real only after I approve the preview.
7. Open `codifix tui` or report the project slug and next commands.

## Finish

Report which repo-local files were created or preserved, the project slug, backend health, and any follow-up actions.