avad-ship

Automate the end-to-end ship workflow from branch validation to PR creation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end ship workflow: validate branch state, sync with the target branch, run tests, perform pre-landing review, push changes, and create a PR.

Core Features & Use Cases

  • Project-aware shipping: reads docs/GIT_WORKFLOW.md, CLAUDE.md, AGENTS.md to determine target branch, required checks, and test commands.
  • Gatekeeping and safety: runs pre-landing review, handles conflicts, and prevents unsafe pushes.
  • Dead-branch handling: detects upstream branches and stops when nothing to ship, with options to move changes to a new branch.
  • Automation scaffolding: integrates with CI, generates/update testing/docs as needed (via further steps).

Quick Start

Run the ship workflow on your feature branch to validate, sync, test, review, and open a PR.

Frequently Asked Questions about avad-ship

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

FAQPage Schema
How do I automate my git workflow to run tests and create a PR?

You can automate the end-to-end git workflow to run tests and create a PR by validating branch state, syncing with the target branch, running pre-landing reviews, and pushing changes. This ensures project-aware gatekeeping checks are enforced before opening the PR.

What is a pre-landing review in a CI workflow?

A pre-landing review in a CI workflow is an automated gatekeeping step that validates branch state and runs checks before pushing changes. It reads project docs like CLAUDE.md to tailor review checklists, preventing unsafe pushes and handling conflicts.

How do I handle dead branches when trying to ship changes?

To handle dead branches when trying to ship changes, the workflow detects upstream branches and stops when nothing is left to ship. It safely guides you to move existing changes to a new branch before proceeding with the PR creation.

Can I use custom git workflow configurations from my project docs?

Yes, you can use custom git workflow configurations from project docs. The workflow reads docs/GIT_WORKFLOW.md, CLAUDE.md, and AGENTS.md to determine the target branch, required checks, and specific test commands for your repository.

Why does my automated PR workflow stop before pushing?

Your automated PR workflow stops before pushing to enforce safety gate checks. It halts actions when it detects merge conflicts, test failures, or dead branches, ensuring no unsafe code changes reach the target branch.

Does the automated ship workflow integrate with CI pipelines?

Yes, the automated ship workflow integrates with CI pipelines to run tests and generate testing or documentation scaffolding. It surfaces the final PR URL upon success, bridging local validation with continuous integration.