Capture technical decisions in your PRs. Find them instantly in your IDE. Never let institutional knowledge walk out the door again.
When a senior developer leaves, their reasoning leaves with them. You're left staring at "weird" code with no explanation.
Decision logic is scattered across Slack, Jira, and old PR comments. Finding the "why" takes hours of archaeology.
Developers avoid refactoring critical code because they don't understand the hidden assumptions. Technical debt piles up.
ContextLock integrates into your GitHub workflow to capture the "why" at the moment of change—and surfaces it exactly when you need it.
Configure rules in .contextlock.yaml to
identify risky changes.
Database migrations? Security updates? Core config changes? ContextLock blocks the PR until a human explanation is provided.
No busywork. Only asks when it matters.
When a PR is flagged, developers explain their decision in seconds:
• Comment
/why Increased timeout to handle slow EU
payment APIs
• Or use the simple web form
Context is automatically linked to the commit SHA and file paths.
/why Increased timeout from 5s to 15s
because EU payment gateways have higher
latency during peak hours. See incident
#4521.
Hover over any line in VS Code to see the "why" behind recent changes.
No more browser tab switching. No more digging through Git history.
Context exactly when you need it.
One-click installation. No code changes required.
Add .contextlock.yaml to define what
changes need context.
ContextLock automatically monitors PRs and asks for context when needed.
Hover in your IDE or search by intent to retrieve context instantly.
Join engineering teams who are building codebases that remember why.