A Claude Code CI step is configured to automatically commit formatting fixes to the PR branch using GITHUB_TOKEN. The step runs on every push. Is this configuration safe?
Answer: No — the step has write access to the repository and can commit code without human review, which creates a blast radius if Claude makes an unintended change
Auto-committing code from a CI step that runs on every push means Claude Code can add commits to the PR branch without any human review. Even for formatting, if Claude makes an unintended change (wrong file, incorrect fix, unexpected scope), it gets committed automatically and becomes part of the PR diff without the developer noticing. This is a mutation step that should require either a human approval gate or careful scope limitation (e.g., only allow changes to files matching *.{ts,js,py} that fail the linter). GITHUB_TOKEN being scoped (A) doesn't prevent unintended commits within its scope. Auto-commit patterns in CI carry inherent risk (C). Claude Code can commit in CI with the right tools (D).