publishing-source
Use when completed source work needs a decision about whether to commit, push, tag, release, or export it.
- License 许可
- MIT
- 最近更新
- 2026-10-08
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- publishing-source
- license
- MIT
- metadata
- { "owner": "Harley Bartles", "status": "active", "use_when": [ "source work is finished and you must decide whether to commit, tag, release, push source, or export a pack.", "choosing between a direct-main commit, a PR, a tag/release, or a pack export for the current change.", "publication proof is required and you must pick the right GitHub-visible surface." ], "source-id": "publishing-source", "source-path": "skills/publishing-source/SKILL.md", "use_instead": [ "using-github-mcp", "release-engineering", "verification-before-completion" ], "related_skills": [ "verification-before-completion", "finishing-a-development-branch", "using-github-mcp", "release-engineering", "repo-worker-base" ], "do_not_use_when": [ "the change is not yet validated; finish verification-before-completion first.", "the task is GitHub mechanics (PR/branch/commit reads or writes) rather than the publication decision; use using-github-mcp.", "the task is release pipeline or CI/CD operation rather than the source-publication decision; use release-engineering." ], "provenance-name": "Publishing Source first-party skill", "source-category": "first_party" }
- description
- Use when completed source work needs a decision about whether to commit, push, tag, release, or export it.
02 资源文件 4
- 参考文档agents/openai.yaml893 B
- 参考文档references/publishing-decisions.md2.9 KB
- 参考文档tests/pressure/prompts/source-publication-decision.md355 B
- 参考文档tests/pressure/README.md701 B
03 SKILL.md 正文
Publishing Source
Owns the source-publication decision tree for this repo: pick the smallest sufficient publication surface for the change, then hand off to the skill that performs the mechanics.
Decision checklist
Run these in order. Stop at the first row that matches the change.
- Validated? If the committed tree would not pass the pre-commit hook, run the named bus repair or preparation target, inspect and stage its output, then let the hook check the staged candidate. The hook does not repair or stage. Do not run the complete gate immediately before a normal commit. Publication is not a substitute for validation.
- Marketplace source edited? If the consumer's canonical marketplace source, inventory, provenance, or bundle manifest changed, regenerate with the consumer repository's canonical marketplace-generation command before publishing. Do not assume a particular repository layout or command name.
- Pick the surface. Choose the smallest sufficient surface from
references/publishing-decisions.md. - Publish. Hand off to the owning skill for the mechanics (
using-github-mcpfor GitHub surfaces,release-engineeringfor release pipelines,finishing-a-development-branchfor branch closeout). - Record proof. Capture the PR URL or direct-main commit SHA as the publication proof required by the repo root
AGENTS.md.
Canonical sequences
- Direct-main commit (authorized only): run explicit preparation/repair -> inspect and stage intended tree -> commit (pre-commit hook checks and passes or rejects) -> push -> record SHA.
- PR (default): run explicit preparation/repair -> inspect and stage intended tree -> commit (pre-commit hook checks and passes or rejects) -> branch -> push -> open a Draft PR -> record the PR URL. Keep it Draft during local review and repair; move it to Ready only when the current committed state has the required evidence and review. Do not ask a second permission question when the publication route was already authorized.
- Tag/release: finish the source change and merge -> tag the merged commit -> publish release notes -> record tag URL.
- Pack export: regenerate marketplace -> validate -> export the pack archive -> record the export artifact and the source commit it was built from.
Common mistakes
- Treating a local commit hash as publication proof. Local state is not repo completion.
- Publishing before
ci --checkis green on the staged tree. - Editing generated plugin surfaces by hand instead of regenerating from the registry.
- Skipping publication proof in the worker return.
04 同仓库更多 Skills
writing
Use when drafting, revising, or reviewing prose for human readers and clarity, an authorised voice, or reader-fatigue concerns may interact.
writing-with-clarity
Use when drafting, revising, or reviewing prose intended for human readers, including documentation, README files, reports, explanations, UI copy, errors, comments, commit messages, and pull request text.
writing-style
Use when revising or reviewing human-facing prose against an authorised voice card or a contextual reader-fatigue profile.
skill
暂无简介
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment.
writing-roadmaps
Use when a goal is too large for one writing-plans plan and requires a sequenced roadmap of consecutive plans.