release-debug

What problem does it solve?

This Skill helps engineers quickly determine why a repository's semantic-release or npm publish step failed in CI by locating the failing GitHub Actions release job, extracting its logs, and surfacing common error patterns.

Core Features & Use Cases

• Locate failing release jobs: Commands to list recent runs on main and identify the Release job and its failing steps.
• Capture and analyze logs: Guidance to stream and save job logs for inspection and targeted searches.
• Pattern-based troubleshooting: Predefined grep checks for common failure indicators such as ENEEDAUTH, ENOSLACKHOOK, MODULE_NOT_FOUND, OIDC token issues, and push rejection messages.
• Use Case: When a CI release job fails to publish to npm or semantic-release aborts, use this Skill to gather evidence, determine whether the cause is auth, environment, versioning, or branch protection, and decide the next remediation.

Quick Start

Run the release-debug flow to find the latest release job on main, save its logs, and scan for npm and semantic-release error patterns.