fleet-refreshing-history

To reset git history to a single signed commit, this Skill squashes the main branch while refreshing dependencies and lockfiles. It validates integrity using a worktree-safe workflow, remote backups, and a force-push contract to ensure a clean baseline.

Squashing repository history across a fleet is handled by applying a per-repo baseline reset with safeguards. This process enforces a signed initial commit and dependency refresh, operating safely within worktrees to avoid touching the primary checkout.

Yes, squashing git history to a clean baseline refreshes dependencies and lockfiles simultaneously. The workflow enforces dependency updates and integrity checks before applying the signed commit and executing the force-push contract.

You can use a worktree-safe workflow to reset repo history without affecting your primary checkout. The Skill operates per-repo using worktrees and remote backups to validate integrity before applying the signed commit and force-push contract.

You should not use a force-push contract to reset repo history without remote backups. The Skill mitigizes this constraint by enforcing remote backup validation and worktree safeguards to preserve integrity before applying fleet-wide baseline resets.

Yes, you need a remote backup before squashing git history for a fleet-wide reset. The workflow validates integrity against remote backups and uses worktree isolation to ensure the primary checkout remains untouched during the signed commit process.