القائمة
Autonomously diagnose and fix a failing CI pipeline on the current branch.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Evaluate the CI/CD pipeline on the PR, check for failures, and fix any issues.
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.
| name | ci-diagnose |
| description | Autonomously diagnose and fix a failing CI pipeline on the current branch. |
Follow these steps to autonomously diagnose and resolve CI failures on the current branch.
Find Latest Failed Run: Run the following command to retrieve the list of recent runs for the current branch and locate the latest failure:
gh run list --branch $(git branch --show-current)
Retrieve Failure Logs: Query the detailed failure logs for the specific failed Run ID identified:
gh run view [RUN_ID] --log-failed
Reproduce Locally:
Run the exact linter command, test command, or build step reported in the failure log on your local environment (e.g. running specific linters, cargo test --all, or container builds).
Fix the Root Cause: Resolve the root issue, checking for configuration schema mismatches, version alignment, or code bugs. Do not just address the symptom.
Local CI Check: Before committing, run the full suite of local validations:
cargo clippy -- -D warnings
cargo test --all
Ensure any pre-commit hooks also pass cleanly.
Commit & Push: Commit your changes using a conventional commit message:
git commit -m "fix(ci): [description of root cause]"
git push origin $(git branch --show-current)
Verify Pipeline Execution: Wait 30 seconds, then check the run list again to verify that the CI pipeline is running and progressing:
gh run list
Iterate: If CI fails again with a DIFFERENT error, repeat starting from step 2. If it fails with the SAME error, your local reproduction was incorrect; investigate the environment or reproduction command deeper. Do up to 3 iterations. Report what you fixed and why it broke.