ci-diagnose

スター1

フォーク0

更新日2026年7月16日 06:21

Evaluate the CI/CD pipeline on the PR, check for failures, and fix any issues.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

ソース

andrewgari

andrewgari/starbunk-rs

ダウンロード

CI/CD Diagnose Workflow

When triggered, perform the following steps in order:

Check Pipeline Status: Fetch the latest CI pipeline status for the current branch or PR. You can use gh pr checks or the GitHub MCP.
Fetch Logs: If the pipeline failed, extract the error logs from the failed jobs. Do not guess the failure reason without reading the logs.
Analyze: Identify the root cause of the failure (e.g., linting error, failing test, build error, Docker issue).
Fix: Make the necessary edits to the codebase to resolve the issue. If it's a test failure, ensure the tests pass locally before proceeding.
Commit and Push: Stage, commit, and push the fix (git push).
Re-check: Verify the pipeline starts running again and monitor it until it passes, or instruct the user to check the pipeline status once it's triggered.

このリポジトリの他の Skills

同じリポジトリ

Analyzes the current branch/PR and adds comprehensive, well-formatted structured logging and spans for observability.

Review PR comments, categorize them into critical/nitpicks, fix user-selected ones, and close resolved comments.

Create a PR using the current branch. Generates a PR description, commits changes, and pushes.

Mandatory rules for general git use in this repository. Follow these constraints before starting work, committing, or pushing.

Feature developer and task runner. Start a new task on a fresh branch, orchestrate worktrees, do the implementation work, and open a PR when done.

Worktree lifecycle protocol — context switching, creating, and cleaning up git worktrees for starbunk-rs.

name	ci-diagnose
description	Evaluate the CI/CD pipeline on the PR, check for failures, and fix any issues.

When triggered, perform the following steps in order:

Check Pipeline Status: Fetch the latest CI pipeline status for the current branch or PR. You can use gh pr checks or the GitHub MCP.
Fetch Logs: If the pipeline failed, extract the error logs from the failed jobs. Do not guess the failure reason without reading the logs.
Analyze: Identify the root cause of the failure (e.g., linting error, failing test, build error, Docker issue).
Fix: Make the necessary edits to the codebase to resolve the issue. If it's a test failure, ensure the tests pass locally before proceeding.
Commit and Push: Stage, commit, and push the fix (git push).
Re-check: Verify the pipeline starts running again and monitor it until it passes, or instruct the user to check the pipeline status once it's triggered.