# Questions & Answers

## Q1: For F2: Should the auto-commit include ALL changes in the working directory (git add -A), or only the files that were modified as part of the task?
**Category:** clarification
**Answer:** Only the files updated or added by the task (not git add -A)

## Q2: For F2: If there are no changes to commit (clean working directory), should it silently succeed, or report that there was nothing to commit?
**Category:** edge_case
**Answer:** Silently succeed - no error if nothing to commit

## Q3: For F2: If the git commit fails (e.g., pre-commit hook fails, not a git repo), should the task status still be set to 'done', or should the status change be blocked?
**Category:** edge_case
**Answer:** Blocked - if git commit fails, the status change to 'done' should be blocked

## Q4: For F2: Should the commit message be customizable via config, or is the fixed format 'Complete task: {task-name}' sufficient?
**Category:** clarification
**Answer:** Include task name AND a short description of what has been done (not just the task name)

## Q5: For F2: Should K4000 check if the project is a git repository before attempting to commit, or just let the git command fail naturally?
**Category:** integration
**Answer:** Let it fail naturally - no pre-check for git repository

## Q6: For F2: Should the response include details about what was committed (files changed, commit hash), or just indicate success/failure?
**Category:** clarification
**Answer:** Just indicate success/failure - no detailed commit info needed
