Hacker News
Show HN: Continue – Source-controlled AI checks, enforceable in CI
Hacker News · Feb 17, 2026 · Collected from RSS
Summary
We now write most of our code with agents. For a while, PRs piled up, causing review fatigue, and we had this sinking feeling that standards were slipping. Consistency is tough at this volume. I’m sharing the solution we found, which has become our main product. Continue (https://docs.continue.dev) runs AI checks on every PR. Each check is a source-controlled markdown file in `.continue/checks/` that shows up as a GitHub status check. They run as full agents, not just reading the diff, but able to read/write files, run bash commands, and use a browser. If it finds something, the check fails with one click to accept a diff. Otherwise, it passes silently. Here’s one of ours: .continue/checks/metrics-integrity.md --- name: Metrics Integrity description: Detects changes that could inflate, deflate, or corrupt metrics (session counts, event accuracy, etc.) --- Review this PR for changes that could unintentionally distort metrics. These bugs are insidious because they corrupt dashboards without triggering errors or test failures. Check for: - "Find or create" patterns where the "find" is too narrow, causing entity duplication (e.g. querying only active sessions, missing completed ones, so every new commit creates a duplicate) - Event tracking calls inside loops or retry paths that fire multiple times per logical action - Refactors that accidentally remove or move tracking calls to a path that executes with different frequency Key files: anything containing `posthog.capture` or `trackEvent` --- To get started, paste this into Claude Code or your coding agent of choice: Help me write checks for this codebase: https://continue.dev/walkthrough - Explore the codebase and use the `gh` CLI to read past review comments - Write checks to `.continue/checks/` - Optionally, show you how to run them locally or in CI Would love your feedback! Comments URL: https://news.ycombinator.com/item?id=47049848 Points: 8 # Comments: 1
Full Article
Continue runs AI checks on every pull request. Each check is a markdown file in your repo that shows up as a GitHub status check — green if the code looks good, red with a suggested fix if not. Quickstart Paste this into Claude Code (or any coding agent): Help me write checks for this codebase: https://continue.dev/walkthrough This walks you through creating your first checks, connecting GitHub, and seeing them run on a PR. See Write Your First Check for the full guide. How it works You define checks as markdown files in .continue/checks/. Each file has a name, a description, and a prompt that tells the AI what to look for. --- name: Security Review description: Flag hardcoded secrets and missing input validation --- Review this pull request for security issues. Flag as failing if any of these are true: - Hardcoded API keys, tokens, or passwords in source files - New API endpoints without input validation - SQL queries built with string concatenation - Sensitive data logged to stdout If none of these issues are found, pass the check. When a PR is opened, Continue runs each check against the diff and reports the result as a GitHub status check. If a check fails, it suggests a fix you can accept or reject directly from GitHub.
Share this story