clawdie/clawdie-ai
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
clawdie-ai/.agent/skills/git-push-upstream/SKILL.md
Operator & Codex 771e19e1c7 Drop FreeBSD 14 support (Sam & Claude) 
Require the tracked FreeBSD 15.x line during install and environment checks, and align docs and skill compatibility metadata with 15.x only.

---
Build: pass
Tests: pass — 37 passed (2 files)

---
Build: pass | Tests: pass — 2363 passed (701 files)
2026-05-10 16:31:40 +02:00

1.9 KiB
Raw Blame History

name description compatibility invoke_patterns estimated_tokens
git-push-upstream Push current branch to Codeberg upstream — explicit one-way sync from local to public mirror FreeBSD 15.x
Push to Codeberg
Push to upstream
Sync to Codeberg
Publish to upstream
Backup to upstream
200-400

git-push-upstream

Push the current branch from the local git jail to the Codeberg upstream mirror. This is an explicit, one-way sync — it does not run automatically.

Architecture

Agent working copy → local (git jail) → upstream (Codeberg)

All agent work targets local (the git jail) by default. This skill is for when the operator explicitly wants commits on Codeberg.

Remotes

Name URL Purpose
local $GIT_LOCAL_URL (git jail) Default push/pull
upstream $REMOTE_GIT_URL (Codeberg) Explicit sync only

Usage

cd $AGENT_REPO_DIR

# Ensure local is up to date first
git push local HEAD

# Push current branch to upstream
git push upstream HEAD

# Push all tags
git push upstream --tags

# Verify
git ls-remote upstream HEAD
git rev-parse HEAD

Safety Rules

  • Always push to local first, then to upstream
  • Never force-push to upstream without explicit operator instruction
  • Check git log --oneline local..upstream/main to see what will be pushed
  • If upstream is ahead, pull and rebase first

When to Use

  • Operator explicitly requests "push to Codeberg"
  • After a release tag is created (usually paired with git-release-tag)
  • Periodic backup of important work

Escalate If

  • Push rejected (upstream ahead) → pull --rebase first, then retry
  • Auth failure → SSH key or deploy token may need refresh, escalate to operator
  • Force push requested on main → always escalate for confirmation