verify-branch-commits

To verify every commit on a branch, you can perform an interactive rebase to edit and check each commit individually. This ensures every commit is independently green across compilation, linting, tests, and formatting before creating a PR.

Ensuring a clean git history before a pull request requires verifying that each commit passes the project's full check suite independently. This prevents bad commits from propagating and involves rebasing to amend commits as needed.

Yes, verifying commits independently requires reading project verification commands from specific documentation files. The process discovers the base ref and check commands from AGENTS.md, agent-docs, or CLAUDE.md files to prepare the environment.

Clearing ESLint caches is necessary when checking commits during a rebase to ensure formatting and linting checks run accurately against each specific commit state. This prevents stale cache data from masking formatting or lint errors in individual commits.

Yes, you can fix and amend commits that fail project checks during verification. The process performs an interactive rebase with edit, allowing you to apply fixes and amend commits as needed before continuing to the next commit in the history.