Commit accepted work

A successful implementation does not automatically authorize a Git commit. TCAF treats review, acceptance, commit, tag and push as distinct decisions.

Before committing

Confirm that:

• the Task Contract was approved;
• the final diff matches the authorized scope;
• developer edits are included and preserved;
• relevant checks were executed or clearly marked pending;
• collateral files are not staged accidentally;
• documentation or backlog reconciliation is either included intentionally or handled separately;
• the developer has explicitly accepted the result.

Inspect the working tree:

git status --short
git diff --check
git diff --stat

Review targeted diffs by file rather than relying on one unmanageably large terminal output.

Stage only accepted files

Prefer explicit paths:

git add <accepted-file-1> <accepted-file-2>

Then inspect the staged change:

git diff --cached --check
git diff --cached --stat

Create the commit

Use a message that describes the accepted result:

git commit -m "<clear scoped message>"

The commit must not include unrelated local work, framework files, private tool rules or generated artifacts that were outside the accepted scope.

Push, tag and pull request are separate

Do not push, create a tag, open a pull request or update remote issues merely because a commit exists. Each remote operation requires its own authorization and review of the destination branch and repository state.

Report completion

Return the commit SHA, included scope and checks performed. Do not claim remote publication unless the push or pull request operation actually succeeded.