docs(skill): report bug attribution via @holdex bot - #146
Conversation
Time Submission Status
Submit or update total time with: Add time on top of previous submission with: See available commands to help comply with our Guidelines. |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
WalkthroughThe PR adds a ChangesBug attribution workflow
Estimated code review effort: 2 (Simple) | ~10 minutes Sequence Diagram(s)sequenceDiagram
participant Contributor
participant report-bug
participant gh
participant GitHubPR
Contributor->>report-bug: Provide report or dispute arguments
report-bug->>gh: Resolve current pull request
report-bug->>GitHubPR: Post attribution or dispute comment
GitHubPR-->>Contributor: Display completion confirmation
Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
|
@holdex pr submit-time 15m |
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (1)
.claude/commands/report-bug.md (1)
1-1: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winAdd a level-1 heading at the start of the command file.
Line 1 triggers the reported
MD041check. Start the file with a heading, then place the command description below it.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.claude/commands/report-bug.md at line 1, Add a level-1 Markdown heading at the beginning of the command file, before the existing command description line, so the document starts with a heading and satisfies the MD041 requirement.Source: Linters/SAST tools
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.claude/commands/report-bug.md:
- Around line 17-19: Update the dispute workflow in report-bug.md so its gh pr
list lookup uses --state all, then validate that the previous attribution
comment matches the requested commit and GitHub handle. Require exactly one
matching PR before posting the dispute; otherwise stop without creating a
comment.
- Around line 32-39: Harden input handling in the report/dispute command flows:
validate the complete GitHub commit or PR URL and restrict the handle to a safe
full pattern, not merely an @ prefix. Store validated inputs in shell variables,
quote those variables in gh pr comment invocations, and provide comment content
through --body-file - in both forms.
---
Nitpick comments:
In @.claude/commands/report-bug.md:
- Line 1: Add a level-1 Markdown heading at the beginning of the command file,
before the existing command description line, so the document starts with a
heading and satisfies the MD041 requirement.
🪄 Autofix
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: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: eb9d9946-f6d4-4342-98c8-930aa8a74ea7
📒 Files selected for processing (2)
.claude/commands/holdex-contributing.md.claude/commands/report-bug.md
Updated example commit URL to use a generic placeholder for user handle. Signed-off-by: Vadim <1125014+zolotokrylin@users.noreply.github.com>
Summary by CodeRabbit