Agent skill

Git Ship

by epam in epam/ai-dial-chat

A skill your agent uses whenever the user wants to commit, push, or ship changes in a git repository.

Apache-2.0Auto-check passedDevelopment

Install Git Ship

skills CLI
$ npx skills add epam/ai-dial-chat --skill git-ship -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install epam/ai-dial-chat git-ship --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/epam/ai-dial-chat.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/git-ship .claude/skills/git-ship && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
git-ship
GitHub stars
504
Token cost
~1.2k tokens
SKILL.md length
481 words
Files
4
Skills in repo
18
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses whenever the user wants to commit, push, or ship changes in a git repository.

  • Works in 8 steps: Detect mode (new branch vs. update… → Gather required context → Understand the changes → …
  • The user wants to commit
  • SKILL.md covers Step 0 — Detect mode (new…, Step 1 — Gather required context, Step 2 — Understand the changes and Step 3 — Determine area, plus 4 more sections
  • Calls git and gh

What it does

Git Ship is an agent skill from epam/ai-dial-chat. Use this skill whenever the user wants to commit, push, or ship changes in a git repository. Triggers include: "commit changes", "push my changes", "ship it", "commit and push", "create a branch and commit", "make a PR", "open a pull request", "create draft PR", or any variation of committing/pushing work. Always use this skill when the user mentions committing — even casually — as it handles the full cycle: branch → add → commit → push → (optionally) PR, with Conventional Commits format and automatic area…

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `areas.md`, `examples/commit-messages.md` and `examples/pr-body.md`).

It sits in Development, covering Commit messages, Git workflow and Pull requests. It works with Git. The repository describes itself as: A default UI for AI DIAL. The licence is Apache-2.0.

When your agent uses it

  • The user wants to commit
  • Ship changes in a git repository
  • Include: commit changes
  • Push my changes

Example prompts

  • “commit changes”
  • “push my changes”
  • “ship it”
  • “/git-ship”

Requirements

  • Pre-approved tools (allowed-tools): Bash(git:*), Bash(gh:*), Bash(grep:*), Read, Edit(.agents/skills/git-ship/areas.md)

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Detect mode (new branch vs. update existing)
  2. Gather required context
  3. Understand the changes
  4. Determine area
  5. Generate commit message
  6. Execute
  7. Pull Request (if requested)
  8. Summary

What it can do on your machine

Read from SKILL.md and the folder at commit 933c12c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(git:*)
    • Bash(gh:*)
    • Bash(grep:*)
    • Read
    • Edit(.agents/skills/git-ship/areas.md)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Git Ship loads about 1.2k tokens when it runs. Until then it costs about 133 tokens; SKILL.md has 481 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~133
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from epam/ai-dial-chat at commit 933c12c, republished under its Apache-2.0 licence (© epam). 481 words, ~1,248 tokens.

Download SKILL.mdSave it as .claude/skills/git-ship/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
git-ship
description
Use this skill whenever the user wants to commit, push, or ship changes in a git repository. Triggers include: "commit changes", "push my changes", "ship it", "commit and push", "create a branch and commit", "make a PR", "open a pull request", "create draft PR", or any variation of committing/pushing work. Always use this skill when the user mentions committing — even casually — as it handles the full cycle: branch → add → commit → push → (optionally) PR, with Conventional Commits format and automatic area detection.
allowed-tools
Bash(git:*), Bash(gh:*), Bash(grep:*), Read, Edit(.agents/skills/git-ship/areas.md)
disable-model-invocation
true
model
claude-haiku-4-5-20251001
context
fork
effort
low
arguments
ticket area
argument-hint
[ticket] [area]

Git Ship Skill

Full cycle for ai-dial-chat: checkout new branch from development → stage → commit (Conventional Commits) → push → optional PR. Base branch is development.

Supporting files (read them when the step says so — don't inline everything up front):

  • .agents/skills/git-ship/areas.md — how to resolve the commit area (scope) for this repo.
  • .agents/skills/git-ship/examples/commit-messages.md — type table, message + branch examples.
  • .agents/skills/git-ship/examples/pr-body.md — PR body template, rules, and gh pr create usage.

Step 0 — Detect mode (new branch vs. update existing)

bash
git rev-parse --abbrev-ref HEAD                 # current branch
gh pr view --json number,url,state 2>/dev/null  # open PR for current branch (if any)
  • New-branch mode — current branch is development (or another base branch), or there's no PR for it. Run the full cycle: Steps 1–6.
  • Update-existing mode — you're already on a feature branch and it has an open PR (or the user says "push to the existing PR" / "update my PR"). Do not create a new branch and do not run gh pr create. Stay on the current branch, then:
    1. Step 2 — review the changes.
    2. Step 4 — generate the commit message (reuse the existing PR's ticket; keep the same area/type).
    3. Step 5 — skip the git checkout lines; just git add → git commit → git push.
    4. Skip Step 6's gh pr create. Pushing updates the open PR automatically. Only refresh the body (gh pr edit --body) if the user asks or the description is stale/missing.
    5. Step 7 — report the existing PR link, not a new one.

Step 1 — Gather required context

  • Ticket number — use the ticket argument if passed. Else look in conversation context. If still not found, ask: "What is the ticket number?"
  • Area — if the area argument is passed, use it directly in Step 3.
  • Draft PR? — if the user said "draft", note it for Step 6.

This skill runs in a forked context (context: fork), so it does not see the main conversation. Prefer passing arguments: /git-ship 7432 catalog.


Show full SKILL.md (186 more words)Show less

Step 2 — Understand the changes

bash
git status
git diff HEAD

If there are no changes at all — report and stop.


Step 3 — Determine area

If the area argument was given, use it. Otherwise read .agents/skills/git-ship/areas.md and map the changed files to an area using its resolution rules. If the resolved area is new, follow that file's append-only self-extend rules so the taxonomy grows (the edit is staged in Step 5 and ships in the same commit).


Step 4 — Generate commit message

Format: <type>(<area>): <short description> (Issue #<ticket>).

Read .agents/skills/git-ship/examples/commit-messages.md for the type table, message examples, and the branch-name rule. Analyze the diff to pick the most accurate type and write a concise, imperative description. Breaking change → add ! before the colon.


Step 5 — Execute

bash
# 1. Create branch from base (skip in update-existing mode)
git checkout development
git checkout -b <type>/<short-slug>

# 2. Stage all changes (includes any areas.md self-extend edit)
git add .

# 3. Commit
git commit -m "<type>(<area>): <description> (Issue #<ticket>)"

# 4. Push
git push origin <type>/<short-slug>

If push fails (no permissions, rejected, conflict) — report the full output and stop. Do not force push or rebase automatically.


Step 6 — Pull Request (if requested)

If the user requested a PR or draft PR, read .agents/skills/git-ship/examples/pr-body.md and follow the repo PR template (.github/pull_request_template.md) — fill every placeholder, then run the gh pr create command shown there with --base development.


Step 7 — Summary

Always finish with a concise confirmation:

Branch:  <type>/<short-slug>
Commit:  <type>(<area>): <description> (Issue #<ticket>)
Push:    ✅ succeeded  /  ❌ failed — <reason>
PR:      <link> (created)  /  <link> (updated existing)  /  skipped
Area:    <area>  (note "added to taxonomy" if Step 3 self-extended areas.md)

© epam, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files in .claude/skills/git-ship of epam/ai-dial-chat.

  • SKILL.md
  • areas.md
  • examples/commit-messages.md
  • examples/pr-body.md

Open the folder on GitHubat commit 933c12c

Compare with similar skills

Git Ship next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Git Ship compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Git Ship this skillepam/ai-dial-chat504—~1.2kAutomated safety check: PassApache-2.0
Git Workflow and Versioningaddyosmani/agent-skills102k2 repos~3.5kAutomated safety check: NotesMIT
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT
Emoji Commit ConventionsbaptisteArno/typebot.io11k—~424Automated safety check: PassCustom licence
Draft Pull Request Creatorwordpress-mobile/WordPress-Android3.2k—~881Automated safety check: NotesGPL-2.0
Adk Gitgoogle/adk-python22k—~1.3kAutomated safety check: PassApache-2.0

Similar skills

  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    102k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes
  • React Router Pull Request Creator

    remix-run/react-router

    Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.

    57k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check passed
  • Emoji Commit Conventions

    baptisteArno/typebot.io

    Sets the repository's convention for commit messages and pull request titles: one emoji prefix for the main intent, a concise title and clean follow-up commits.

    11k GitHub stars~424 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Draft Pull Request Creator

    wordpress-mobile/WordPress-Android

    Commits and pushes current changes, writes a pull request title and body from the branch history and template, and opens a draft PR on GitHub after you approve it.

    3.2k GitHub stars~881 tokensUpdated today
    DevelopmentAuto-check: notes
  • Adk Git

    google/adk-python

    Official

    Writes commit messages and pull request descriptions for the adk-python repository: Conventional Commits types and scopes, subject lines that say why a change was made, and the linked-issue and…

    22k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Git PR Flow

    wgzhao/Addax

    Standard branch, commit, and pull-request workflow for this repo.

    1.4k GitHub stars~216 tokensUpdated today
    DevelopmentAuto-check passed

More from epam/ai-dial-chat

All 18 skills in this repo
  • Refactoring Audit

    epam/ai-dial-chat

    Deep codebase refactoring audit for AI DIAL Chat. An agent skill from epam/ai-dial-chat.

    504 GitHub stars~4.3k tokensUpdated today
    Auto-check passed
  • Read unresolved GitHub code review threads for the pull request associated with the current branch, classify each comment, and implement and verify required code fixes.

    504 GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Create Ticket

    epam/ai-dial-chat

    Interactively create OR update GitHub issues (Bug, Feature, Task) for the current repository.

    504 GitHub stars~4.6k tokensUpdated today
    Auto-check passed
  • Dep Scan

    epam/ai-dial-chat

    Runs Trivy filesystem scan against the repo root and emits structured vulnerability findings (CVE, package, versions) in the SDLC reviewer schema.

    504 GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Figma

    epam/ai-dial-chat

    Design-to-code workflow for Figma designs. An agent skill from epam/ai-dial-chat.

    504 GitHub stars~997 tokensUpdated today
    Auto-check passed
  • Responsive Design

    epam/ai-dial-chat

    Responsive (mobile + desktop) layout workflow. An agent skill from epam/ai-dial-chat.

    504 GitHub stars~2.7k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Git Ship

What does Git Ship do?

A skill your agent uses whenever the user wants to commit, push, or ship changes in a git repository. Git Ship is an agent skill from epam/ai-dial-chat. Use this skill whenever the user wants to commit, push, or ship changes in a git repository.

When should I use Git Ship?

Git Ship fits situations like: the user wants to commit; ship changes in a git repository; include: commit changes; push my changes.

How do I install Git Ship in Claude Code?

Run `npx skills add epam/ai-dial-chat --skill git-ship -a claude-code`. Or copy the skill folder (.claude/skills/git-ship in epam/ai-dial-chat) into .claude/skills/git-ship in your project. Claude Code loads it when a task matches its description.

How do I install Git Ship in Codex?

Run `npx skills add epam/ai-dial-chat --skill git-ship -a codex`. Or copy the skill folder (.claude/skills/git-ship in epam/ai-dial-chat) into .agents/skills/git-ship in your project. Codex loads it when a task matches its description.

Can I use Git Ship in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add epam/ai-dial-chat --skill git-ship -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/git-ship, .gemini/skills/git-ship, .github/skills/git-ship and .opencode/skills/git-ship in your project.

What does Git Ship need to run?

Going by SKILL.md and its folder, Git Ship needs the command-line tools its instructions call (git and gh). Its frontmatter pre-approves these tools: Bash(git:*), Bash(gh:*), Bash(grep:*), Read, Edit(.agents/skills/git-ship/areas.md).

Does Git Ship access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Git Ship safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Git Ship use?

Git Ship is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Git Ship use?

About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Git Ship?

Skills that share tags, products or a category with Git Ship: Git Workflow and Versioning (addyosmani/agent-skills, 102k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars), Emoji Commit Conventions (baptisteArno/typebot.io, 11k stars) and Draft Pull Request Creator (wordpress-mobile/WordPress-Android, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Git Ship?

epam (a GitHub organization) maintains it in epam/ai-dial-chat, which has 504 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 7, 2026.

Source: epam/ai-dial-chat on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.