New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Ship A Feature

by compartmentdev in compartmentdev/compartment

Carry an approved repo change from request to monitored PR handoff by orchestrating preflight, implementation, review, commit, and PR creation without duplicating those skills.

Apache-2.0Auto-check passedBackend & APIs

Install Ship A Feature

skills CLI
$ npx skills add compartmentdev/compartment --skill ship-a-feature -a claude-code

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

GitHub CLI
$ gh skill install compartmentdev/compartment ship-a-feature --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/compartmentdev/compartment.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/ship-a-feature .claude/skills/ship-a-feature && 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-a-feature
GitHub stars
205
Token cost
~343 tokens
SKILL.md length
170 words
Files
2
Skills in repo
12
Repo updated
First seen
Licence
Apache-2.0

At a glance

Carry an approved repo change from request to monitored PR handoff by orchestrating preflight, implementation, review, commit, and PR creation without duplicating those skills.

  • Works in 6 steps: Confirm the ship target: approved… → Run $develop-a-feature with the approved… → Once the diff and local automated checks… → …
  • Backend & APIs work in your project
  • SKILL.md covers Read, Algorithm and Output
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Ship A Feature is an agent skill from compartmentdev/compartment. Carry an approved repo change from request to monitored PR handoff by orchestrating preflight, implementation, review, commit, and PR creation without duplicating those skills.

Its SKILL.md is about 340 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Backend & APIs. The repository describes itself as: Compartment is a self-hosted deployment system for small software on infrastructure your team controls. The licence is Apache-2.0.

When your agent uses it

  • Backend & APIs work in your project

Example prompts

  • “/ship-a-feature”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Confirm the ship target: approved request, expected outcome, dedicated feature branch, and whether the task should end at local ready…
  2. Run $develop-a-feature with the approved request, intended outcome, known scope, and visible constraints. Let it own preflight…
  3. Once the diff and local automated checks are stable, run $review-a-change and fix actionable findings before PR handoff.
  4. Use $commit-a-change for each commit that should survive review.
  5. When the branch is locally ready, hand it to $open-pr-and-monitor. Let that skill open or reuse the PR, return its URL, and start the…
  6. Finish when the monitored PR handoff starts, or when blocked or redirected before a PR can be opened.

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

    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 A Feature loads about 343 tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 170 words of instructions outside code blocks.

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

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 compartmentdev/compartment at commit 15373e7, republished under its Apache-2.0 licence (© compartmentdev). 170 words, ~343 tokens.

Download SKILL.mdSave it as .claude/skills/ship-a-feature/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
ship-a-feature
description
Carry an approved repo change from request to monitored PR handoff by orchestrating preflight, implementation, review, commit, and PR creation without duplicating those skills.

Ship a Feature

Use when the user wants the task implemented and handed to a monitored PR, not just coded locally.

Read

  • AGENTS.md
  • $develop-a-feature
  • $review-a-change
  • $commit-a-change
  • $open-pr-and-monitor

Algorithm

  1. Confirm the ship target: approved request, expected outcome, dedicated feature branch, and whether the task should end at local ready state or monitored PR handoff. Default to monitored PR handoff.
  2. Run $develop-a-feature with the approved request, intended outcome, known scope, and visible constraints. Let it own preflight, implementation, and local validation.
  3. Once the diff and local automated checks are stable, run $review-a-change and fix actionable findings before PR handoff.
  4. Use $commit-a-change for each commit that should survive review.
  5. When the branch is locally ready, hand it to $open-pr-and-monitor. Let that skill open or reuse the PR, return its URL, and start the monitoring heartbeat.
  6. Finish when the monitored PR handoff starts, or when blocked or redirected before a PR can be opened.

Output

Return only the PR URL, or the blocker if no PR was opened.

© compartmentdev, 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 1 other file in .codex/skills/ship-a-feature of compartmentdev/compartment.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 15373e7

Compare with similar skills

Ship A Feature 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 A Feature compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ship A Feature this skillcompartmentdev/compartment205—~343Automated safety check: PassApache-2.0
Configuring Horizoncoollabsio/coolify63k4 repos~898Automated safety check: PassMIT
Nestjs Best Practicesrolling-scopes/rsschool-app10k6 repos~1.2kAutomated safety check: PassMIT
Sub2API AdminWei-Shaw/sub2api43k1 repos~717Automated safety check: PassLGPL-3.0
Firecrawl Build Onboardingfirecrawl/firecrawl190k1 repos~1.4kAutomated safety check: NotesISC
Obsidian BasesAtmosphere/atmosphere3.8k22 repos~3.2kAutomated safety check: PassApache-2.0

