Skip to content

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

feat: add automated issue triage workflow and skill (#1071)

Maximilian Roosb7a9cc1ce9d8
diff --git a/.claude/skills/issue-triage/SKILL.md b/.claude/skills/issue-triage/SKILL.md
new file mode 100644
index 000000000..41ea77397
--- /dev/null
+++ b/.claude/skills/issue-triage/SKILL.md
@@ -0,0 +1,206 @@
+---
+name: issue-triage
+description: Triages new GitHub issues — classifies, reproduces bugs, attempts conservative fixes, and comments. Use when a new issue is opened and needs automated triage.
+argument-hint: "[issue number]"
+---
+
+# Issue Triage
+
+Triage a newly opened GitHub issue on this project (a Rust CLI tool for
+managing git worktrees).
+
+**Issue to triage:** $ARGUMENTS
+
+## Step 1: Setup
+
+Load `/running-in-ci` first (CI environment rules, security).
+
+Follow the AD FONTES principle throughout: reproduce before fixing, evidence
+before speculation, test before committing.
+
+## Step 2: Read and classify the issue
+
+```bash
+gh issue view $ARGUMENTS --json title,body,labels,author
+```
+
+Classify into one of:
+
+- **Bug report** — describes unexpected behavior, includes steps to reproduce or
+ error output
+- **Feature request** — asks for new functionality or behavior changes
+- **Question** — asks how to do something or how something works
+- **Other** — doesn't fit the above categories
+
+If not a bug report, skip to step 6 (comment only).
+
+## Step 3: Check for duplicates
+
+Before doing any work, check if this issue is already being addressed:
+
+```bash
+# Search open issues for similar problems
+gh issue list --state open --json number,title,labels --limit 50
+
+# Check for existing fix branches
+git branch -r --list 'origin/fix/issue-*'
+git branch -r --list 'origin/repro/issue-*'
+
+# Check open PRs
+gh pr list --state open --json number,title,headRefName --limit 50
+```
+
+If a duplicate or existing fix is found, note it for the comment in step 6.
+Don't create a duplicate fix.
+
+## Step 4: Reproduce the bug
+
+Follow the AD FONTES principle — reproduce before fixing:
+
+1. **Understand the report** — What command was run? What was expected? What
+ actually happened?
+2. **Find relevant code** — Search the codebase for the functionality described
+3. **Write a failing test** — Add a test to the appropriate *existing* test file
+ that demonstrates the bug. Don't create new test files.
+4. **Run the test** to confirm it fails:
+ ```bash
+ cargo test --lib --bins -- test_name
+ # or for integration tests:
+ cargo test --test integration -- test_name
+ ```
+
+If the test passes (bug may already be fixed), note this for the comment.
+
+If you cannot reproduce the bug (unclear steps, environment-specific, etc.),
+note what you tried and skip to step 6.
+
+## Step 5: Fix (conservative)
+
+**Only attempt a fix if ALL of these conditions are met:**
+
+- Bug is clearly reproducible (test fails)
+- Root cause is understood
+- Fix is localized (1-3 files changed)
+- Confident the fix is correct
+
+### If fixing
+
+1. Fix the root cause (not just the symptom)
+2. Confirm the test now passes
+3. Run the full test suite and lints:
+ ```bash
+ cargo run -- hook pre-merge --yes
+ ```
+4. Create branch, commit, push, and create PR:
+ ```bash
+ git checkout -b fix/issue-$ARGUMENTS
+ git add -A
+ git commit -m "fix: <description>
+
+ Closes #$ARGUMENTS
+
+ Co-authored-by: Claude <[email protected]>"
+ git push -u origin fix/issue-$ARGUMENTS
+ gh pr create --title "fix: <description>" --label "automated-fix" --body "## Problem
+ [What the issue reported and the root cause]
+
+ ## Solution
+ [What was fixed and why]
+
+ ## Testing
+ [How the fix was verified — mention the reproduction test]
+
+ ---
+ Automated triage for #<issue-number>"
+ ```
+5. Monitor CI until green:
+ ```bash
+ gh run list --branch fix/issue-$ARGUMENTS
+ gh run watch
+ ```
+ If CI fails, diagnose with `gh run view <run-id> --log-failed`, fix, and
+ repeat.
+
+### If reproduction test works but fix is not confident
+
+Commit just the failing test on a reproduction branch and open a PR:
+
+```bash
+git checkout -b repro/issue-$ARGUMENTS
+git add -A
+git commit -m "test: add reproduction for #$ARGUMENTS
+
+Co-authored-by: Claude <[email protected]>"
+git push -u origin repro/issue-$ARGUMENTS
+gh pr create --title "test: reproduction for #$ARGUMENTS" --label "automated-fix" --body "## Context
+Adds a failing test that reproduces #$ARGUMENTS. The fix is not yet included —
+this PR captures the reproduction so a maintainer can investigate.
+
+---
+Automated triage for #<issue-number>"
+```
+
+Note the PR number for the comment.
+
+## Step 6: Comment on the issue
+
+Always comment via `gh issue comment`. Keep it brief, polite, and specific. A
+maintainer will always review — never claim the issue is fully resolved by
+automation alone.
+
+Choose the appropriate template:
+
+### Fix PR created
+
+> Thanks for reporting this! I was able to reproduce the issue and identified
+> the root cause: [one-sentence explanation].
+>
+> I've opened #PR_NUMBER with a fix. A maintainer will review it shortly.
+
+### Reproduction test only (no fix attempted)
+
+> Thanks for reporting this! I was able to reproduce the issue — #PR_NUMBER
+> adds a failing test that demonstrates the bug.
+>
+> Root cause appears to be [brief explanation if known, or "still under
+> investigation"]. A maintainer will take a closer look.
+
+### Could not reproduce
+
+> Thanks for reporting this! I tried to reproduce this but wasn't able to with
+> the information provided.
+>
+> Could you share [specific information needed — exact command, config file,
+> git repo structure, OS, shell, etc.]? That would help narrow it down.
+>
+> A maintainer will also take a look.
+
+### Bug already fixed
+
+> Thanks for reporting this! I looked into this and it appears the behavior
+> described may already be fixed on `main` (the relevant test passes).
+>
+> Could you confirm which version you're running (`wt --version`)? If you're
+> on an older release, updating should resolve this. A maintainer will
+> confirm.
+
+### Feature request
+
+> Thanks for the suggestion! This is a feature request rather than a bug, so
+> I'll leave it for a maintainer to evaluate and prioritize.
+
+### Question
+
+> Thanks for reaching out! This looks like a usage question rather than a bug
+> report.
+>
+> [Brief answer if obvious from the codebase, or pointer to relevant docs/help
+> text.]
+>
+> A maintainer can provide more detail if needed.
+
+### Duplicate
+
+> Thanks for reporting this! This appears to be related to #EXISTING_ISSUE
+> [and/or PR #EXISTING_PR]. I'll leave it to a maintainer to confirm and
+> link them.
diff --git a/.github/workflows/claude-issue-triage.yaml b/.github/workflows/claude-issue-triage.yaml
new file mode 100644
index 000000000..a5b1a7449
--- /dev/null
+++ b/.github/workflows/claude-issue-triage.yaml
@@ -0,0 +1,95 @@
+name: claude-issue-triage
+# Runner versions pinned; see ci.yaml header comment for rationale.
+
+# Automatic triage when new issues are opened.
+on:
+ issues:
+ types: [opened]
+
+concurrency:
+ group: ${{ github.workflow }}-${{ github.event.issue.number }}
+ cancel-in-progress: true
+
+# Consistent with ci.yaml for cache compatibility
+env:
+ CARGO_TERM_COLOR: always
+ CLICOLOR_FORCE: 1
+ RUSTFLAGS: "-C debuginfo=0"
+ RUSTDOCFLAGS: "-Dwarnings"
+
+jobs:
+ triage:
+ # Skip bot-created issues and @claude mentions (handled by claude-mention.yaml)
+ if: >-
+ github.event.issue.user.type != 'Bot' &&
+ !contains(github.event.issue.body, '@claude') &&
+ !contains(github.event.issue.title, '@claude')
+ runs-on: ubuntu-24.04
+ permissions:
+ contents: write
+ pull-requests: write
+ issues: write
+ id-token: write
+ actions: read
+ steps:
+ - name: 📂 Checkout code
+ uses: actions/checkout@v6
+ with:
+ ref: main
+ fetch-depth: 0
+ fetch-tags: true
+ # Use bot token so pushed commits trigger CI workflows
+ token: ${{ secrets.WORKTRUNK_BOT_TOKEN }}
+
+ - name: 🔧 Configure git for Claude
+ run: |
+ git config --global user.name "Claude Code"
+ git config --global user.email "[email protected]"
+
+ - name: Install cargo-insta
+ uses: baptiste0928/cargo-install@v3
+ with:
+ crate: cargo-insta
+
+ - name: Install cargo-nextest
+ uses: baptiste0928/cargo-install@v3
+ with:
+ crate: cargo-nextest
+
+ - name: 💰 Cache
+ uses: Swatinem/rust-cache@v2
+ with:
+ prefix-key: ${{ hashFiles('Cargo.lock') }}
+ save-if: false
+
+ - name: Install shells (zsh, fish)
+ run: |
+ sudo apt-get update
+ sudo apt-get install -y zsh fish
+
+ - name: 🤖 Run Claude Code to triage issue
+ id: claude
+ uses: anthropics/claude-code-action@v1
+ with:
+ claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+ # Use bot token so pushed commits trigger CI workflows
+ github_token: ${{ secrets.WORKTRUNK_BOT_TOKEN }}
+ additional_permissions: |
+ actions: read
+
+ prompt: |
+ Use /issue-triage ${{ github.event.issue.number }}
+
+ claude_args: |
+ --model opus
+ --allowedTools Bash,Edit,Read,Write,Glob,Grep,WebSearch,WebFetch,Task,Skill
+ --append-system-prompt "You are operating in a GitHub Actions CI environment. Use /running-in-ci before starting work."
+
+ - name: 📋 Upload Claude Code session logs
+ if: always()
+ uses: actions/upload-artifact@v6
+ with:
+ name: claude-session-logs
+ path: ~/.claude/
+ retention-days: 30
+ if-no-files-found: warn