add fix-ci-failed claude code custom command #7815
Conversation
|
Warning Rate limit exceeded@wvandeun has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 13 minutes and 9 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (1)
WalkthroughA new Markdown document is introduced at Pre-merge checks✅ Passed checks (3 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (2)
.claude/commands/fix-ci-failed.md (2)
3-20: Add verification steps after major actions per documentation guidelines.The learnings indicate that documentation should include verification steps after each major action to confirm successful completion. Consider adding expected output examples or success criteria for each step. For instance, after retrieving logs (step 1), specify what output indicates success; after implementing changes (step 5), clarify how to verify the fix is working.
Example enhancement for step 1 verification:
+ + **Verification:** You should see the failed job logs displayed. Look for error messages or stack traces that indicate the root cause.Based on learnings: Documentation changes should include verification checkpoints and troubleshooting guidance.
1-22: Create a Towncrier changelog entry for this new feature.This PR introduces a new custom command, which qualifies as a new feature. Per project conventions, create a changelog entry at
changelog/7815.added.md.Would you like me to generate the changelog entry file, or do you prefer to create it manually? I can help open a follow-up commit with the appropriate Towncrier entry.
Based on learnings: Applies to changelog entries – create entries for every new feature using format
${ISSUE}.{ACTION}.md.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
.claude/commands/fix-ci-failed.md(1 hunks)
🧰 Additional context used
🧠 Learnings (4)
📓 Common learnings
Learnt from: CR
Repo: opsmill/infrahub PR: 0
File: docs/docs/guides/AGENTS.md:0-0
Timestamp: 2025-12-02T08:57:13.765Z
Learning: Applies to docs/docs/guides/docs/docs/how-to/**/*.md{,x} : Break complex multi-step workflows into logical sections with clear headings, include verification after each major section, and provide troubleshooting tips for common issues
Learnt from: CR
Repo: opsmill/infrahub PR: 0
File: docs/docs/guides/AGENTS.md:0-0
Timestamp: 2025-12-02T08:57:13.765Z
Learning: Applies to docs/docs/guides/docs/docs/how-to/**/*.md{,x} : Include verification steps after each major action to confirm the step was completed successfully
Learnt from: CR
Repo: opsmill/infrahub PR: 0
File: docs/docs/guides/AGENTS.md:0-0
Timestamp: 2025-12-02T08:57:13.765Z
Learning: Applies to docs/docs/guides/docs/docs/**/*.md{,x} : Run linting with 'uv run invoke docs.lint' and build documentation with 'uv run invoke docs.build' before submitting documentation changes
Learnt from: CR
Repo: opsmill/infrahub PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-03T15:19:49.437Z
Learning: Applies to changelog/*.{added,fixed,housekeeping}.md : Create Towncrier changelog entries for every issue fix or new feature using the format `${ISSUE}.{ACTION}.md` where ACTION is one of: added, fixed, housekeeping
📚 Learning: 2025-12-02T08:57:13.765Z
Learnt from: CR
Repo: opsmill/infrahub PR: 0
File: docs/docs/guides/AGENTS.md:0-0
Timestamp: 2025-12-02T08:57:13.765Z
Learning: Applies to docs/docs/guides/docs/docs/how-to/**/*.md{,x} : Break complex multi-step workflows into logical sections with clear headings, include verification after each major section, and provide troubleshooting tips for common issues
Applied to files:
.claude/commands/fix-ci-failed.md
📚 Learning: 2025-12-03T15:19:49.437Z
Learnt from: CR
Repo: opsmill/infrahub PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-03T15:19:49.437Z
Learning: Applies to changelog/*.{added,fixed,housekeeping}.md : Create Towncrier changelog entries for every issue fix or new feature using the format `${ISSUE}.{ACTION}.md` where ACTION is one of: added, fixed, housekeeping
Applied to files:
.claude/commands/fix-ci-failed.md
📚 Learning: 2025-12-02T08:57:13.765Z
Learnt from: CR
Repo: opsmill/infrahub PR: 0
File: docs/docs/guides/AGENTS.md:0-0
Timestamp: 2025-12-02T08:57:13.765Z
Learning: Applies to docs/docs/guides/docs/docs/how-to/**/*.md{,x} : Include verification steps after each major action to confirm the step was completed successfully
Applied to files:
.claude/commands/fix-ci-failed.md
🪛 GitHub Check: markdown-lint
.claude/commands/fix-ci-failed.md
[failure] 15-15: Lists should be surrounded by blank lines
.claude/commands/fix-ci-failed.md:15 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "2. Understand the problem desc..."] https://github.com/DavidAnson/markdownlint/blob/v0.39.0/doc/md032.md
[failure] 14-14: Fenced code blocks should be surrounded by blank lines
.claude/commands/fix-ci-failed.md:14 MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines [Context: "```"] https://github.com/DavidAnson/markdownlint/blob/v0.39.0/doc/md031.md
🪛 LanguageTool
.claude/commands/fix-ci-failed.md
[grammar] ~5-~5: Use a hyphen to join words.
Context: ...the script should be the current checked out branch, which you can retrieve using...
(QB_NEW_EN_HYPHEN)
[style] ~18-~18: Consider using a different verb for a more formal wording.
Context: ...w 5. Implement the necessary changes to fix the issue 6. Run tests to verify the fi...
(FIX_RESOLVE)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: documentation
- GitHub Check: Cloudflare Pages
|
@wvandeun would be great to get this command in the repo, please can you try to rebase the branch or open a new branch/PR |
This custom command can be used with Claude code to fix issues that cause the GitHub CI to fail for the current checked out branch.
It will pull the logs for the failed tasks of the CI job, analyzes them and tries to implement a fix.
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.