skills.rest
darkroomengineering
darkroomengineeringOFFICIAL
Explore all skills by this author →
Website𝕏@darkroomdevsGitHub

ship

Automate type-check, build, test, lint, and PR creation for software changes.

41|3|Updated Jan 12, 2026
Search Tags:#automation#workflow#build#release#pr#ship#ci
One-click install
npx skills add https://github.com/darkroomengineering/cc-settings --skill ship-darkroomengineering
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/darkroomengineering/cc-settings/tree/main/skills/ship
Command: npx skills add https://github.com/darkroomengineering/cc-settings --skill ship-darkroomengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shipping software requires a reliable, repeatable pipeline to verify, build, test, lint, and prepare a PR for release.

Core Features & Use Cases

  • End-to-end shipping pipeline: Type-check, build, test, lint, review, and create a PR automatically.
  • Guardrails and compliance: Enforces mandatory steps to prevent incomplete releases.
  • Use Case: When a feature is ready, run this skill to produce a clean PR with validated builds and tests.

Quick Start

Initiate the ship pipeline to validate, build, test, lint, review, and open a PR for your latest changes.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate the end-to-end shipping pipeline for code changes?▼

Automating the shipping pipeline for code changes requires enforcing mandatory type-check, build, test, and lint steps before automatically generating a PR with a verified change set.

Can I automatically create a PR only after build and tests pass?▼

Automatically creating a PR after builds and tests pass requires guardrails that enforce mandatory checks to prevent incomplete releases from generating a verified change set.

What mandatory checks should a CI workflow run before opening a pull request?▼

Mandatory checks a CI workflow should run before opening a pull request include type-check, build, test, and lint steps to ensure a clean, validated release.

How do I add guardrails to prevent incomplete software releases?▼

Adding guardrails to prevent incomplete software releases involves configuring the shipping pipeline to enforce mandatory type-check, build, test, and lint validations before producing a PR.

Does this automated release workflow require any external CI dependencies?▼

This automated release workflow requires no external CI dependencies, self-containedly enforcing the type-check, build, test, and lint pipeline to produce a verified PR.

Related Skills

Explore More Software Engineering Skills→
LuohaothuLuohaothu
24

refactor-clean

Remove dead code, duplicates, and unused dependencies from JavaScript/TypeScript, Go, and Python projects.

Community
Advanced
D0NMEGAD0NMEGA
8

gsd-ship

Push a branch, create a PR with an auto-generated body, and track merge status.

Community
Advanced
ericdahl-devericdahl-dev

health

Calculate a codebase health score and visualize quality trends.

Official
Intermediate
KewtonKewton

release

Automate software releases from version bump to GitHub Release publishing.

Community
Advanced