Skip to content

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

fix(bot): guide claude-mention toward inline suggestions and push offers (#1435)

worktrunk-bot8d2e47d5eb78
diff --git a/.claude/skills/review-pr/SKILL.md b/.claude/skills/review-pr/SKILL.md
index b2a593087..919c4a609 100644
--- a/.claude/skills/review-pr/SKILL.md
+++ b/.claude/skills/review-pr/SKILL.md
@@ -472,12 +472,17 @@ gh api graphql -F query=@/tmp/resolve-thread.graphql -f threadId="THREAD_ID"
Outdated comments (null line) are best-effort — skip if the original context
can't be located.
-### 7. Push mechanical fixes on bot PRs
+### 7. Push mechanical fixes
-If the review found concrete, fixable issues on a bot PR (Dependabot, renovate,
-etc.) where there's no human author to act on feedback, commit and push the fix
+**Bot PRs** (Dependabot, renovate, etc.): If the review found concrete, fixable
+issues and there's no human author to act on feedback, commit and push the fix
directly to the PR branch.
+**Human PRs**: Post inline suggestions first (one-click apply is fastest for the
+author). Additionally, **offer to push a commit** when the fixes are mechanical
+and correctness is obvious — e.g., "I can push these changes in a commit if
+you'd like." Only push after the author accepts the offer.
+
```bash
gh pr checkout <number>
git add <files>
@@ -486,6 +491,3 @@ git commit -m "fix: <description>
Co-Authored-By: Claude <[email protected]>"
git push
```
-
-Only do this for mechanical changes where correctness is obvious. For human PRs,
-leave inline suggestions for the author instead.
diff --git a/.github/workflows/claude-mention.yaml b/.github/workflows/claude-mention.yaml
index 10383d6e7..d82a3af7b 100644
--- a/.github/workflows/claude-mention.yaml
+++ b/.github/workflows/claude-mention.yaml
@@ -208,11 +208,11 @@ jobs:
|| github.event.comment.html_url
&& (contains(github.event.comment.body, '@worktrunk-bot')
&& format(
- 'You were mentioned in a comment ({0}). Read the full issue or PR (description, diff, recent comments, CI status) and respond. If they''re requesting changes, make the changes, commit, and push. If they''re asking a question, answer it.',
+ 'You were mentioned in a comment ({0}). Read the full issue or PR (description, diff, recent comments, CI status) and respond. If they''re requesting changes, make the changes, commit, and push. If they''re asking a question, answer it. When suggesting code changes on a PR, use the review-pr skill for inline suggestions.',
github.event.comment.html_url
)
|| format(
- 'A user commented on an issue/PR where you previously participated ({0}). Read the full context (description, recent comments, CI status). Only respond if the comment is directed at you, asks a question you can help with, or requests changes you can make. If the conversation is between humans and doesn''t need your input, exit silently without commenting. Note: if you are the author of the PR or issue, commenters are probably expecting the author to engage — lean toward responding.',
+ 'A user commented on an issue/PR where you previously participated ({0}). Read the full context (description, recent comments, CI status). Only respond if the comment is directed at you, asks a question you can help with, or requests changes you can make. If the conversation is between humans and doesn''t need your input, exit silently without commenting. Note: if you are the author of the PR or issue, commenters are probably expecting the author to engage — lean toward responding. When suggesting code changes on a PR, use the review-pr skill for inline suggestions.',
github.event.comment.html_url
))
|| format(