GH#13902: tighten error-feedback.md (164→99 lines)#13950
GH#13902: tighten error-feedback.md (164→99 lines)#13950alex-solovyev wants to merge 2 commits intomainfrom
Conversation
Remove generic troubleshooting tables (common GH Actions errors, local test errors, language-specific test commands) that an LLM already knows. Deduplicate CI commands that appeared in both monitoring and resolution sections. Replace inline fork/PR workflow with pointer to reference/external-repo-submissions.md. Preserve all gh API commands, Checks API queries, linters-local.sh/qlty-cli.sh references, concurrency control YAML, feedback prioritization, and escalation guidance. Closes #13902
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 24 minutes and 4 seconds. ⌛ 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. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThe error feedback documentation file was streamlined by removing verbose sections (local build tests, common error tables), renaming workflow-related sections for clarity, and replacing detailed procedural lists with concise instructions. Total content reduced by 65 lines while preserving core institutional knowledge. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
🔍 Code Quality Report�[0;35m[MONITOR]�[0m Code Review Monitoring Report SonarCloud: 0 bugs, 0 vulnerabilities, 1 code smells Mon Mar 30 06:34:10 UTC 2026: Code review monitoring started 📈 Current Quality Metrics
Generated on: Mon Mar 30 06:34:13 UTC 2026 Generated by AI DevOps Framework Code Review Monitoring |
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
.agents/workflows/error-feedback.md (1)
79-79: Use one placeholder convention across commands.Line 79 uses
{number}while Line 71/99 context uses{pr_number}style. Standardizing placeholders will reduce copy/paste mistakes in automation prompts.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.agents/workflows/error-feedback.md at line 79, Standardize placeholder usage by replacing the `{number}` placeholders in the "Collect" command string (the snippet containing "gh pr view {number} --comments --json comments" and "gh api repos/{owner}/{repo}/pulls/{number}/reviews") with `{pr_number}` to match the `{pr_number}` convention used elsewhere; update both occurrences in that command so all automation prompts use a single placeholder convention.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.agents/workflows/error-feedback.md:
- Line 88: Replace the interactive "gh run watch" usage with an explicit
run-id-based invocation: after pushing (the "git push origin {branch}" step)
capture the created GitHub Actions run ID and pass that ID to the GH CLI watcher
instead of calling "gh run watch" with no arguments; update the script/code that
performs the push to extract the run id from the GH API/CLI output (the command
that lists or creates runs) and use that ID in the "gh run watch <run-id>"
invocation so monitoring is deterministic and non-interactive.
---
Nitpick comments:
In @.agents/workflows/error-feedback.md:
- Line 79: Standardize placeholder usage by replacing the `{number}`
placeholders in the "Collect" command string (the snippet containing "gh pr view
{number} --comments --json comments" and "gh api
repos/{owner}/{repo}/pulls/{number}/reviews") with `{pr_number}` to match the
`{pr_number}` convention used elsewhere; update both occurrences in that command
so all automation prompts use a single placeholder convention.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 31ac2a4b-8de5-4fcd-b94c-a361d18f1535
📒 Files selected for processing (1)
.agents/workflows/error-feedback.md
🔍 Code Quality Report�[0;35m[MONITOR]�[0m Code Review Monitoring Report SonarCloud: 0 bugs, 0 vulnerabilities, 1 code smells Mon Mar 30 06:40:13 UTC 2026: Code review monitoring started 📈 Current Quality Metrics
Generated on: Mon Mar 30 06:40:16 UTC 2026 Generated by AI DevOps Framework Code Review Monitoring |
|
Both findings addressed in commit 0d01679: standardized placeholders and added explicit run_id to gh run watch.
johnwaldo
left a comment
There was a problem hiding this comment.
Auto-approved by pulse — collaborator PR (author: @alex-solovyev). All pre-merge checks passed.



Summary
reference/external-repo-submissions.mdAll
ghAPI commands, Checks API queries,linters-local.sh/qlty-cli.shreferences, concurrency control YAML, feedback prioritization order, and escalation scenarios preserved.Closes #13902
Runtime Testing
Risk: Low — documentation/agent prompt only, no code changes.
Level:
self-assessedaidevops.sh v3.5.446 plugin for OpenCode v1.3.6 with claude-opus-4-6 spent 3m and 6,750 tokens on this as a headless worker.
Summary by CodeRabbit