Skip to content

fix(ci): hourly reviewer prefers PRs over issues for small fixes#1432

Merged
max-sixty merged 3 commits intomainfrom
hourly/prefer-prs-over-issues
Mar 10, 2026
Merged

fix(ci): hourly reviewer prefers PRs over issues for small fixes#1432
max-sixty merged 3 commits intomainfrom
hourly/prefer-prs-over-issues

Conversation

@worktrunk-bot
Copy link
Collaborator

Summary

  • Rewrite the hourly reviewer's Step 7 ("Report findings") to prefer creating PRs over issues
  • PRs are now the default for any fixable problem (skill edits, workflow tweaks, CLAUDE.md updates)
  • Issues are only for problems too large or ambiguous to fix directly
  • PR descriptions carry the full analysis (run ID, log excerpts, root cause) — replacing what would have been the issue body
  • Instructs the bot to keep findings cohesive (grouped PRs, not many small patches)

This eliminates the duplication problem from #1425/#1426, where the hourly reviewer created an issue and the triage bot raced to also fix it. With the reviewer going straight to PR, there's no issue for triage to pick up.

Requested by @max-sixty in #1425 (comment).

Test plan

  • Workflow YAML passes validation (CI lint check)
  • Next hourly run creates PRs instead of issues for small fixes

🤖 Generated with Claude Code

Rewrite Step 7 of the hourly reviewer prompt so it defaults to creating
PRs (with thorough descriptions) instead of issues. Issues are now only
for problems too large or ambiguous to fix directly. Also instructs the
bot to keep findings cohesive rather than creating many small patches.

Requested in #1425.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Body: Include the run ID, specific log excerpts showing the problem, analysis of root cause, and what makes it hard to fix directly
- Label: `claude-behavior`

When you have multiple findings, keep them **cohesive**: group related fixes into a single PR rather than creating many small patches. If findings are unrelated, separate PRs are fine.
Copy link
Owner

Choose a reason for hiding this comment

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

let's group based on "broad theme"

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Done — updated the wording to "group by broad theme".

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@worktrunk-bot
Copy link
Collaborator Author

Looks good — clean rewrite of Step 7 that directly addresses the duplication problem from #1425/#1426.

A few observations:

Details

What this does well:

  • Clear hierarchy: PRs as default, issues as fallback — with concrete criteria for when each applies
  • "Do NOT also create a separate issue" is the key line that prevents the triage-race duplication
  • "The PR description replaces what would have been the issue body" sets the right expectation for thoroughness
  • Grouping by broad theme avoids the many-small-patches problem

One thing to watch:

  • The deduplication check in Step 6 still searches gh issue list and gh pr list separately. Now that the default output is PRs, the bot might still create a PR that overlaps with an existing issue (filed before this change). That's probably fine for the transition period — just noting it as something that may surface once.

No changes requested — this is a straightforward prompt improvement.

@max-sixty max-sixty enabled auto-merge (squash) March 10, 2026 21:28
@max-sixty max-sixty merged commit 90f8ec1 into main Mar 10, 2026
21 checks passed
@max-sixty max-sixty deleted the hourly/prefer-prs-over-issues branch March 10, 2026 21:39
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