push-skills
/push-skills
Wypycha skille i globalny AGENTS.md do prywatnego repozytorium i weryfikuje publiczne lustro, wyłącznie po wyraźnym wywołaniu /push-skills.
- Autor
- davidondrej ↗
- Repozytorium
- skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 26.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 26.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Wypycha skille i globalny AGENTS.md do prywatnego repozytorium i weryfikuje publiczne lustro, wyłącznie po wyraźnym wywołaniu /push-skills.
Oryginalny opis (EN)
Push skills and global AGENTS.md to the private repo and verify the public mirror. Use only when the user explicitly invokes /push-skills.
Jak działa
- Always include global instructions
- Choose the source file
- Prepare without disturbing other work
- Commit and push
- Verify public publication
Podgląd SKILL.md
--- name: push-skills description: Push skills and global AGENTS.md to the private repo and verify the public mirror. Use only when the user explicitly invokes /push-skills. disable-model-invocation: true --- # Push Skills Canonical repo: `AGENT_REPO`. Private remote: `PRIVATE_REPO`. Pushing `main` triggers the sanitized mirror at `PUBLIC_MIRROR_REPO`; only the configured automation pushes there. Only commit or push when the user requests it. Editing this skill is not permission to publish it. For distributed skill edits, follow `distribute-skill-to-all-agents` before pushing. ## Always include global instructions The user's standing scope for an authorized `/push-skills` run includes saved changes to `GLOBAL_INSTRUCTIONS_FILE`, unless they explicitly exclude that file. Check it on every run, even when the latest message names a skill. Preserve the conversation's original publishing objective through skill edits, renames, and other follow-up requests. After fetching, compare saved `global/AGENTS.md` with `origin/main:global/AGENTS.md`. Local dirt may already be published; Git status alone cannot tell. Transfer new edits while preserving upstream changes. Verify saved global instructions are committed privately and substantive updates appear in public root `AGENTS.md`. Report this separately; successful skill publication does not complete an AGENTS.md request. ## Choose the source file - `GLOBAL_INSTRUCTIONS_FILE` should link to `AGENT_REPO/global/AGENTS.md`. Save the editor buffer and verify the link. If it differs, inspect both files before choosing; do not replace the link or overwrite either file. Public destination: root `AGENTS.md`. - `AGENT_REPO/AGENTS.md` is a separate, private repo-instruction file and stays excluded. - Updating global instructions needs no copy, skill allowlisting, or policy version bump. - Skills live under `skills/<skill-name>/`. Use `publish-skill` for newly public skills; include policy changes in the same commit. ## Prepare without disturbing other work Run Git in `AGENT_REPO` or the temporary worktree below. Check staged and unstaged changes: ```bash git status --short git diff --cached --stat git diff HEAD -- global/AGENTS.md git remote -v git fetch origin main ``` For skills, substitute the intended paths. Confirm `origin` is private. Review outgoing commits as well as files: every commit ahead of `origin/main` will push. - Clean checkout: fast-forward `main` with `git merge --ff-only origin/main`. - Only intended edits pending: commit, then rebase those commits onto `origin/main`. - Unrelated edits, staged files, or local commits: use `git worktree add --detach <temporary-path> origin/main`. Preserve the original checkout and index. Transfer approved changes as a patch against their original base, using three-way application when needed; copy approved new files separately. Preserve newer upstream edits instead of overwriting with an old copy. Resolve conflicts from both versions; ask only when intent is ambiguous. Do not stash, reset, unstage, or commit someone else's work. ## Commit and push Stage only intended paths. Plain `git commit` includes all staged files regardless of the preceding `git add`; use an explicit path list: ```bash git add -- global/AGENTS.md git commit --only -m "Update global agent instructions" -- global/AGENTS.md ``` Adapt paths and message for skills. Review `git show --stat HEAD` and `git diff origin/main..HEAD` before pushing. If nothing needs committing, check whether the intended state is already pushed, then verify it. ```bash git push origin HEAD:main source_sha=$(git rev-parse HEAD) ``` If `main` advanced, fetch, rebase the isolated intended commits, review, and retry. Never force-push. Verify the remote contains the commit instead of relying on push-output labels. Report when a temporary worktree kept the original checkout untouched. ## Verify public publication Find the workflow for the pushed commit; a private push alone does not prove publication: ```bash gh run list --repo PRIVATE_REPO --workflow MIRROR_WORKFLOW \ --commit "$source_sha" --json databaseId,headSha,status,conclusion,url gh run watch <run-id> --repo PRIVATE_REPO --exit-status ``` Wait for the matching run. If superseded, verify the newer source contains your change. The workflow may add an automated sync commit, so public `Source:` can name a descendant of your commit. For failure, cancellation without replacement, or a stall, inspect status/logs and report incomplete publication with the run link. Do not rerun indefinitely. Read the published file and confirm the intended update: ```bash gh api repos/PUBLIC_MIRROR_REPO/contents/AGENTS.md \ -H 'Accept: application/vnd.github.raw' ``` Find skill categories from the committed policy and published tree, then check `skills/<category>/<skill-name>/SKILL.md`. Private-only skills need only private push verification. The mirror may rewrite or omit content; green CI and file existence do not prove correctness. For missing or unexpected content, inspect the matching mirror-report artifact and the mirror tooling documentation. Report exclusions/failures accurately. Never bypass the sanitizer or add manual approval gates. Finish with the private commit, workflow result, and published file link.
Pliki w paczce (2)
- SKILL.md 5 KB
- agents/openai.yaml 1 KB
Wersje
W bazie nie ma innych skilli o nazwie push-skills.
Migawka bazy z 13.11.2026 · wersja paczki 72b754080513 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100skills-push
Wysyła nowe lub zmienione lokalne skille do zdalnego repozytorium na GitHubie, najpierw pytając, które z nich. - 100sync-skills
Przenosi ostatnio zmienione skille i workflow do publicznego repozytorium, usuwając sekrety i dane osobowe, a potem wypycha commit. - 100skill-installer
Instaluje skille VT Code do $VTCODE_HOME/skills z listy polecanych lub ze ścieżki repozytorium GitHub, także prywatnego, i wyświetla skille możliwe do instalacji. - 95skill-installer
Instaluje skille Codex do $CODEX_HOME/skills z listy polecanych lub ze ścieżki repozytorium GitHub, także prywatnego, i wyświetla skille możliwe do instalacji. - 100skill-installer
Instaluje skille Codex do $CODEX_HOME/skills z listy polecanych lub ze ścieżki repozytorium GitHub, także prywatnego, i wyświetla skille możliwe do instalacji. - 100skill-sync
Synchronizuje skille między instalacją lokalną a repozytorium GitHub będącym źródłem prawdy: instaluje, aktualizuje, wyświetla i wypycha skille.