okhp3-replit-github-sync

原文涵盖的主题

• okhp3-replit-github-sync
• Scope
• Operating contract
• GitHub capability adapter
• PUSHREJECTED recovery
• Output contract
• About

OverKill Hill P³ · overkillhill.com · github.com/OKHP3 Replit's Git UI can be a useful surface, but it is not the source of truth when the workspace and GitHub disagree. This skill establishes the actual Git state, preserves local work, and uses an explicit integration path instead of retrying a rejected push until it happens to work. It requires a Git checkout with an origin remote. A connected GitHub capability is optional for hosted compare, pull-request, and merge actions; local Git remains authoritative for the Replit working tree. | In scope | Out of scope | |---|---| | Diagnose one Replit checkout against origin | Multi-clone maintenance or branch cleanup | | Commit reviewed local work, pull, and normally push | Force-push, history rewriting, or deleting refs | | Prepare a branch PR and an approved squash merge | Bypassing required review or status checks | | Verify GitHub and local branch alignment after sync | Solving merge conflicts without owner input | 1. Treat the Replit UI error as a symptom, not a diagnosis. Record the repository root, current branch, remotes, current status, and the default base ref before changing anything: Default to origin/main only when that is

这里只展示节选，请以完整原文和当前要求为准。