Quickstart
Set up gspot yourself, or give one prompt to your coding agent.
Set up gspot
Section titled “Set up gspot”Run these commands in the root of your repository.
npm i -D -E @gspothq/clinpx gspot initnpx gspot installpnpm add -D -E @gspothq/clipnpm exec gspot initpnpm exec gspot installyarn add -D -E @gspothq/cliyarn exec gspot inityarn exec gspot installbun add -d -E @gspothq/clibunx gspot initbunx gspot installmise use --pin node@24 --tool-option allow_low_downloads=true npm:@gspothq/climise exec -- gspot initmise exec -- gspot install- The first command adds gspot to the project, pinned to one version.
gspot initshows a plan. When you accept it, gspot writesgspot.toml, the tool files,AGENTS.mdand the rules, the Git hooks, and the CI workflow, and deletes the tool files it replaces. Read the plan first.gspot installinstalls the pinned tools and turns on the hooks. From then on, every commit runs the checks.
gspot starts at level recommended. For stricter checks, run gspot set level all, then gspot install again.
Levels says what each level checks.
Paste this prompt into Claude Code, Codex, Cursor, or another coding agent that can run commands.
Set up gspot in a repository. Run curl -fsSL https://generativespotting.com/llms.txt and follow its steps.The agent then:
- Adds
@gspothq/cliwith the package manager of your repository, or pins it with mise. - Runs
gspot init --dry-run, shows you the plan, and asks which level you want. It writes the plan only after you agree. - Runs
gspot installandgspot check, and shows you the result. - Reads
AGENTS.mdand the agent rules before it writes more code.
After you install
Section titled “After you install”Commit gspot.toml and the files that gspot wrote; Generated files lists them. Then
commit as usual. The pre-commit hook checks the staged files and stops the commit when a check fails. Run
gspot check to check every file, including work that you did not commit.