git-sync-workflow

Configuring git hooks like pre-commit and pre-push speeds up CI by validating changes locally before they reach the remote server. This skill applies these hook recommendations to establish guardrails around hook execution and prevent broken builds.

Keeping git history linear during team collaboration is best achieved by pulling with rebase before pushing. This skill enforces pull before push with rebase to maintain a streamlined history and predictable merges across typical workflows.

Safely force pushing to a remote branch with upstream tracking requires using --force-with-lease to prevent overwriting remote changes. This skill implements safe pushing with upstream tracking and applies --force-with-lease when necessary.

Use rebasing instead of merging in your git workflow when you need to resolve merge conflicts and maintain a streamlined, linear history. This skill applies best-practice rebasing to enforce safe history and predictable merges during daily syncs.

You can use this git workflow without external dependencies because it operates with an empty dependency list. It applies best practices for pulling with rebase, pushing with upstream tracking, and configuring hooks directly within your environment.

Git force push fails without upstream tracking because the remote branch relationship is undefined, making safe overwrites impossible. This skill mitigates this by enforcing safe pushing with upstream tracking and applying --force-with-lease when necessary.