Skip to content

docs(skill): report bug attribution via @holdex bot - #146

Merged
zolotokrylin merged 3 commits into
mainfrom
feat/report-bug-command
Aug 7, 2026
Merged

docs(skill): report bug attribution via @holdex bot#146
zolotokrylin merged 3 commits into
mainfrom
feat/report-bug-command

Conversation

@georgeciubotaru

@georgeciubotaru georgeciubotaru commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

  • Documentation
    • Updated contribution guidelines to require bug-attribution details for fix pull requests.
    • Added instructions for reporting or disputing bug attribution, including commit and author information.
    • Added a guided workflow that validates details, requests missing information, identifies the current pull request, verifies existing attribution, and confirms successful submission.

@holdex

holdex Bot commented Aug 6, 2026

Copy link
Copy Markdown

Time Submission Status

Member # Time Running Total Status Last Update
georgeciubotaru 15min ✅ Submitted Aug 6, 2026, 10:20 AM
zolotokrylin 11min ✅ Submitted Aug 7, 2026, 1:51 AM

Submit or update total time with:

@holdex pr submit-time 2h

Add time on top of previous submission with:

@holdex pr add-time 1h30m

See available commands to help comply with our Guidelines.

@coderabbitai

coderabbitai Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 7abae105-d38c-4ccf-858a-adf108f8580f

📥 Commits

Reviewing files that changed from the base of the PR and between c8cff3a and 51b464b.

📒 Files selected for processing (1)
  • .claude/commands/report-bug.md

Walkthrough

The PR adds a /report-bug command for bug attribution and disputes. It also updates the contribution checklist so fix PRs require attribution before review readiness.

Changes

Bug attribution workflow

Layer / File(s) Summary
Report-bug command workflow
.claude/commands/report-bug.md
The command validates commit and author arguments, resolves the current PR, supports report and dispute modes, and posts the matching GitHub comment.
Fix PR contribution requirement
.claude/commands/holdex-contributing.md
The contribution rules require fix PRs to include bug commit and author attribution before review readiness.

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
Loading

Possibly related PRs

Suggested reviewers: zolotokrylin

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Title check ✅ Passed The title clearly summarizes the main change: documenting a command for bug attribution through the @holdex bot.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/report-bug-command

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@georgeciubotaru

Copy link
Copy Markdown
Contributor Author

@holdex pr submit-time 15m

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (1)
.claude/commands/report-bug.md (1)

1-1: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Add a level-1 heading at the start of the command file.

Line 1 triggers the reported MD041 check. 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

📥 Commits

Reviewing files that changed from the base of the PR and between d353931 and c8cff3a.

📒 Files selected for processing (2)
  • .claude/commands/holdex-contributing.md
  • .claude/commands/report-bug.md

Comment thread .claude/commands/report-bug.md
Comment thread .claude/commands/report-bug.md Outdated
georgeciubotaru and others added 2 commits August 6, 2026 13:35
Updated example commit URL to use a generic placeholder for user handle.

Signed-off-by: Vadim <1125014+zolotokrylin@users.noreply.github.com>

@zolotokrylin zolotokrylin left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@holdex pr add-time 11m

@zolotokrylin zolotokrylin changed the title feat(command): report bug attribution via @holdex bot docs(skill): report bug attribution via @holdex bot Aug 7, 2026
@zolotokrylin
zolotokrylin merged commit 5e723d8 into main Aug 7, 2026
3 of 4 checks passed
@zolotokrylin
zolotokrylin deleted the feat/report-bug-command branch August 7, 2026 01:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants