agent-shipper

Commits changes, pushes Git branches, and creates pull requests for deployment.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/TrevorPLam/agency --skill agent-shipper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-shipper
Source: https://github.com/TrevorPLam/agency/tree/main/.windsurf/skills/agent-shipper
Command: npx skills add https://github.com/TrevorPLam/agency --skill agent-shipper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finalizes delivery by guiding the user to commit changes, push branches, and create pull requests in a controlled, auditable manner to prepare for deployment.

Core Features & Use Cases

  • Automates the final shipping steps after validation: lint/typecheck/tests and security checks.
  • Enforces conventional commits and PR workflows for deployment readiness.
  • Use Case: When reviewer, tester, and security validations are green, trigger shipper to prepare a deployment PR and mark the issue complete.

Quick Start

Trigger the shipper after reviewer, tester, and security validations pass to create PRs and enable deployment.

Frequently Asked Questions about agent-shipper

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

FAQPage Schema
How do I create a pull request after passing security and lint checks in CI/CD?

To create a pull request after passing security and lint checks, stage your changes and enforce conventional commit messaging. The shipper workflow automates this final step, guiding you to push branches and prepare a deployment PR once validations are green.

What is the best way to automate GitHub commits and branch pushing for deployment readiness?

The best way to automate GitHub commits and branch pushing for deployment readiness is using a controlled Git workflow. This approach requires staged changes and conventional commit messaging, ensuring your code is auditable and fully prepared for final deployment.

When do I need conventional commit messaging for a pull request?

You need conventional commit messaging for a pull request when finalizing delivery to prepare for deployment. It enforces a standardized PR workflow that ensures deployment readiness after reviewer, tester, and security validations have successfully passed.

Does this shipping workflow require passing security validations before committing changes?

Yes, this shipping workflow requires passing security validations before committing changes. It is triggered only when reviewer, tester, and security checks are green, ensuring code is safe to commit, push, and deploy via an auditable Git workflow.

Can I include a rollback plan when creating a deployment PR via a Git workflow?

Yes, you can include a rollback plan when creating a deployment PR via a Git workflow. The finalized shipping process supports generating a shipping checklist and rollback plan alongside optional PR automation payloads sent directly to GitHub.