Official agent skill

Ship

by awslabs in awslabs/loom

Finalize dev work on an issue branch — update docs, push, and open a PR.

OfficialApache-2.0Auto-check passedDevelopment

Install Ship

skills CLI
$ npx skills add awslabs/loom --skill ship -a claude-code

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

GitHub CLI
$ gh skill install awslabs/loom 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/awslabs/loom.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/ship .claude/skills/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
ship
GitHub stars
193
Token cost
~715 tokens
SKILL.md length
340 words
Files
1
Skills in repo
3
Repo updated
First seen
Licence
Apache-2.0

At a glance

Finalize dev work on an issue branch — update docs, push, and open a PR.

  • Works in 5 steps: Verify Branch State → Fetch Issue Details → Update Documentation → …
  • Tasks that involve Pull requests
  • SKILL.md covers Input, Step 1: Verify Branch State, Step 2: Fetch Issue Details and Step 3: Update Documentation, plus 2 more sections
  • Calls git and gh

What it does

Ship is an agent skill from awslabs/loom, published by the product's own GitHub organization. Finalize dev work on an issue branch — update docs, push, and open a PR.

Its SKILL.md is about 720 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. It works with Git. The repository describes itself as: Loom for AWS is an enterprise-grade platform for building, deploying, integrating, and operating AI agents on Amazon Bedrock AgentCore. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Pull requests

Example prompts

  • “/ship”

Requirements

  • Pre-approved tools (allowed-tools): Agent, Bash(git *), Bash(gh *), Bash(cd *), Bash(cat *), Bash(ls *), Bash(wc *), Read, Edit, Write, Grep, Glob

Workflow steps

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

  1. Verify Branch State
  2. Fetch Issue Details
  3. Update Documentation
  4. Commit Documentation Updates
  5. Push and Create Pull Request

What it can do on your machine

Read from SKILL.md and the folder at commit 00f5a5b. 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:

    • Agent
    • Bash(git *)
    • Bash(gh *)
    • Bash(cd *)
    • Bash(cat *)
    • Bash(ls *)
    • Bash(wc *)
    • Read
    • Edit
    • Write

    …and 2 more on the same allowed-tools line.

    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

Ship loads about 715 tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 340 words of instructions outside code blocks.

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

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 awslabs/loom at commit 00f5a5b, republished under its Apache-2.0 licence (© awslabs). 340 words, ~715 tokens.

Download SKILL.mdSave it as .claude/skills/ship/SKILL.md (or your agent's skills folder).
name
ship
description
Finalize dev work on an issue branch — update docs, push, and open a PR.
allowed-tools
Agent, Bash(git *), Bash(gh *), Bash(cd *), Bash(cat *), Bash(ls *), Bash(wc *), Read, Edit, Write, Grep, Glob
argument-hint
<issue-number>

Ship Issue

Finalize development work on a feature branch: update documentation, push, and submit a pull request.

Input

$ARGUMENTS must be a GitHub issue number (e.g. 78). If missing or non-numeric, ask the user for the issue number.

Step 1: Verify Branch State

Confirm that you are on a feature branch (not main). If on main, abort and tell the user to switch to the feature branch first.

Run git log main..HEAD --oneline to see all commits on this branch. There must be at least one commit. Display the commit list to the user.

Run git status to confirm the working tree is clean. If there are uncommitted changes, warn the user and ask how to proceed.

Step 2: Fetch Issue Details

Run gh issue view $ARGUMENTS --json title,body,labels,number to get the issue title and number.

Also check if a matching markdown file exists under tmp/issues/ by looking for files that start with a zero-padded version of the issue number (e.g. issue 78 maps to a file starting with 078-). If the file exists, read it to understand the requirements for documentation updates.

Step 3: Update Documentation

Search for all SPECIFICATIONS.md files in the repository using Glob (**/SPECIFICATIONS.md). Update each relevant file with the latest design decisions from this branch's changes. Use git diff main..HEAD to understand what changed.

Search for all README.md files in the repository using Glob (**/README.md). Update each relevant file with the latest implementation details. Ensure no sensitive or account-specific information is included — no ARNs, account IDs, tokens, secrets, or endpoint URLs.

Step 4: Commit Documentation Updates

Stage and commit all documentation changes:

git add -A
git commit -m "docs: update specifications and readme for issue #$ARGUMENTS

Co-Authored-By: Claude <noreply@anthropic.com>"

Step 5: Push and Create Pull Request

Display the final commits with git log main..HEAD --oneline for the user to review.

Push the branch to the remote:

git push -u origin HEAD

Create a pull request using gh pr create. Derive the PR title and body from the issue and the work done:

gh pr create --title "<semantic-prefix>: <short description>" --body "$(cat <<'EOF'
## Summary
<2-4 bullet points describing what this PR does>

## Test Plan
<bullet list of how the changes were tested>

Closes #$ARGUMENTS

Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"

The PR body must include Closes #<issue-number> so the issue is automatically closed when the PR is merged.

Display the PR URL to the user.

© awslabs, 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

Just SKILL.md in .claude/skills/ship of awslabs/loom.

Open the folder on GitHubat commit 00f5a5b

Compare with similar skills

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.

Ship compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ship this skillawslabs/loom193—~715Automated safety check: PassApache-2.0
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Understand Diff AnalysisEgonex-AI/Understand-Anything86k1 repos~1.4kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Open Code Review CLIalibaba/open-code-review44k—~3.1kAutomated safety check: PassApache-2.0
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    86k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed
  • Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed
  • Open Code Review CLI

    alibaba/open-code-review

    Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.

    44k GitHub stars~3.1k tokensUpdated 3 days ago
    DevelopmentAuto-check passed
  • Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed
  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed

More from awslabs/loom

  • Issue

    awslabs/loom

    Official

    Implement a GitHub issue end-to-end — branch, code, test, docs, and commit.

    193 GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Release

    awslabs/loom

    Official

    Increment the release version, draft release notes, and prepare a GitHub release.

    193 GitHub stars~601 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Ship

What does Ship do?

Finalize dev work on an issue branch — update docs, push, and open a PR. Ship is an agent skill from awslabs/loom, published by the product's own GitHub organization. Finalize dev work on an issue branch — update docs, push, and open a PR.

When should I use Ship?

Ship fits situations like: tasks that involve Pull requests.

How do I install Ship in Claude Code?

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

How do I install Ship in Codex?

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

Can I use 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 awslabs/loom --skill 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/ship, .gemini/skills/ship, .github/skills/ship and .opencode/skills/ship in your project.

What does Ship need to run?

Going by SKILL.md and its folder, Ship needs the command-line tools its instructions call (git and gh). Its frontmatter pre-approves these tools: Agent, Bash(git *), Bash(gh *), Bash(cd *), Bash(cat *), Bash(ls *), Bash(wc *), Read, Edit, Write, Grep, Glob.

Does 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 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 Ship use?

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 Ship use?

About 715 tokens (SKILL.md is roughly 2.9k 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 Ship?

Skills that share tags, products or a category with Ship: Finishing a Development Branch (obra/superpowers, 296k stars), Understand Diff Analysis (Egonex-AI/Understand-Anything, 86k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Open Code Review CLI (alibaba/open-code-review, 44k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ship?

awslabs (a GitHub organization, an official publisher) maintains it in awslabs/loom, which has 193 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 7, 2026.

Source: awslabs/loom on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.