Menu
GitHub repository initialization, authentication, PR governance, and cross-machine synchronization workflows.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | github-sync |
| description | GitHub repository initialization, authentication, PR governance, and cross-machine synchronization workflows. |
Streamlined workflows for repository management and cross-machine synchronization.
scripts/init-repo.sh <repo-name> [github-username]
Creates local repo, adds .gitignore, initializes git, creates GitHub repo, pushes initial commit.
scripts/sync-push.sh ["commit message"]
Stages changes (excluding agent-specific files), commits, pushes to origin, then runs PR governance for non-default branches. Default message: "Auto-sync YYYY-MM-DD HH:MM"
scripts/sync-pull.sh
Pulls latest from origin, handles merge conflicts with strategy preference for remote changes.
scripts/pr-governance.sh
Enforces Henry's repo governance:
init-repo.sh: self-merge is allowed while the default branch is still bootstrap-small.Use explicit override only when the project source of truth is clear:
PR_GOVERNANCE_PROJECT_CLASS=new scripts/pr-governance.sh
PR_GOVERNANCE_PROJECT_CLASS=existing scripts/pr-governance.sh
scripts/fix-auth.sh
Configures gh auth, sets up git credential helper, tests authentication.
Scripts automatically exclude:
SOUL.md, IDENTITY.md*.png, *.jpg, *.jpeg, *.gifsecrets/, .env, *.pem, *.keynode_modules/, dist/, .next/Default policy is conservative:
.github/pr-governance marker and therefore require approval.init-repo.sh writes .github/pr-governance with PROJECT_CLASS=new.pr-governance.sh treats that marker as new only while the default branch has at most 3 commits. After the bootstrap branch grows, the repo is treated as existing unless explicitly overridden.Workflow:
git checkout -b feature/my-change
# ... make changes ...
scripts/sync-push.sh "Describe change"
sync-push.sh calls pr-governance.sh after a successful feature-branch push. For existing codebases the helper creates or reuses a PR, prints PR_GOVERNANCE_DECISION=approval_required, and prints a Henry notification message. For new projects it self-merges the PR. To send approval requests automatically from an agent runtime, set:
GITHUB_SYNC_NOTIFY_HENRY=1 HENRY_NOTIFY_TARGET=<target> scripts/pr-governance.sh
Pattern: Each machine pulls before working, pushes after changes.
# On any machine
cd ~/clawd # or workspace directory
scripts/sync-pull.sh
# ... make changes ...
scripts/sync-push.sh "Description of changes"
Conflict resolution: If push fails due to remote changes, pull first:
scripts/sync-pull.sh # Handles conflicts automatically
scripts/sync-push.sh "Merged changes"
Scripts auto-configure on first run:
git config user.email "henry@curacel.ai"
git config user.name "Henry Mascot"
git config credential.helper '!gh auth git-credential'
Override by setting manually before running scripts.
Push rejected: Remote has changes you don't have locally.
scripts/sync-pull.sh # Pull and merge
scripts/sync-push.sh # Push again
Authentication failed: Credential helper not configured or gh not authenticated.
scripts/fix-auth.sh # Fixes both issues
Merge conflicts: Auto-resolved favoring remote. If manual resolution needed, script will prompt.
.github/pr-governance marker for new-project self-merge policyghgh auth login if neededUse when an existing UI artifact needs to be iterated to a verified 5/5 design score. Enumerate every view, run independent dead-item and design-rubric audits, apply fixes, then re-score with fresh reviewers until every view and the whole app pass. Designed for Enterprise Crew/OpenClaw operators finishing prototypes without false 5/5 claims.
Use when the operator says publish a skill, promote a skill publicly, or ship a skill to SuperAda, GitHub, and ClawHub. Sanitizes the skill bundle for personal info/secrets, publishes a GitHub source copy, updates SuperAda skill pages/install assets, and publishes to ClawHub with receipts.
Use when turning a coding goal or PRD into bounded build missions, running those missions through Codex, Droid, Cursor, or Claude Code, verifying outcomes separately, and preserving receipts. Geordi merges the former build-pipeline discipline with the installable mission runner.
Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards, and it must generate fresh separate images for sections or detail views rather than cropping them out of previously generated images.
Prepare for conferences, summits, trade shows, and investor events: research attendees/speakers/agenda, build pitch-deck briefs, schedule meetings, enrich contacts, capture session notes, and run post-event follow-ups.
Create and run evidence-backed OpenClaw beta test plans and issue intelligence loops. Use when an operator asks for beta testing, release candidate validation, baseline beta health checks, canary stress packets, beta issue submission/follow-up, automated vs manual beta checklists, contributor test asks, or OpenClaw release gate structure.