Let a checked change be committed
3 minute read · Projects & Git
Automatic commit is an explicit opt-in for a checked agent change. Use it when the project has meaningful tests and you want a successful task recorded as a local Git commit.
- Prepare the conditions
- Understand a skipped commit
- Prepare the project before enabling it
- Read a skipped-commit result
- Keep the permission scope clear
Prepare the conditions
Start from a clean checkout. Configure the project’s test command and make sure it checks the behavior you care about. Enable automatic commit for the intended work; it is off by default for scheduled tasks and is not granted merely by delegation.
Vortex requires passing configured tests, the same branch and HEAD, and the same tested file snapshot at commit time. If another task changes the files after the checks, the proof no longer applies.
Understand a skipped commit
A dirty starting tree, missing checks, failed tests or changed Git state can prevent automatic commit. Vortex leaves the changes for review and reports why it skipped. Do not interpret that as a lost edit or retry by discarding the work.
Review the diff and make a manual commit when appropriate. Automatic commit never implies a push or deployment. Use project checks to decide what evidence a task needs.
Prepare the project before enabling it
Automatic commit is an explicit opt-in. First identify the project's real test command and confirm that it checks the behavior you care about. Start the task from a clean checkout so Vortex can distinguish that run's change from unrelated work. Check the current branch and HEAD before the run begins.
The commit is allowed only when the configured checks pass, the branch and HEAD remain unchanged, and the file snapshot to be committed is the same one that was tested. If another process changes a file after tests, the earlier passing result does not validate the new snapshot. Vortex should skip the automatic commit and explain why.
Read a skipped-commit result
| Reason | Appropriate next step |
|---|---|
| Checkout was already dirty | Review the existing and new changes together; use a deliberate manual commit if appropriate. |
| No configured tests | Configure meaningful project checks before relying on automatic commit. |
| A check failed | Read the failure, fix the cause and validate the corrected work. |
| Branch or HEAD changed | Inspect the checkout transition and confirm where the change belongs. |
| Files changed after validation | Review and test the current snapshot before committing it. |
Skipping automatic commit must preserve the user's files for review. It is not permission to reset the checkout or delete changes until the guard passes.
Keep the permission scope clear
A linked delegated task disables automatic commit rather than inheriting permission to mutate Git. Local scheduled work also starts with automatic commit off unless you explicitly opt in. Manual commit remains a separate user action. Neither mode includes push, publish branch, tags or deployment; ask for those exact operations when you intend them. Git review explains how to inspect the resulting commit.