ship-to-dev

Merge feature branches into DEV after passing tests and coverage gates.

1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/aberrantCode/llm_skills --skill ship-to-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship-to-dev
Source: https://github.com/aberrantCode/llm_skills/tree/main/claude/skills/ship-to-dev
Command: npx skills add https://github.com/aberrantCode/llm_skills --skill ship-to-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often need to move their current work into the DEV branch safely and consistently, handling pulls, staging, committing, PR creation, merging, branch cleanup, and local DEV synchronization while meeting test and coverage requirements.

Core Features & Use Cases

  • Detects repository context and whether the work is already committed.
  • Guides through branch naming, pulls latest changes only when needed, stages all modifications, and runs full test, coverage, lint, and build gates.
  • Automatically creates a pull request targeting DEV, merges it with squash, deletes the feature branch, and syncs the local DEV branch.
  • Ideal for any developer who wants a single command to ship feature work to DEV without manual git choreography.

Quick Start

Use the ship-to-dev skill to automatically stage, test, create a PR, merge, and synchronize your changes into the DEV branch.

Frequently Asked Questions about ship-to-dev

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

FAQPage Schema
How do I automate git pull requests and merges into the DEV branch?

To automate pull requests and merges into the DEV branch, this skill orchestrates the entire feature-branch workflow including staging, testing, linting, PR creation, and squash merging. It automatically handles branch naming, quality gate enforcement, and local DEV synchronization.

What is the best way to ship code to DEV with automated testing and coverage checks?

The best way to ship code to DEV with testing and coverage checks is using an automated PR workflow that runs full test, coverage, lint, and build gates before merging. This ensures all quality requirements are satisfied before changes are merged into the target branch.

Can I use a single command to stage, commit, and create a pull request for my feature branch?

Yes, you can use a single command to stage, commit, and create a pull request for your feature branch. The skill detects repository context, stages modifications, runs quality gates, creates a DEV-targeted PR, and handles branch cleanup automatically.

Does the automated DEV merge workflow handle branch cleanup and local synchronization?

Yes, the automated DEV merge workflow handles branch cleanup and local synchronization. After merging the pull request with a squash, it automatically deletes the feature branch and synchronizes your local DEV branch with the remote repository.

How does feature branch PR workflow handle uncommitted changes before creating a pull request?

The feature branch PR workflow handles uncommitted changes by detecting repository context and automatically staging all modifications before running tests. It guides branch naming and pulls latest changes only when needed before creating the pull request.

What happens if linting or test coverage gates fail during the DEV branch merge process?

If linting or test coverage gates fail during the DEV branch merge process, the automated workflow halts before PR creation. The skill enforces all test, coverage, lint, and build quality gates to ensure only passing changes are merged into DEV.