Similar skills

  • Configuring Horizon

    coollabsio/coolify

    A skill your agent uses whenever the user mentions Horizon by name in a Laravel context.

    63k GitHub starsUsed in 4 repos~898 tokens
    Backend & APIsAuto-check passed

  • Nestjs Best Practices

    rolling-scopes/rsschool-app

    NestJS best practices and architecture patterns for building production-ready applications.

    10k GitHub starsUsed in 6 repos~1.2k tokens
    Backend & APIsAuto-check passed

  • Sub2API Admin

    Wei-Shaw/sub2api

    Manages a Sub2API deployment from the command line: accounts, redeem and invitation codes, groups, proxies, imports, exports and raw admin API calls.

    43k GitHub starsUsed in 1 repo~717 tokens
    Backend & APIsAuto-check passed

  • Firecrawl Build Onboarding

    firecrawl/firecrawl

    Gets Firecrawl working in a project: signs you in through the browser, saves FIRECRAWL_API_KEY to .env and picks the first SDK or REST path.

    190k GitHub starsUsed in 1 repo~1.4k tokens
    Backend & APIsAuto-check: notes

  • Obsidian Bases

    Atmosphere/atmosphere

    Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries.

    3.8k GitHub starsUsed in 22 repos~3.2k tokens
    Backend & APIsAuto-check passed

  • Fortify Development

    coollabsio/coolify

    ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.

    63k GitHub starsUsed in 4 repos~1.9k tokens
    Backend & APIsAuto-check passed

More from compartmentdev/compartment

All 12 skills in this repo

  • Audit Type Ownership

    compartmentdev/compartment

    Audit type ownership and boundary placement in the compartment repo: misplaced or duplicated types, query/service leaks, root export surface, and phased move plans.

    205 GitHub stars~745 tokensUpdated 1 mo ago
    Auto-check passed

  • Open PR And Monitor

    compartmentdev/compartment

    Open or reuse a repo PR and monitor it with a five-minute Codex heartbeat until it is ready, terminal, or blocked.

    205 GitHub stars~470 tokensUpdated 1 mo ago
    Auto-check passed

  • Review A Change

    compartmentdev/compartment

    A skill your agent uses when the user invokes $review-a-change or asks for a compartment repo code review; always use the delegated subagent review path by splitting review into separate parallel…

    205 GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check passed

  • Review Reuse And Dedup

    compartmentdev/compartment

    A skill your agent uses when reviewing compartment repo changes for existing helper reuse, extractable pure utilities, duplicated logic, repeated constants, hardcoded values, or repeated variable…

    205 GitHub stars~753 tokensUpdated 1 mo ago
    Auto-check passed

  • Compartment Smoke Test

    compartmentdev/compartment

    Run or delegate a browser-first smoke test of the local compartment through browser-use as a real user: boot or reuse the local stack, install or log in, deploy the repo smoke fixtures, verify CLI…

    205 GitHub stars~2.1k tokensUpdated 1 mo ago
    Auto-check: notes

  • Develop A Feature

    compartmentdev/compartment

    Implement repo changes by starting with preflight feature review, then editing the smallest owning surface on one canonical path and running only diff-triggered checks.

    205 GitHub stars~554 tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Ship A Feature

What does Ship A Feature do?

Carry an approved repo change from request to monitored PR handoff by orchestrating preflight, implementation, review, commit, and PR creation without duplicating those skills. Ship A Feature is an agent skill from compartmentdev/compartment. Carry an approved repo change from request to monitored PR handoff by orchestrating preflight, implementation, review, commit, and PR creation without duplicating those skills.

When should I use Ship A Feature?

Ship A Feature fits situations like: backend & APIs work in your project.

How do I install Ship A Feature in Claude Code?

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

How do I install Ship A Feature in Codex?

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

Can I use Ship A Feature 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 compartmentdev/compartment --skill ship-a-feature -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-a-feature, .gemini/skills/ship-a-feature, .github/skills/ship-a-feature and .opencode/skills/ship-a-feature in your project.

What does Ship A Feature need to run?

SKILL.md names no scripts, command-line tools or credentials: Ship A Feature is instructions for the agent only.

Does Ship A Feature access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Ship A Feature 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 A Feature use?

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

About 343 tokens (SKILL.md is roughly 1.4k 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 A Feature?

Skills that share tags, products or a category with Ship A Feature: Configuring Horizon (coollabsio/coolify, 63k stars), Nestjs Best Practices (rolling-scopes/rsschool-app, 10k stars), Sub2API Admin (Wei-Shaw/sub2api, 43k stars) and Firecrawl Build Onboarding (firecrawl/firecrawl, 190k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ship A Feature?

compartmentdev (a GitHub organization) maintains it in compartmentdev/compartment, which has 205 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on August 20, 2026.

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