release-checklist

Orchestrate pre-release QA and governance checks for EA Lite releases.

54|48|Updated Jul 19, 2017
One-click install
npx skills add https://github.com/WPDevelopers/essential-addons-for-elementor-lite --skill release-checklist-wpdevelopers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-checklist
Source: https://github.com/WPDevelopers/essential-addons-for-elementor-lite/tree/main/.claude/skills/release-checklist
Command: npx skills add https://github.com/WPDevelopers/essential-addons-for-elementor-lite --skill release-checklist-wpdevelopers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-flight checks ensure EA Lite releases are clean, compliant, and ready for wordpress.org by validating branch state, version consistency across key files, changelog format, distignore audit, and post-release verification. No phase is skippable — all gates must pass before shipping.

Core Features & Use Cases

  • Pre-flight validation: Check branch state, clean working tree, and up-to-date main to prevent drift.
  • Quality gates: Run PHPCS, linting, builds, and e2e tests to ensure code quality and stability.
  • Version bump synchronization: Ensure Version header, defined constants, and stable tag match across all files.
  • Changelog and i18n readiness: Validate changelog format and translation readiness for wordpress.org.
  • Distribution prep: Audit .distignore and packaging to ensure a clean zip for submission.
  • Post-release verification: Provide a checklist to verify the released version on a clean environment.

Quick Start

Run the release-checklist step on your next EA Lite release to ensure all gates pass before tagging.

Frequently Asked Questions about release-checklist

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

FAQPage Schema
How do I run pre-release checks for a WordPress.org plugin deployment?

Pre-release checks for a WordPress.org plugin deployment involve orchestrating multi-phase QA and governance gates, validating branch state, running PHPCS, and verifying version consistency before tagging. All quality gates must pass before shipping.

What is version bump synchronization and why does it matter for releases?

Version bump synchronization ensures the Version header, defined constants, and stable tag match across all files. It prevents version drift and submission rejections during wordpress.org release deployment.

How do I audit distignore for a clean WordPress plugin zip submission?

Auditing distignore for a clean WordPress plugin zip submission involves reviewing .distignore rules and packaging configurations to ensure only necessary production files are included for wordpress.org deployment.

Does the release checklist enforce PHPCS, linting, and e2e tests before tagging?

Yes, the release checklist enforces PHPCS, linting, builds, and e2e tests as mandatory quality gates. No phase is skippable; code quality and stability must be verified before deployment readiness is approved.

What are the limitations of skipping preflight validation in release planning?

Skipping preflight validation in release planning risks branch drift, uncommitted changes, and version mismatch across key files. No phase is skippable, meaning releases lacking these checks fail quality gates before tagging.