code-review
3 questions
- AI
How do I connect Claude Code to our self-hosted GitHub Enterprise Server?
An admin connects your GHES instance once via a guided GitHub App manifest flow. After that, developers start sessions with claude --remote in any GHES checkout. Plugin marketplaces on GHES require full git URLs instead of the owner/repo shorthand that only resolves github.com.
- AI
Which Claude code review tool should I actually use?
Three reviewers ship inside Claude: a single-pass local /review, a cloud-sandbox multi-agent /ultrareview, and a GitHub App that runs on every PR. They cost different amounts, run in different places, and answer different questions. Here's the picking guide and the per-tool footguns.
- AI
What does Claude Code look like when you ask it to audit a codebase without editing anything?
A captured `claude --print` session against the demo app, prompted to audit five production-readiness concerns and produce a structured report without modifying any code. Claude used 11 tool calls (1 Glob, 4 Grep, 6 Read), zero edits, finished in 54 seconds, cost 46 cents, and produced a 5-section report with file:line references. The article shows the verbatim audit output, the tool-call census, and a head-to-head comparison against `grep`/`rg` shell scripts for each of the five concerns: TODO scans and missing-test detection are commodity work the agent overpays for, but flagging `new Date()` calls that bypass an injection pattern (vs benign date arithmetic) and reading the dead-letter queue line as 'operational risk' are the kind of semantic judgment that justifies the cost.