Skip to content

Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows

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

worktrunk-bot90f8ec1930ab
diff --git a/.github/workflows/claude-hourly-review-reviewers.yaml b/.github/workflows/claude-hourly-review-reviewers.yaml
index ad6d0cb3a..bbf14b1aa 100644
--- a/.github/workflows/claude-hourly-review-reviewers.yaml
+++ b/.github/workflows/claude-hourly-review-reviewers.yaml
@@ -114,19 +114,23 @@ jobs:
gh issue list --state closed --label claude-behavior --json number,title,closedAt --limit 30
```
- ## Step 7: Report findings
-
- For each problem found:
- 1. **Create a GitHub issue** with label `claude-behavior`:
- - Title: Clear description of the behavioral problem
- - Body: Include the run ID, specific log excerpts showing the problem, analysis of root cause, and suggested fix
- - Use `gh issue create`
-
- 2. **For actionable fixes** (skill edits, workflow tweaks, CLAUDE.md updates):
- - Create a branch: `git checkout -b hourly/review-${{ github.run_id }}`
- - Make the changes
- - Commit and push
- - Create a PR referencing the issue
+ ## Step 7: Act on findings
+
+ Prefer PRs over issues. A PR with a clear description is more useful than an issue describing the same problem — it's immediately actionable and reviewable.
+
+ **Default: Create a PR** for problems you can fix (skill edits, workflow tweaks, CLAUDE.md updates, prompt adjustments):
+ - Create a branch: `git checkout -b hourly/review-${{ github.run_id }}`
+ - Make the changes
+ - Commit and push
+ - Create a PR with label `claude-behavior`. Put the full analysis in the PR description: run ID, specific log excerpts, root cause, and what the fix does. The PR description replaces what would have been the issue body — make it thorough.
+ - Do NOT also create a separate issue. The PR is the issue.
+
+ **Fallback: Create an issue** only for problems that are too large or ambiguous to fix directly — e.g., architectural concerns, unclear root causes, or changes that need maintainer judgment on the approach:
+ - Title: Clear description of the behavioral problem
+ - 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, group PRs by **broad theme**
## Step 8: Summary