refreshing-history

To squash git history into a single signed commit across multiple repositories, this Skill consolidates fragmented default branches using coordinated per-repo base resolution, dependency refresh, formatting, and pre-push integrity verification. It executes fleet-level baseline cleanups safely via worktree isolation and remote backups.

A fleet-wide baseline reset is the process of coordinating per-repo base resolution to consolidate fragmented project histories into a single signed initial commit. You need it for fleet-level releases or baseline cleanups to ensure history integrity across multiple repositories.

To safely force-push a squashed git baseline, this Skill uses worktree isolation for execution, creates remote backups, and performs pre-push integrity verification before aligning force-pushes across repositories. This controlled workflow prevents data loss during fleet-wide baseline updates.

Dependency refresh and lockfile updates happen before squashing git history into the signed initial commit. The Skill applies format, fix, type checks, and consistency verification prior to push, ensuring the new baseline includes fully updated dependencies and passes code quality passes.

Yes, you can use worktree isolation to protect local branches during a fleet-wide history reset. The Skill isolates operations in separate worktrees and creates remote backups before applying force-push alignment, ensuring safe recovery and preventing unintended branch corruption.