メニュー
Diagnose semantic-release and npm publish failures from the latest CI release job
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Show CI/CD pipeline status for current branch with job details and failure diagnostics
Cross-validate documentation and artifacts across the codebase for consistency, conflicts, and contradictions. Use when users ask to "cross-validate", "validate docs", "check documentation consistency", "audit documentation", or find conflicts/contradictions in docs. Supports automatic fixing with "validate and fix" argument. Runs parallel subagents for efficient validation across categories (domain-models, agent-system, tech-stack, architecture, cli-commands). Part of the ShipIT autonomous SDLC platform — https://github.com/jrmatherly/shipit
React Flow (@xyflow/react) for workflow visualization with custom nodes and edges. Use when building graph visualizations, creating custom workflow nodes, implementing edge labels, or controlling viewport. Triggers on ReactFlow, @xyflow/react, Handle, NodeProps, EdgeProps, useReactFlow, fitView.
Provides complete shadcn/ui component library patterns including installation, configuration, and implementation of accessible React components. Use when setting up shadcn/ui, installing components, building forms with React Hook Form and Zod, customizing themes with Tailwind CSS, or implementing UI patterns like buttons, dialogs, dropdowns, tables, and complex form layouts.
Use when ready to commit, push, and create a PR with CI verification. Triggers include "commit and pr", "push pr", "create pr", "ship it", or when implementation is complete and needs CI validation. Watches CI and auto-fixes failures. Part of the ShipIT autonomous SDLC platform — https://github.com/jrmatherly/shipit
Use when the user wants rapid implementation iteration without tests, builds, or commits. Triggers include "fast loop", "fast iteration", "just code", "no tests", "iterate quickly", or when the user says they have a dev server running and want to check results manually. Part of the ShipIT autonomous SDLC platform — https://github.com/jrmatherly/shipit
| name | release-debug |
| description | Diagnose semantic-release and npm publish failures from the latest CI release job |
Diagnose why the Release or Dev Release job failed in CI.
gh run list --branch main --limit 3 --json databaseId,status,conclusion,name
gh run view <ID> --json jobs --jq '[.jobs[] | select(.name | test("Release")) | {name, conclusion, steps: [.steps[] | select(.conclusion == "failure") | .name]}]'
gh run view <ID> --job <JOB_ID> --log 2>&1 | tee /tmp/release-log.txt | tail -30
# npm auth failures
grep -n "ENEEDAUTH\|EOTP\|E403\|E401\|EINVALIDNPMTOKEN" /tmp/release-log.txt
# Semantic-release errors
grep -n "ENOSLACKHOOK\|SemanticReleaseError\|AggregateError" /tmp/release-log.txt
# npm/node version issues
grep -n "npm: \|Node.js v\|MODULE_NOT_FOUND" /tmp/release-log.txt
# OIDC issues
grep -n "OIDC\|id-token\|token exchange" /tmp/release-log.txt
# Git push failures (branch protection)
grep -n "protected branch\|push.*rejected\|Permission denied" /tmp/release-log.txt
registry-url in Release job's setup-node.SLACK_WEBHOOK env var. Check release.config.mjs conditional.git ls-remote --tags origin 'refs/tags/v*' and create missing tag.npm install -g npm@latest on Node 22 — use Node 24 instead.RELEASE_TOKEN secret exists and has contents:write permission. Check branch protection has enforce_admins: false.id-token: write permission in workflow job.