with one click
compare-actions
Compare two actions for pattern consistency
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Compare two actions for pattern consistency
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Comprehensive health check for a single action
Scaffold a new GitHub Action with all required files
Deterministic adversarial code review focused on provable failures. Optimized for agent execution, minimal tokens, and high signal findings across web applications.
Generate a changelog for a specific action or the whole repo
Verify all action references are properly SHA-pinned
Run security analysis across all or a specific action
| name | compare-actions |
| description | Compare two actions for pattern consistency |
Compare two actions side-by-side for pattern consistency. Useful when one action was modeled after another and you want to ensure they follow the same conventions.
<action1> (required): First action directory name (e.g., npm-publish)<action2> (required): Second action directory name (e.g., npm-semantic-release)Check that both <action1>/action.yml and <action2>/action.yml exist. Abort with an error if either is missing.
Extract all actions/checkout@ references from both action.yml files. Flag if they use different SHAs.
Extract all actions/setup-node@, actions/setup-python@, actions/setup-go@, and similar setup action references.
Compare versions/SHAs between the two actions. Only compare setup actions that appear in both.
Look for actions/cache@ usage or built-in caching (cache: keys in setup actions). Compare cache key patterns and restore-keys strategies.
Check both actions for:
set -eu usage in shell blocksif: failure() or if: always() stepscontinue-on-error usageFlag differences.
Check both actions for:
::add-mask:: usageFlag if one action masks secrets and the other does not.
Print a comparison report:
Comparing: <action1> vs <action2>
--------------------------------------------------
Checkout version MATCH / MISMATCH (details)
Setup actions MATCH / MISMATCH / N/A
Cache patterns MATCH / MISMATCH / N/A
Error handling MATCH / MISMATCH (details)
Secret masking MATCH / MISMATCH (details)
Structure (summary of differences)
--------------------------------------------------
Inconsistencies found: N
A structured comparison report. Each check shows MATCH, MISMATCH (with details), or N/A (if the check does not apply to both actions). Inconsistencies are flagged with specific recommendations for which action should be updated to match.