github-device-sync

Use this skill only when the owner explicitly asks to install or verify GDS, its pinned bundle, and selected harness projections on a new macOS, Linux, server, or CI device. Build an exact reversible plan and keep secrets in approved stores. Do not use it to clone every estate repository or change global tools silently.

Use this skill only when the owner explicitly asks to apply one logical change across repositories selected by a GDS portfolio. Create independent repository subplans, canaries, bounded waves, and an aggregate journal. Do not use it for one repository or pretend the portfolio has one Git transaction.

Use this skill only when the owner explicitly asks to finish the current work completely across every affected Git repository: implement, verify, integrate, publish, update dependency pins, and remove only proven-safe completed branches or worktrees. Do not use it for status, routine sync, or unfinished handoff.

Use this skill only when the owner wants to preserve unfinished work for another device or session. Plan an exact checkpoint commit, push the task branch, and create or update a draft pull request when policy requires it. Do not use it to merge, complete, synchronize main, or clean branches and worktrees.

Use this skill only when the owner explicitly asks to create, inspect, synchronize, rehome, detach, freeze, archive, or otherwise change a fork lifecycle. Preserve fork-specific commits and upstream identity; force is never the default. Do not use it for ordinary source repositories or generic branch synchronization.

Use this skill only when the owner explicitly asks to add, replace, reclassify, or remove a module relationship for a project. Validate independent Git boundaries, typed relationships, .gitmodules or package metadata, visibility, and pin policy. Do not use it for ordinary code changes inside an existing module.

Use this skill only when the owner explicitly asks to create, onboard, rename, transfer, archive, rehome, or otherwise change the lifecycle of a Git repository under GDS. Preserve stable identity and plan every provider and local mutation. Do not use it for source-code work or repository deletion hidden as removal.

Use this skill only when the owner explicitly asks to clone or materialize a selected repository set on a device. Resolve selectors, local roots, clone modes, submodules, and resource limits before applying. Do not use it to clone the whole estate by default or synchronize existing checkouts.

Use this skill only when the owner explicitly asks to migrate GDS manifests, state, policies, plans, or projections between schema versions. Rehearse a reversible migration on fixtures and canaries before approved apply. Do not use it for ordinary data edits or cosmetic format changes.

Use this skill only when the owner explicitly asks to release a verified GDS CLI, plugin, or immutable bundle. Enforce reproducible build, monotonic release sequence, checksums, provenance, SBOM policy, and exact artifact identity. Do not use it to develop features or roll out the release to repositories.

Use this skill only when the owner explicitly asks to release a module according to its declared pin and publication policy. Classify compatibility, verify the exact commit, publish required tag, package, or GitHub Release, and preserve provenance. Do not use it for module implementation or consumer pin updates alone.

Use this skill only when the owner explicitly asks to roll out an immutable GDS bundle or policy version across managed repositories. Plan canaries and bounded waves, apply approved repository changes, pause on failures, and verify adoption. Do not use it to edit canonical policy or publish a bundle.

Use this skill only when the owner explicitly asks to apply safe synchronization to selected existing local checkouts. Refresh remote evidence, skip dirty or diverged boundaries, and apply only approved fast-forward or policy-defined actions. Do not use it at session start or to clone, rebase, force, merge, or clean broadly.

Use this skill only when the owner explicitly asks to update verified consumers to a finalized module commit, version tag, or package version. Discover typed consumers, plan independent repository changes, verify each consumer, and roll out safely. Do not use it to release the module or mass-update without a selector.

Use this skill in a control-plane or portfolio session when detected estate drift must be classified, deduplicated, prioritized, and routed to canonical owners. Produce remediation candidates without applying them. Do not use it for ordinary repository implementation or silent auto-fix.

Use this skill only when the owner explicitly asks to inspect and resume, abort, or compensate an interrupted GDS operation or stale lock. Reconstruct state from the durable journal and current evidence before any action. Do not use it to conceal partial completion or perform a generic rollback.

Use this skill in a control-plane admin session when the owner asks for a read-only audit across repositories, portfolios, installations, policies, projections, or rollout state. Aggregate bounded evidence without applying remediation. Do not use it for one-repository review or any external mutation.

Use this skill when the owner asks to inspect one repository for GDS context, manifest, policy, projection, Git-state, or agent-system drift. Produce read-only evidence and remediation options. Do not use it to fix, synchronize, commit, push, merge, release, or clean anything.

Use this skill when verified repository facts changed and generated AGENTS, harness projections, or provenance-bearing Serena memories may be stale. Regenerate only affected context from canonical sources and validate drift. Do not use it for speculative documentation rewrites or estate-wide bundle rollout.

Use this skill only when the owner explicitly asks to update the GDS agent operating system itself: current source facts, capability profiles, canonical AGENTS templates, skills, schemas, generators, hooks, or policies. Validate, release immutably, and prepare canary rollout. Do not use it for ordinary repository feature work.

Use this skill only when the owner explicitly asks to add, update, verify, migrate, or retire an agent harness adapter in GDS. Research current official behavior, update one capability profile and generated projections, and prove runtime discovery. Do not use it to change a user's global harness configuration silently.

Use this skill when the owner asks where they are in the GDS estate, which Git boundaries and policies apply, or how to continue safely from the current directory. Resolve verified local context and explain available workflows. Do not use it to synchronize, publish, integrate, or clean work.

Use this skill in a control-plane admin session when the owner wants a structured, side-effect-free plan for a change spanning repositories, portfolios, policies, harnesses, or GitHub governance. Resolve targets, dependencies, approvals, waves, and rollback. Do not use it to apply the plan.