orbit-version-compare

Compares two WordPress plugin versions and reports code, asset, and visual differences.

2|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/adityaarsharma/orbit --skill orbit-version-compare
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orbit-version-compare
Source: https://github.com/adityaarsharma/orbit/tree/main/skills/orbit-version-compare
Command: npx skills add https://github.com/adityaarsharma/orbit --skill orbit-version-compare

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the comparison of two versions of the same WordPress plugin, highlighting changes such as new errors, asset weight, function adds/removes, hooks, and visual regressions.

Core Features & Use Cases

  • Version Comparison: Automatically compare v(N-1).zip vs v(N).zip for plugins.
  • Detailed Reports: Generates detailed reports on PHPCS errors, asset weight, function changes, hooks, and visual diffs.
  • Visual Diffs: Sets up visual baseline diffs for the new version for easy visual comparison.
  • Use Case: Ideal for pre-release checks, such as 'v1 vs v2', 'before vs after release', or 'what changed since the last release'.

Quick Start

Compare versions of your plugin with the following command:

bash ~/Claude/orbit/scripts/compare-versions.sh --old ~/downloads/my-plugin-v2.3.zip --new ~/downloads/my-plugin-v2.4.zip

Frequently Asked Questions about orbit-version-compare

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

FAQPage Schema
How do I automate WordPress plugin version comparison between two zip files?

Automate WordPress plugin version comparison by running a shell script that analyzes v(N-1).zip versus v(N).zip to highlight differences in code, assets, functions, hooks, and visual appearance.

What does a visual regression check for WordPress plugins include?

A visual regression check for WordPress plugins includes setting up visual baseline diffs for the new version, allowing easy visual comparison alongside reports on PHPCS errors, asset weight, function changes, and hooks.

Can I detect new PHPCS errors and function changes before releasing a plugin update?

Yes, you can detect new PHPCS errors and function changes before releasing a plugin update by executing an automated comparison script that generates detailed reports on differences between the old and new versions.

How do I compare two WordPress plugin zip files for code and asset differences?

Compare two WordPress plugin zip files for code and asset differences by passing the old and new zip file paths as arguments to the comparison script, which then executes regression analysis and outputs the results.

Do I need version control knowledge to run automated plugin version diffs?

Yes, you need basic file operations and version control knowledge to run automated plugin version diffs accurately, as the process requires managing plugin zip files and interpreting regression analysis reports.