skills.rest
mrdulasolutions
mrdulasolutionsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

devlearn-pre-ship

Run a merge/deploy checklist evaluating tests, lint, builds, secrets, and rollback.

1|Updated May 24, 2026
Search Tags:#breaking changes#merge readiness#secrets scanning#release checklist#rollback planning#staging parity#ship lifecycle
One-click install
npx skills add https://github.com/mrdulasolutions/DevLearn --skill devlearn-pre-ship
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: devlearn-pre-ship
Source: https://github.com/mrdulasolutions/DevLearn/tree/main/devlearn-pre-ship
Command: npx skills add https://github.com/mrdulasolutions/DevLearn --skill devlearn-pre-ship

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents risky releases by guiding you through a focused pre-merge/pre-release checklist, including tests, lint/types, build readiness, secrets scanning, staging parity, rollback planning, and breaking-change awareness.

Core Features & Use Cases

  • Release readiness checklist: Produces a structured pass/fail/skip report to decide go/no-go with clear blocker prioritization.
  • Vibe (viber) vs decision (seasoned) modes: Keeps it fast when you need momentum, or expands into rollback and migration-risk review for critical changes.
  • Action handoffs across the ship lifecycle: Suggests next steps to chain into security, devops, deploy, and post-ship checks.

Quick Start

Tell your agent to run pre-ship on this release candidate and include a summary of any failing checks plus the top blockers.

Frequently Asked Questions about devlearn-pre-ship

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

FAQPage Schema
How do I run a pre-merge checklist to ensure release readiness for my code changes?▼

To ensure release readiness, a pre-merge checklist evaluates tests, lint/types, builds, secrets exposure, staging parity, and rollback options. It produces a structured pass/fail/skip report to help you decide go/no-go for your release candidate.

What is staging parity and why does it matter for production deploys?▼

Staging parity checks that your staging environment matches production conditions before a direct deploy. Evaluating this during pre-ship prevents unexpected runtime behavior by ensuring your release candidate has been tested against an environment mirroring real user traffic.

Can I use a release checklist for direct production deploys or is it only for PR merges?▼

You can use a release checklist for direct production deploys, PR merges, and release tagging. It applies across the ship lifecycle by collecting release target context and evaluating breaking-change risk, secrets scanning, and rollback planning for real users.

What's the best way to plan a rollback for breaking changes before merging?▼

The best way to plan a rollback for breaking changes is to expand your pre-ship checklist into a decision mode that reviews migration risks and rollback options. This identifies top blockers and suggests action handoffs to devops and post-ship checks.

Does the pre-ship checklist scan for exposed secrets in my build?▼

Yes, the pre-ship checklist includes secrets scanning to identify exposed credentials before release. It evaluates your build readiness and secrets exposure alongside tests and lint/types, generating a report to block risky merges.

Related Skills

Explore More Software Engineering Skills→
tony30552001tony30552001

land-and-deploy

Coordinate PR merge, CI wait, production deployment, and canary health checks.

Community
Advanced
zzxtbetazzxtbeta

land-and-deploy

Merge pull requests, wait for CI, deploy, and verify canary health.

Community
Advanced
jangtrinhjangtrinh

lint-and-validate

Run linters and type checkers on Node.js and Python projects.

Community
Intermediate
blocknaviblocknavi
1

convex-security-check

Audit Convex applications for authentication, function exposure, and access control.

Official
Basic