Sherlog installs in 30 seconds. On every pull request it posts velocity, gap analysis, and blast radius — right in the PR thread, where your team already works.
Sherlog uses GitHub's webhook system. No CI tokens to rotate, no YAML pipelines to maintain, no new dashboards to check.
Authorize Sherlog on one repo or your entire org. It needs read access to code and write access to PR comments.
Sherlog clones the PR head, runs the full doctor pipeline — velocity, gaps, blast radius — and posts the results as a comment.
.sherlog.yml for ProDrop a two-line config file into the repo with your Pro license key. The next PR gets the full diagnostic — gap list, per-check table, detailed rationale.
Sherlog edits its own comment — no spam. Each force-push or new commit triggers a fresh analysis on the same comment thread.
Toggle between the free snapshot and the full Pro diagnostic. This is real output — not a mockup.
Sherlog is built to produce repo diagnostics that coding assistants can inspect, challenge, and use. Install the free tier, paste the output into Cursor, Claude Code, Copilot Chat, or your IDE assistant, and ask whether the findings hold up against the code.
Every Sherlog PR comment also ships with a hidden <details> block addressed directly to coding assistants — the same audit prompt, embedded where your AI will already see it. The prompt is adversarial by default: if the findings are weak in your repo, your AI is invited to say so plainly.
Sherlog doesn't ask you to trust another dashboard. It gives your AI assistant better evidence to argue with.
The free tier shows you something is wrong. Pro tells you exactly what and why — before it merges.
.sherlog.yml — no CI setup
After checkout you receive a license key by email. Drop it in a .sherlog.yml at the repo root. The next PR comment upgrades automatically.
Sherlog clones the PR head branch (read-only) to run the doctor analysis. It reads commit history, file structure, and source layout. It does not store your code — the clone is discarded after each analysis. See the privacy policy for the full breakdown.
After subscribing, you receive a license key by email. Add a .sherlog.yml to your repo root:license_key: SHLG-XXXX-XXXX-XXXX
Sherlog reads this file from the PR head on every run. The key never leaves your repo — it is validated server-side against our allow-list and is never echoed in comments or logs.
Yes. One Pro license covers all repos in the GitHub App installation. Add the same .sherlog.yml to each repo, or manage it at the org level if you're on an org installation.
Yes. Sherlog requests the contents: read permission during installation, which covers both public and private repos. Your code is cloned over the standard GitHub API using a temporary installation token.
Your key is removed from the allow-list at the end of the billing period. Sherlog continues to run on your PRs in free-tier mode — you keep the health summary and velocity snapshot, you just lose the full gap list and diagnostics table. No disruption to your CI pipeline.
Yes — the same doctor engine. The GitHub App is the managed, always-on version: you don't install or update anything locally, and it runs automatically on every PR. The CLI and VS Code extension are still available for local dev use.