1[2 {3 "query": "package this up into a draft pr",4 "should_trigger": true5 },6 {7 "query": "ok the feat/passkeys branch is done — ship it for review",8 "should_trigger": true9 },10 {11 "query": "wrap this branch and send it over to the team for review",
15 "query": "I just finished the PM-23456 work on the autofill prompts, throw together a pull request with the usual template please",
16 "should_trigger": true
17 },
18 {
19 "query": "open a draft pr for me — the branch is fix/sync-crash and it tracks origin already",
20 "should_trigger": true
21 },
22 {
23 "query": "let's get this in front of reviewers — it's the auth middleware rewrite for PM-19002, I want it as a draft",
24 "should_trigger": true
25 },
26 {
27 "query": "draft the PR body for feat/refresh-tokens — I've already pushed the branch, just need a clean description that follows the bitwarden template",
28 "should_trigger": true
29 },
30 {
31 "query": "can you put together a pull request? the bitwarden/clients diff is ready, branch is chore/cleanup-stale-flags",
32 "should_trigger": true
33 },
34 {
35 "query": "this is good to go, push it up to github for review with an ai-review-vnext label",
36 "should_trigger": true
37 },
38 {
39 "query": "I want to open a non-draft PR for PM-12345, what should the title look like and which t: label will it get?",
40 "should_trigger": true
41 },
42 {
43 "query": "address the PR review comments on #1234 — the reviewer flagged a race condition in the session middleware and I want to push back on one of them",
44 "should_trigger": false
45 },
46 {
47 "query": "what's the status of my open PRs in bitwarden/server right now? specifically curious which ones are blocked on reviewers",
48 "should_trigger": false
49 },
50 {
51 "query": "explain how pull requests work in the bitwarden org — I'm new and trying to understand the review process",
52 "should_trigger": false
53 },
54 {
55 "query": "merge PR #4567 in bitwarden/clients, CI is green and I've already approved it",
56 "should_trigger": false
57 },
58 {
59 "query": "close that stale PR from last quarter — the one about the deprecated auth flow, I don't think we're picking it up",
60 "should_trigger": false
61 },
62 {
63 "query": "commit my staged changes with a feat: message about the new passkey enrollment flow",
64 "should_trigger": false
65 },
66 {
67 "query": "what's the right t: label for adding tests to a previously untested service class? is it t:tech-debt or something else?",
68 "should_trigger": false
69 },
70 {
71 "query": "run preflight before I commit — I want to make sure tests pass and the spell check is clean",
72 "should_trigger": false
73 },
74 {
75 "query": "package up this plugin as a .skill file so I can install it on another machine",
76 "should_trigger": false
77 },
78 {
79 "query": "rebase feat/auth-refactor onto main and walk me through any conflicts in the session store",