vitya
69091868cb
Skeleton (header + empty body) promoted from .workshop/.brainstorm/skill-private-dev-public-publish.md. Body filled in a second pass. No install/push/hermes — handled by baseline tasks. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1.6 KiB
1.6 KiB
name, version, description
| name | version | description |
|---|---|---|
| private-dev-public-publish | 0.1.0 | Use when setting up or maintaining a publishable open-source port/fork that should be developed privately but published cleanly — messy development on a PRIVATE Gitea repo (with `.wiki/`+`.tasks/` inside), and a curated COPY of finished work into a PUBLIC GitHub fork that preserves upstream lineage (stays a fork, keeps attribution; GPL-clean). Triggers - «опубликовать форк/порт на гитхаб», «разработку держать приватно, релиз публичный», «приватный гитеа + публичный гитхаб», «publish a fork without exposing dev history», «curated publish to GitHub», «как правильно форкнуть open-source для публикации». NOT for purely-private projects, purely-public open development, or greenfield bootstrap (use project-bootstrap). |
private-dev-public-publish
Two-repo topology for a publishable open-source port/fork: develop messily on a private Gitea repo (with .wiki/ + .tasks/ inside it), then publish only curated, finished work to a public GitHub fork that stays a real fork of upstream — so attribution and lineage hold and the dev history (experiments, dead-ends) never goes public.
When to use
<дописывается во втором проходе — источник: .workshop/.archive/2026-05-29-skill-private-dev-public-publish.md>
Inputs
<пусто>
Steps
<пусто>
Failure modes
<пусто>
Side effects
<пусто>
What NOT to do
<пусто>