This project uses Lefthook for managing git hooks to ensure code quality and consistency.

The following checks run on staged files before each commit:

• Database Schema Check: Validates Drizzle schema changes (drizzle-kit check) on db/schema/*.ts
• Prettier: Code formatting (prettier --write)
• Oxlint: Code linting with auto-fix

Pre-push hooks are currently disabled (commented out in lefthook.yml). Uncomment to enable if desired.

If you need to bypass hooks (use sparingly):

# Skip pre-commit hooks
git commit --no-verify

# Skip pre-push hooks
git push --no-verify

You can manually run hooks for testing:

# Run pre-commit checks
pnpx lefthook run pre-commit

# Run pre-push checks
pnpx lefthook run pre-push

Automaspec helps organize test specifications, requirements, and individual tests in a foldered hierarchy with per‑spec status breakdowns. It includes authentication, organizations, and a dashboard UI.

• Next.js 16 (Turbopack) + React 19
• Drizzle ORM with libsql/Turso
• Better Auth (with organizations plugin)
• oRPC + TanStack Query
• Tailwind CSS v4
• Vitest + React Testing Library
• Lefthook, Prettier, Oxlint

• Node.js (active LTS recommended)
• pnpm
• Turso CLI (for turso dev) or another libsql-compatible server

1. Install dependencies

   pnpm install

2. Environment variables

   Copy .env.example to .env.local for local dev and to .env for Docker:

   NEXT_PUBLIC_DATABASE_URL=https://your-cloud-libsql-endpoint
   DATABASE_AUTH_TOKEN=your-cloud-libsql-token
   # Optional: VERCEL_URL=your-vercel-deployment-url
   # Optional: OPENROUTER_API_KEY=...
   # Optional: GEMINI_API_KEY=...

3. Database (local libsql)

Start a local libsql dev server backed by db/local.db:

pnpm db:local

In another terminal, run migrations:

pnpm dbm

Optional: open Drizzle Studio

pnpm dbs

Optional: seed sample data into db/local.db:

sqlite3 db/local.db < sample_data.sql

pnpm dev     # start Next.js (Turbopack)
pnpm build   # build
pnpm start   # run production build

pnpm test             # run unit/component tests
pnpm test --watch     # watch mode
pnpm test tests/components/test-details-panel.test.tsx

Notes:

• Integration tests are skipped by default; to enable, set NEXT_PUBLIC_DATABASE_URL to a reachable libsql endpoint.

The application is fully containerized for reproducible deployments and local development.

• Docker
• Docker Compose

1. Configure Environment: Copy .env.example to .env and fill in the required secrets.

   cp .env.example .env

2. Start Application:

   # For standard development
   docker compose up --build
   
   # For production-optimized profile
   docker compose -f docker-compose.prod.yml up --build -d

3. Stop Application:

   docker compose down

The system uses a multi-stage Alpine-based container to minimize footprint and maximize security.

graph TD
    Client[Browser/Client] -->|port 3000| App[Automaspec App Container]
    App -->|Drizzle ORM| DB[(External libSQL / local.db)]
    
    subgraph "Docker Environment"
        App
    end

Common scripts (see package.json):

• dev, build, start
• test
• db:local, dbg (generate), dbm (migrate), dbs (studio), dbup (generate+migrate)
• lint, format, typecheck (lefthook-driven jobs)

• Changelog: CHANGELOG.md
• Versioning policy: VERSIONING.md
• Release process + release notes template: RELEASING.md

• The app reads database credentials from NEXT_PUBLIC_DATABASE_URL and DATABASE_AUTH_TOKEN (see db/index.ts and drizzle.config.ts).
• Better Auth trusted origins use VERCEL_URL in production if set.