← ClaudeAtlas

orbit-changelog-testlisted

Map every CHANGELOG.md entry to a targeted Playwright test or skill audit. Reads the changelog, classifies each entry (NEW FEATURE / PERFORMANCE / SECURITY / BUG FIX / etc.), and generates a per-change test plan you can execute before tagging the release. Use when the user says "test the changelog", "changelog → tests", "test the new features", "before release", or has just updated CHANGELOG.md for a new version.
adityaarsharma/orbit · ★ 1 · Testing & QA · score 55
Install: claude install-skill adityaarsharma/orbit
# 🪐 orbit-changelog-test — Changelog-driven test plan The release is only as good as the tests for what changed. This skill ensures every changelog entry has a corresponding test or audit. --- ## Quick start ```bash bash ~/Claude/orbit/scripts/changelog-test.sh \ --changelog ~/plugins/my-plugin/CHANGELOG.md ``` Output: `reports/changelog-tests-<timestamp>.md`. --- ## How it works 1. Read `CHANGELOG.md` (the one for the release you're about to tag) 2. For each `=== <version> ===` block, parse each line into: - **Category** (NEW FEATURE / FIX / PERFORMANCE / SECURITY / I18N / DEPRECATION / etc.) - **Subject** (what changed — usually the feature/file name) 3. Suggest a specific test or skill audit for that line 4. Output a checklist you can run as part of the release gate --- ## Example CHANGELOG.md: ``` == 2.4.0 == - [NEW FEATURE] Added Mega Menu widget for Elementor - [PERFORMANCE] Reduced DB queries on homepage by 30% - [SECURITY] Added nonce verification to AJAX handler in admin/save.php - [FIX] Fixed crash when saving empty settings - [I18N] Updated French + German translations - [DEPRECATION] Removed legacy `my_plugin_old_render()` filter ``` Output (excerpt): ```markdown # Changelog Test Plan — my-plugin v2.4.0 ## [NEW FEATURE] Mega Menu widget for Elementor **Test:** 1. Open Elementor editor on a test page 2. Search for "Mega Menu" in the widgets panel — verify it appears 3. Drag onto canvas — verify it renders without errors 4. Configure 3 menu it