git-publishlisted

# `git-publish` — offer to commit and push, with confirmation ## Why this is a skill (Form 1) and not Form 2 Two other pieces need to chain into this one by name: `project-initializer` (after `/init-project` finishes) and `/new-feature` (after `java-spring-boot-developer` reports success). `disable-model-invocation: true` (Form 2) blocks exactly that — the model can't call a Form 2 skill via the `Skill` tool at all, only a human typing `/git-publish` can, the same restriction `java-spring-boot-developer.md` documents for why it can't re-invoke `java-patterns`. Precedent: `@.claude/decisions/0007-pipeline-skills-invocation.md` (D17) — the five `/new-feature` pipeline skills stay without `disable-model-invocation` for the same reason, and rely on an entry guard in the body instead of the flag. This file's guard is the two `AskUserQuestion` gates below: no git side effect ever runs without an explicit yes, regardless of what triggered the invocation. Form 3 (agent) was rejected: the confirmation dialogue with the user is the heart of this task, the context it needs fits entirely in this file, and the final output is short — all three fail the counter-test in `references/decision-matrix.md` § 5. Decision record: `@.claude/decisions/0034-git-publish-skill.md`. ## Contract **Input (optional, from the invoking context):** a short description of what was just done — e.g. "initial scaffold, blueprint hexagonal, maven, features: rest,jpa" or "UC-001-order: order management featur