ship

Execute tightly scoped code edits and patches within repositories.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/espensev/ai-skills --skill ship-espensev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/espensev/ai-skills/tree/main/gemini-skills/skills/ship
Command: npx skills add https://github.com/espensev/ai-skills --skill ship-espensev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Ship Agent addresses the need to complete highly specific, tightly scoped coding tasks quickly and reliably, reducing manual debugging and project-context switching.

Core Features & Use Cases

  • Executes small, well-defined code edits and patches in a controlled scope.
  • Enforces contract-first guardrails and maintains auditable evidence of decisions.
  • Applies to micro-tixes like bug fixes, patches, or small feature adjustments across repositories.

Quick Start

Instruct the Ship Agent to complete a tightly scoped coding task in the target repository.

Frequently Asked Questions about ship

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute tightly scoped coding tasks without manual debugging?

You can execute tightly scoped coding tasks by instructing an automated agent to apply small code edits and patches within a controlled scope, reducing manual debugging and project-context switching.

What are contract-first guardrails in code editing?

Contract-first guardrails in code editing are enforced constraints that maintain auditable evidence of decisions before applying changes, ensuring consistency across repositories for bug fixes and small feature adjustments.

How do I apply micro-fixes and small patches across multiple repositories?

You can apply micro-fixes across multiple repositories by automating the process with an agent that enforces precise scope and contract-first guardrails, ensuring consistent small feature adjustments and patches without human error.

Does automated code editing work for small bug fixes and patches?

Automated code editing works effectively for small bug fixes and patches by enforcing a controlled scope and contract-first guardrails, ensuring changes are tightly scoped and auditable before being applied.

When should I not use an automated agent for code edits?

You should not use an automated agent for code edits when the task is not tightly scoped or well-defined, as this approach is designed specifically for small patches, micro-fixes, and minor feature adjustments to reduce turnaround times.