Using with Claude Code
Run Nitpick conversationally inside Claude Code, instead of via the CLI.
Nitpick works with or without Claude Code. This guide covers the Claude Code integration.
Two ways Claude Code fits in
1. As a provider
llm:
provider: claude-code
Nitpick’s CLI runs normally, but LLM calls route through the claude subprocess (instead of direct API). Use when you want billing to route through your Claude Code account.
Requires @anthropic-ai/claude-code installed globally.
2. As the runtime
Install the bundled skills into ~/.claude/skills/:
./scripts/install-skill.sh
Symlinks skills/nitpick/, skills/prd-e2e-orchestrator/, and skills/multi-role-e2e/ into your Claude Code skills directory.
Then:
claude
And ask conversationally:
“I need to test my app at https://app.example.com. I changed the task form. Credentials: admin@example.com / pass123.”
Claude will:
- Activate the nitpick skill
- Run the crawler (via Bash tool)
- Propose affected pages (in chat)
- Wait for your confirmation
- Delegate per-page testing via the
Agenttool to subagents running prd-e2e-orchestrator - Present Phase 3.5 summaries in chat for approval
- Show you the unified report inline
No CLI. All interaction is conversational.
When to use which
| CLI / HTTP API | Claude Code (runtime) | |
|---|---|---|
| Interface | Terminal / REST | Conversational |
| Config | nitpick.yaml + .env | Inline in chat if you want |
| LLM | Your API key | Your Claude Code session |
| Parallelism | Node subprocess model | Agent tool (subagents) |
| Best for | CI, scripts, scheduled | Ad-hoc investigation |
Uninstalling the skill
rm ~/.claude/skills/{nitpick,prd-e2e-orchestrator,multi-role-e2e}