Skip to content
TCAFTask-Contract AI Development Framework
TCAF 0.3.3

Git operations and safety

Keep inspection, commit, push, tag, reset and cleanup actions under explicit developer authorization.

Content: completeWorkflow: not supported

TCAF may describe safe Git procedures, but it does not treat repository-changing Git operations as implicit consequences of a successful task.

Read-only inspection

The agent may use approved read-only commands to understand current state, for example:

git status --short
git diff --check
git diff --stat
git diff -- <path>
git diff --cached --stat
git log --oneline -n 10

Git status and diff show current changes; they do not prove who created them. Do not attribute uncertain changes to the developer or agent without evidence.

Commit

A commit requires:

  • accepted implementation;
  • explicit authorization;
  • review of included paths;
  • targeted staging;
  • a message describing one logical change.

Do not use broad staging when unrelated local work may exist.

Push, tag and pull request

These are separate remote operations. Before each one, confirm repository, branch, destination and exact scope. A local commit does not authorize any of them.

Destructive operations

Never run or recommend automatic use of destructive commands against uncertain work, including:

git reset --hard
git clean -fd
git checkout -- <path>
git restore <path>

A destructive restore may be appropriate only when the developer identifies the exact known work to discard and authorizes that action explicitly.

Developer and concurrent changes

The current working tree is authoritative. Before continuing after a pause or manual edit:

  1. inspect current status;
  2. re-read relevant files;
  3. preserve unrelated work;
  4. distinguish compatible, overlapping and contradictory changes;
  5. ask when overlap cannot be interpreted safely.

Do not use reset, checkout or file replacement to return to the agent’s previous state.

Unsupported automation

The workflow status is not-supported because TCAF does not automatically authorize commit, push, tag, branch deletion, reset, clean or remote issue updates. These remain explicit developer-controlled operations even when an adapter technically has permission to perform them.