Lockstep for GitHub
Lockstep runs a PR check that catches code drifting from approved decisions, blocking on conflict before it merges, right where your engineers already work.
What Lockstep captures from GitHub
- a PR that contradicts an approved constraint
- decisions made in PR review comments
- an agent shipping code against a prior call
How the loop runs
Lockstep captures the decision from GitHub, routes it to its owner for one-click approval, then briefs every engineer and every AI coding agent before they touch the code, and flags any pull request that drifts from it. See the full pipeline on how it works.
Access & trust
GitHub App with a PR check. Configurable via .lockstep.yml.
Frequently asked questions
- Does the PR check block our merges?
- It warns by default. When you're ready, one line of config (block-on-conflict: true in .lockstep.yml) turns a conflict into a failing check. The judgment stays with your team; Lockstep flags, humans decide.
- What does the check actually compare?
- The surfaces a PR touches (endpoints, capabilities, flows) against the approved decisions that govern them. A change to a governed surface with an open conflict gets an annotation and a labeled PR comment linking both decisions.
- Does Lockstep read our source code?
- The check runs against changed surfaces and the decision record; Lockstep's coordination flow carries decisions and metadata, not your source. The only thing it writes to GitHub is the check result and a labeled comment.
Other integrations