setup

Setup

Detect this project's stack and fill in the Project context block in AGENTS.md.

Run this once, right after installing. Everything else in the workflow reads the Project context block — /test needs to know your test runner, /commit needs your lint command, /ship needs your base branch. Left blank, every command guesses, and a guess that's wrong is worse than a question.

Input: none. Anything you pass is treated as a hint (e.g. pnpm, vitest, deploys from develop).

---

Step 1 — Detect

Look at what's actually in the repo. Don't ask about anything you can read:

ls package.json pnpm-lock.yaml yarn.lock package-lock.json bun.lockb 2>/dev/null
ls pyproject.toml requirements.txt go.mod Cargo.toml Gemfile composer.json 2>/dev/null
ls nx.json turbo.json lerna.json pnpm-workspace.yaml 2>/dev/null   # monorepo?
ls Makefile Dockerfile docker-compose.yml 2>/dev/null

# scripts are the source of truth for how this project is actually run
[ -f package.json ] && python3 -c "import json;print(json.load(open('package.json')).get('scripts',{}))"

# base branch, as configured rather than assumed
git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's|.*/||'
git rev-parse --abbrev-ref HEAD

# existing test files tell you the convention better than the config does
git ls-files | grep -iE '(\.test\.|\.spec\.|_test\.|/__tests__/|/tests?/)' | head -10

The lockfile decides the package manager — pnpm-lock.yaml means pnpm, not npm, regardless of what the README says.

Step 2 — Fill in the block

Rewrite the Project context section of AGENTS.md with what you found:

Stack:        TypeScript + Next.js 15, React 19
Install:      pnpm install
Run / dev:    pnpm dev
Test:         pnpm test          (vitest)
Lint/format:  pnpm lint && pnpm format
Build:        pnpm build
Base branch:  main

Rules:

• Only write commands you verified exist — a script in package.json, a Makefile target, a documented CLI. Never invent pnpm test because it's conventional.
• If something genuinely isn't there (no linter, no tests yet), write none rather than a plausible-looking command. Test: none — no test setup yet is useful information; a command that errors is not.
• Monorepo → prefer the affected-scope form (nx affected -t test --base=origin/main). See docs/nx.md.