A Git publishing helper that pushes the current working branch to GitHub and creates a draft pull request when one does not already exist. Git is the version-control system, and a pull request is a proposed change for review.

Use it to publish a non-protected branch, show an existing pull request, or force-update a retained pull-request branch when the required branch and commit safeguards are supplied.

It avoids manually repeating branch detection, protected-branch checks, pushing, and draft pull-request creation.

git-publish — Skill for Claude Code by sflandergan/agentic-coding

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add sflandergan/agentic-coding --skill git-publish

Clone the repo

git clone --depth 1 https://github.com/sflandergan/agentic-coding

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/sflandergan/agentic-coding/git-publish/github.svg)](https://agentmods.dev/skills/sflandergan/agentic-coding/git-publish)

Your own site

<a href="https://agentmods.dev/skills/sflandergan/agentic-coding/git-publish"><img src="https://agentmods.dev/badge/skills/sflandergan/agentic-coding/git-publish/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/sflandergan/agentic-coding/git-publish"><img src="https://agentmods.dev/badge/skills/sflandergan/agentic-coding/git-publish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 564 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00037	$0.00564
Opus 5.5	$0.00015	$0.00226
Sonnet 5.5	$0.00007	$0.00113
Haiku 4.5	$0.00004	$0.00056

Measured 1mo ago against content hash 4e627ddee5a4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

git-publish scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/publish-branch.sh, test/helpers/stubs.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

core/agents/skills/git-publish/SKILL.md · 52 lines

How it starts

The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Publish the Current Branch

Run:

bash .agents/skills/git-publish/scripts/publish-branch.sh

The script:

Detects the current branch.
Refuses detached HEAD and protected branches — main, master, and the resolved default branch (origin/HEAD, falling back to main).
Pushes the current branch to origin with upstream tracking.
Prints the existing PR URL when one already exists and leaves its readiness unchanged.
Otherwise creates a draft PR with gh pr create --fill --draft and prints its URL.

If publishing fails because the branch is behind, has diverged, or needs a rebase, stop and report the Git failure to the calling workflow. Rebasing, pulling, or conflict resolution belongs to the workflow agent, not this narrow publish helper.

Publish to an Existing PR

When a workflow already owns an existing pull request and wants to force-update its retained head branch without an approval prompt, run:

bash .agents/skills/git-publish/scripts/publish-branch.sh \
  --existing-pr <number> \
  --expected-head <sha> \
  --head-branch <head-branch>

All three arguments are required together:

<number> is a positive pull-request number.
<sha> is the 40-character hexadecimal SHA that the remote head branch is expected to point at when publication starts.
<head-branch> is the retained pull-request headRefName; it must pass Git branch-ref validation and must not be a protected branch.

The script:

Treats the explicit <head-branch> as the remote destination; the local branch name is irrelevant, so local main and detached HEAD are accepted in this mode.
Verifies the pull request exists, is open, and still reports <head-branch> as its head branch.
Pushes the tested local HEAD with the qualified lease refs/heads/<head-branch>:<sha> to the explicit refspec HEAD:refs/heads/<head-branch>.
Prints the existing pull-request URL.

This mode never creates or merges a pull request. If the lease is stale because the remote head moved, the push fails and the script stops; never retry with an unqualified force push or switch to a newly renamed head branch.

Read the full file on GitHub · 52 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 52 lines · 37 tokens per session scan A 4e627ddee5a4

Subscribe to this mod's changes

git-publish is a skill published in the GitHub repository sflandergan/agentic-coding (4 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 564 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-13.

Git and workflow

git-publish

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Publish the Current Branch

Publish to an Existing PR

What ships with it

What this file has done since we first saw it

Other skills, from other repositories

merge-batch

prowler-commit

gh-auth-isolation

comet-github

github-skill

release-helper