Proof
Ask Vibedata on the pull request and get the commit back
A pull request is already a scoped delegation. On a repository set up for mentions, a reviewer comment reaches the Intent that owns the branch, and the commit comes back to the same review; with no visible Intent, the work arrives as a new pull request.
A reviewer reads a diff, finds a column that should be renamed, and has one place to say so: the pull request. On a repository set up for mentions, a top-level comment can bring the change back to that review.
The reviewer writes @vibedata rename cust_id to customer_id in the orders model in a top-level pull-request comment. When an active Intent already owns the branch, that Intent makes the change, pushes it and replies with the commit id. When none is visible, or only a draft exists, Vibedata creates one and the work arrives as a new pull request linked from the original.123
The pull request is already a scoped delegation
A pull request carries the diff, the branch, the review and the person who owns the decision. A change request is a delegation with a known target and a named judge, and GitHub's review flow is built around that conversation on the diff.4
What was missing was the work. The reviewer could describe the change on the pull request, then had to open Vibedata, find the Intent behind the branch and start a second conversation to get it made. The request and the execution lived in different places, so the reviewer carried the context across.
Data work makes that split expensive. The reviewer of a data change carries the model and the tests in their head, along with the slice of data they ran them on, and rebuilding that context in another tool is the part that gets skipped. A comment on the diff arrives with that context already loaded.
Putting the request on the pull request keeps the review where it is. When an active Intent already owns the branch, the commit arrives on the branch the reviewer is already reading, and the reviewer judges it in the same place they asked for it.
The comment becomes a commit when an active Intent owns the branch
The trigger is a top-level pull-request comment that contains @vibedata as a whole word.1 The workflow checks that the commenter can write to the repository: write, maintain or admin. A bot comment, a quoted line, @vibedata-test or me@vibedata.com does not start a request.
The workflow starts a short mention Intent. That Intent runs a skill that looks for the active Intent owning the pull request's branch and, when exactly one exists, opens it and sends the comment unchanged.2 The skill never edits files, commits or pushes.
The skill treats an Intent as busy while someone holds its edit lease or a turn is running. It checks once a minute and waits up to 15 minutes before it replies that someone is working there.2 Two mentions that open an idle Intent at the same moment can join one turn, a race the design accepts.1
The work Intent does the change. It runs its usual checks, commits and pushes to the pull request's branch, then replies with a brief summary and the commit id.123
With no visible Intent, the work arrives as a new pull request
When no Intent is visible on the branch, or only a draft exists, the skill creates one and sends it the request with the pull request's link.2 A created Intent has its own branch, so its push lands there and the work arrives as a new pull request linked from the original.
That is a different review loop. The request starts on the original diff, and the result is judged on a second pull request. The design records working directly on an existing branch as an open question.1
The skill takes exactly one active Intent first. Several active Intents, or none active and one archived, completed or closed, stop the request with a reply instead of a change.2 It creates a new Intent only when none is visible or the only one is a draft.
The fork decides which review carries the result, or whether the request stops.
The Intent that owns the branch carries the context it has accumulated
A fair objection is that this is another chat surface. A local coding agent in the pull-request checkout can make the same edit, and the reviewer still has to judge the result.
The difference is where the work runs. The request goes to the active Intent that already owns the branch, so it arrives with the context that Intent has accumulated: the conversation and the earlier changes on the branch. Reusing the Intent avoids transferring its accumulated conversation.
That matters because the change is usually not the whole job. A rename still has to hold in the model and pass the tests before a reviewer can accept it. The forwarded request asks the Intent to run its usual checks before it commits and pushes, and the reply names the change and the commit id. It does not certify that those checks passed; the reviewer reads that in the review itself.
The productivity gain is the same team shipping more when the work and its review stay in one loop, and each accepted review leaves less for the next one to re-explain.
The repository token sets the boundary
The sharper objection is the repository token. One token per repository means the agent acts as the token owner, whoever wrote the comment. That is the boundary the design chooses.
Every Vibedata call uses the repository's Personal Access Token, so the mention Intent, the work Intent, the audit trail and every Vibedata permission check belong to that owner.1 The commenter's login is carried into the forwarded request, so the work Intent shows who asked.12
Only repository writers can trigger. The agent's reach is bounded by the token owner's Vibedata permissions, by branch protection and by the outer CI loop. Choose a Domain owner as the token owner, because list_intents shows a Domain contributor only the Intents shared with them.1
Setup is a one-time repository task
The workflow is part of the CI bundle. A repository whose CI predates mentions does nothing on a mention until an Intent repairs the CI install.1 Once the workflow is present, an install that is not fully configured replies once with the missing step: the environment's branch rule, the token, or Sync's variables.1
A new repository gets the workflow when /install-ci runs, and an existing install gets it by asking an Intent to repair the CI install.1 The rest is repository administration.
- The mention workflow is part of the CI bundle;
/install-ciinstalls it on a new repository. - The
vibedata-mentionenvironment limits the token secret to runs from the default branch. - The
VIBEDATA_PATsecret holds one Vibedata token per repository; a Domain owner is the recommended owner. - GitHub Actions Sync writes
VD_CI_STUDIO_URLandVD_CI_DOMAIN_ID, so the runner can reach the install and its Domain. - Default-branch protection requires a pull request before merging, with no bypass for the GitHub App.
After the setup, a writer's comment is the whole interface.
The test is a small request on a pull request you already have open
Pick an open pull request with a small, unambiguous request, and put it in a top-level comment: @vibedata add a description to the orders model.
If the branch already has an active Intent, judge the commit in the review where you asked. If none is visible or only a draft exists, Vibedata creates one and the reply tells you where the work is.2
Which open pull request would your team try first?
References
Footnotes
-
The GitHub mention design in
accelerate-data/studio,docs/design/github-mentions/README.mdat8cfc1aa, read recently: the@vibedatawhole-word match, thewrite/maintain/admincheck, the mention Intent and the work Intent, the repository token model, the reply that names the commit, the per-repository setup and its limits, and the new-Intent branch that opens a new pull request. The implementation is in thevibedata-mentionworkflow and runner inaccelerate-data/domain-cicdat1c124b8, read recently. ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9 ↩10 ↩11 -
The
handling-vibedata-mentionsskill inaccelerate-data/vibedata-data-engineering,plugins/vibedata-data-engineering/skills/handling-vibedata-mentions/, at9e3aa1a, read recently: it forwards the comment unchanged, finds or creates the Intent that owns the branch, waits while the Intent is busy, never edits files, commits or pushes, and posts the replies. A created Intent has its own branch and opens its own pull request. ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 -
In a recent run on a test repository, recorded in
accelerate-data/studio's GitHub mentions implementation plan at8cfc1aa, Task 9, we watched a writer's mention produce a forwarded reply, a commit on the branch carrying the Vibedata co-author trailer and a done reply naming the commit. A later mention with no Intent visible created a new Intent, and its work arrived as a new pull request. ↩ ↩2 -
GitHub Docs, "Reviewing proposed changes in a pull request", on the pull request as the place where the diff, the comments and the review already sit. https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request ↩
Get the weekly roundup by email
One email a week: what got easier in Vibedata, a recipe to try yourself, and where data engineering is heading.
Or follow the RSS feed.
