ship-test-ensure

Automate shipping pipelines from commit to production with staging verification and audits.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/vinicius91carvalho/.claude --skill ship-test-ensure
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship-test-ensure
Source: https://github.com/vinicius91carvalho/.claude/tree/main/skills/ship-test-ensure
Command: npx skills add https://github.com/vinicius91carvalho/.claude --skill ship-test-ensure

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

End-to-end shipping is automated from code commit to production, including staging, E2E validation, production deployment, and post-deploy audits, reducing manual toil and risk.

Core Features & Use Cases

  • Autonomous CI/CD pipeline: from commit to verified production with automated gating and rollback readiness.
  • Staging deployment and E2E testing: validate changes in a production-like environment before production.
  • Production deploy with mandated human confirmation: safeguard critical releases while maintaining speed for regular updates.
  • Post-deploy quality checks: PageSpeed Insights and Lighthouse audits to ensure performance/quality targets.
  • Execution Config driven: reads settings from CLAUDE.md to tailor commands, targets, and credentials.
  • Audit-ready reporting: maintains a session learnings file and final report to document outcomes.

Quick Start

Start an autonomous ship-test-ensure run from the current branch to execute staging verification, E2E tests, production deployment, and post-deploy audits.

Frequently Asked Questions about ship-test-ensure

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

FAQPage Schema
How do I automate CI/CD pipelines from commit to production with staging verification?▼

You can automate end-to-end shipping pipelines from commit to production by enforcing staging verification, E2E validation, and post-deploy audits. This approach reduces manual toil and ensures production readiness through mandatory gates.

How do I run E2E tests in staging before deploying to production?▼

Run E2E tests by deploying changes to a production-like staging environment first. This validates your code before any production deployment, ensuring that only verified changes pass the mandatory gating checks.

Can I use CLAUDE.md execution config to tailor autonomous deployment commands?▼

Yes, autonomous deployments can read settings directly from CLAUDE.md execution config. This allows you to tailor specific commands, deployment targets, and required credentials for your CI/CD pipeline.

How do I automate PageSpeed and Lighthouse audits after a production deploy?▼

Automate PageSpeed and Lighthouse audits by running post-deploy quality checks immediately after production deployment. This ensures your performance and quality targets are continuously verified and audit-ready.

Does autonomous deployment require human confirmation for production releases?▼

Yes, production deploys require mandated human confirmation to safeguard critical releases. This maintains deployment speed for regular updates while preventing unauthorized changes to production.