Skip to content

feat(amdsmi): add amdsmi-why-ci-fail slash command - #9569

Merged
marifamd merged 1 commit into
developfrom
amdsmi-why-ci-fail-command
Aug 31, 2026
Merged

marifamd merged 1 commit into
developfrom
amdsmi-why-ci-fail-command

Conversation

@bill-shuzhou-liu

Copy link
Copy Markdown
Contributor

Summary

  • Adds .claude/commands/amdsmi-why-ci-fail.md — a Claude Code slash command for diagnosing CI failures on amdsmi PRs
  • Fetches PR metadata, CI check results, and failure logs via gh, then correlates failures against PR-changed files to determine verdict: Your issue, Pre-existing, Unrelated/Flaky, or Needs investigation
  • Handles known edge cases: (xfail) checks and therock-pr-bot secondary failures

Test plan

  • Run /amdsmi-why-ci-fail <PR_NUMBER> on a PR with known failures and verify the structured diagnosis output
  • Run without arguments on a branch with an associated PR and verify auto-detection works
  • Run on a PR with no failures and verify it exits cleanly with "All CI checks passed"

JIRA ID

N/A

Issue link

N/A

🤖 Generated with Claude Code

Adds a Claude Code slash command that diagnoses CI failures for an
amdsmi PR — correlates failed checks against PR-changed files to
determine whether failures are the PR author's issue, pre-existing
on the base branch, or unrelated/flaky.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@bill-shuzhou-liu
bill-shuzhou-liu requested a review from a team July 31, 2026 19:00
@therock-pr-bot

Copy link
Copy Markdown

❌ PR Check — Action Required

Check Status Details
📝 PR Description ❌ Fail Error: PR description must reference a JIRA ID, ISSUE ID, or a GitHub closing keyword.
Expected: include a JIRA ID / ISSUE ID line (separator : or -, or omitted; value may be a JIRA key, a number with/without #, or a link), OR a closing keyword + issue reference. Accepted examples:
• JIRA ID : TESTAUTO-6039
• JIRA ID - #330
• JIRA ID #330
• JIRA ID (on separate line)
ROCM-25757
• ISSUE ID : TESTUTO-3334
• ISSUE ID #3334
• ISSUE ID - TESTAUTO-3433
• ISSUE ID (on separate line)
AIRUNTIME-2352
• ISSUE ID : https://github.com/<org_name>/<repo_name>/issues/1234
• Closes #10
• Fixes octo-org/octo-repo#100
• Resolves: #123
• #123
• https://github.com/<org_name>/<repo_name>/issues/123
Current: no valid JIRA/ISSUE/closing-keyword reference found
⛔ Forbidden Files ✅ Pass —
🧪 Unit Test ✅ Pass PR does not contain code files — Unit Test auto-passed
🔎 pre-commit ⏳ Pending ⏳ Still running…
🚫 Draft PR 🔜 To Be Enabled —
🚩 Feature Flag 🔜 To Be Enabled —
📊 Code Coverage 🔜 To Be Enabled —

⚠️ 1 policy check(s) failed. Please address the issues above before this PR can be Reviewed.

🚫 Please fix the failed policies

  • ❌ PR Description

The Not ready to Review label was added to this PR. Once all policies pass, the label is removed automatically.

📖 Need help? See the Policy FAQ for details on every check and how to fix failures.

🙋 Wish to Override Policy?

@therock-pr-bot

Copy link
Copy Markdown

🚫 Please fix the failed policies before requesting reviews.

The following policy checks failed:

  • ❌ PR Description

The Not ready to Review label has been added to this PR.
Once all policies pass, the label will be removed automatically.

@github-actions

Copy link
Copy Markdown
Contributor

This pull request has been inactive for 25 days and will be marked as stale.

If you would like to keep this PR open, please:

  • Add new commits
  • Add a comment explaining why it should remain open

This PR will be automatically closed in 5 days if no further activity occurs.

@github-actions github-actions Bot added the Stale PR has no activity for 25+ days label Aug 26, 2026
@github-actions

Copy link
Copy Markdown
Contributor

This pull request has been automatically closed due to inactivity (30 days with no updates).

If you'd like to continue working on this, feel free to reopen the PR or create a new one.

@github-actions github-actions Bot closed this Aug 31, 2026
@marifamd marifamd reopened this Aug 31, 2026
@marifamd
marifamd merged commit 9d4ae3d into develop Aug 31, 2026
65 of 67 checks passed
@marifamd
marifamd deleted the amdsmi-why-ci-fail-command branch August 31, 2026 22:33
@systems-assistant

Copy link
Copy Markdown
Contributor

TheRock Submodule Bump Activity

Newest first

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants