github-project-release
/github-project-release
Przygotowuje i publikuje lokalny projekt jako czyste repozytorium GitHub: nowe repozytoria, prywatne wydania testowe, czyszczenie README, aktualizacje istniejących zdalnych i pakowanie kodu badawczego bez danych i artefaktów.
- Autor
- sidiangongyuan ↗
- Repozytorium
- codex-skills-library ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 21.09.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 5
- Skrypty
- 1
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 21.09.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 1 skrypt w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: scripts/github_project_release.py
Co robi i kiedy
Przygotowuje i publikuje lokalny projekt jako czyste repozytorium GitHub: nowe repozytoria, prywatne wydania testowe, czyszczenie README, aktualizacje istniejących zdalnych i pakowanie kodu badawczego bez danych i artefaktów.
Oryginalny opis (EN)
Use when preparing or publishing a local project as a clean GitHub repository. Covers new repositories, private staging releases, public README cleanup, updates to existing remotes, and research-code packaging without datasets, checkpoints, papers, or generated artifacts.
Jak działa
- Workflow
- Script Quick Reference
- Defaults
- When To Ask
Podgląd SKILL.md
---
name: github-project-release
description: Use when preparing or publishing a local project as a clean GitHub repository. Covers new repositories, private staging releases, public README cleanup, updates to existing remotes, and research-code packaging without datasets, checkpoints, papers, or generated artifacts.
license: MIT
---
# GitHub Project Release
Turn a local project into a clean GitHub repository that is safe to make public later. Default to
research-code release behavior: clean copy first, private GitHub repo first, audit before push.
## Workflow
1. Inspect the source project before copying.
- Identify the runnable entrypoints, key configs, curated figures/tables, license, citation files,
and upstream dependencies.
- Treat the codebase as source of truth. Do not preserve stale upstream README language as the
release front page.
2. Check credentials.
- Run `scripts/github_project_release.py auth-check`.
- Use the active `gh` account as the default owner.
- Never ask the user to paste a GitHub token into chat. If auth is missing, ask them to run
`gh auth login` or provide credentials through a secure non-chat channel.
3. Prepare a clean release copy.
- Run `scripts/github_project_release.py prepare --source <project> --dest <release-dir>`.
- Keep only what a new user needs to understand and run the project.
- Exclude datasets, checkpoints, logs, generated outputs, raw experiment dumps, paper PDFs, local
submission material, and exploratory files unless the user explicitly overrides the default.
4. Write or rewrite the README.
- Read `references/readme_playbook.md` before drafting README content.
- Use English by default.
- Write for external readers, not for the project owner.
- For research code, cover Context + Run + Cite: what it is, what problem it solves, what is
included, how to install/run the minimal path, and how to cite current and upstream work.
5. Audit before publishing.
- Run `scripts/github_project_release.py audit --path <release-dir>`.
- Treat reported high-risk items as blockers unless the user explicitly accepts them.
- If a paper link is not public, use `Paper link: coming soon.` and do not upload PDFs.
6. Publish privately.
- Run `scripts/github_project_release.py publish --release-dir <release-dir>`.
- If the repo does not exist, create a private repo.
- If it exists, push only safe non-rewriting updates.
- Do not force-push, delete, overwrite, or make the repo public unless explicitly requested.
7. Report the result.
- Include repo URL, branch, commit SHA, visibility, and audit status.
- If any sensitive artifact was accidentally pushed earlier, explain that branch-history cleanup
may not immediately remove exact-SHA access on GitHub; for strict removal, recreate a clean repo.
## Script Quick Reference
Resolve `<skill-dir>` to the directory containing this `SKILL.md`; do not
assume a particular global skills installation root.
```bash
python "<skill-dir>/scripts/github_project_release.py" auth-check
python "<skill-dir>/scripts/github_project_release.py" prepare \
--source /path/to/project \
--dest /path/to/project-github
python "<skill-dir>/scripts/github_project_release.py" audit \
--path /path/to/project-github
python "<skill-dir>/scripts/github_project_release.py" publish \
--release-dir /path/to/project-github
```
Use `--dry-run` on `prepare` or `publish` to inspect intended actions without copying or pushing.
## Defaults
- Visibility: private.
- Owner: active `gh` account.
- Repo name: sanitized release directory name, unless `--repo`, `--owner`, or `--name` is provided.
- Existing repo policy: safe update only.
- README language: English.
- Results policy: paper-confirmed figures/tables/results only; never infer metrics from logs.
- Asset policy: curated explanatory figures/tables only; never bulk-upload raw visualization outputs.
## When To Ask
Ask the user only when the answer cannot be derived from the project:
- Target GitHub owner differs from the active `gh` account.
- Repo name should differ from the project/release directory.
- A normally blocked file type must be included.
- The user wants public release, force-push, repo deletion, or history rewrite.
- The current project has no clear runnable path and the README would otherwise invent commands.
Pliki w paczce (5)
- LICENSE 1 KB
- SKILL.md 4 KB
- agents/openai.yaml 1 KB
- references/readme_playbook.md 4 KB
- scripts/github_project_release.py 21 KB
Wersje
W bazie nie ma innych skilli o nazwie github-project-release.
Migawka bazy z 13.11.2026 · wersja paczki 752272401825 (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
- 100public-repo
Upublicznia projekt lub skill jako repozytorium GitHub bez prywatnych danych w plikach, historii i ustawieniach, i pilnuje czystości przy kolejnych pushach. - 100readme-generation
Generuje profesjonalny README.md dla lokalnych projektów i zdalnych repozytoriów GitHub, gdy brakuje dokumentacji albo jest nieaktualna. - 95git-repo-creator
Zakłada repozytorium Git i GitHub z nazwą, opisem, licencją, .gitignore, README i CI, a istniejące repozytoria sprawdza i poprawia. - 100pb-open-source
Przygotowuje projekt do otwarcia kodu: oczyszczony fork bez sekretów i odniesień wewnętrznych, README i LICENSE, a potem nowe prywatne repo na GitHubie po GO, bez upubliczniania. - 100github-repo-readme
Sprawdza, tworzy lub poprawia README repozytorium z kodu, manifestów i testów, z sekcjami, odznakami i szybkim startem. - 100create-release-workflow
Prowadzi tworzenie nowego wydania: wpis w changelogu, tagi git, publikacja przez GitHub Releases i aktualizacja przykładów instalacji w README do ostatniego tagu.