prq-cli 0.8.0 → 0.9.0

package/dist/bin/prq.js

@@ -6482,98 +6482,62 @@ Available actions: ${available}`);
 // src/commands/skill.ts
 var SKILL_CONTENT = `---
 name: prq
-description: PR review queue manager. Use when the user wants to check their PR review queue, review PRs, nudge stale PRs, or manage code review workflow. Triggers on mentions of "review queue", "PRs waiting", "stale PRs", "what needs review", or "prq".
+description: PR review queue manager. Use when the user wants to check their PR review queue, review PRs, nudge stale PRs, open PRs, or manage code review workflow. Triggers on mentions of "review queue", "PRs waiting", "stale PRs", "what needs review", "open PR", "nudge", or "prq".
 ---
 
-# PRQ — PR Review Queue
+# PRQ CLI
 
-You have access to the \`prq\` CLI tool installed on this machine. Use it to help the user manage their code review queue.
+\`prq\` is a CLI tool for managing code review queues. It's installed on this machine.
 
-## Step 1: Get the queue
-
-Run this command to get the user's current review queue:
+## Commands
 
 \`\`\`bash
+# Show the review queue (JSON for parsing)
 prq status --json
-\`\`\`
 
-This returns a JSON object with categorized PRs:
-- **needs-re-review** — PRs where the user left a review but new commits were pushed after
-- **requested** — PRs where the user is a requested reviewer
-- **stale** — PRs with no activity for N days
-- **waiting-on-others** — PRs the user authored that are waiting on someone else
+# Open a PR in the browser
+prq open <number>
+prq open <owner/repo#number>
 
-## Step 2: Present the queue
+# Open files changed tab for review
+prq review <number>
 
-Show the results in a clear, scannable format grouped by category. For each PR, show:
-- The category symbol (◆ needs re-review, ● requested, ○ stale, ◇ waiting)
-- The repo and PR number
-- The title
-- The detail (e.g., "new commits since your review 2d ago")
+# Post a nudge comment on a stale PR
+prq nudge <number> --yes
+prq nudge <number> --message "Custom message" --yes
 
-Then ask what the user wants to do.
+# Run any configured action
+prq run <action> <number>
+\`\`\`
 
-## Step 3: Act on PRs
+## JSON output
 
-When the user asks to act on a PR, check the \`.prqrc.json\` file in the current directory (or \`~/.config/prq/config.json\`) for custom actions:
+\`prq status --json\` returns:
 
 \`\`\`json
 {
-  "actions": {
-    "review": "/review {url}",
-    "nudge": "shell:prq nudge {number} --yes"
-  }
+  "user": "caio-pizzol",
+  "prs": [
+    {
+      "category": "needs-re-review",
+      "repo": "org/repo",
+      "number": 2439,
+      "title": "fix: something",
+      "author": "alice",
+      "url": "https://github.com/org/repo/pull/2439",
+      "detail": "New commits since your review 1d ago"
+    }
+  ]
 }
 \`\`\`
 
-### Action resolution
-
-For each action template:
-- **Starts with \`/\`** — it's a Claude Code skill. Invoke it by running the skill with the interpolated value. For example, \`/review https://github.com/org/repo/pull/123\`
-- **Starts with \`shell:\`** — it's a shell command. Run it with the Bash tool. For example, \`prq nudge 123 --yes\`
-- **Otherwise** — treat it as a prompt. Send it as a message.
-
-### Template variables
-
-Replace these in the action template:
-- \`{url}\` — full PR URL
-- \`{number}\` — PR number
-- \`{owner}\` — repo owner
-- \`{repo}\` — repo name
-- \`{title}\` — PR title
-- \`{author}\` — PR author
-
-### Default actions (if no config found)
-
-If no actions are configured, use these defaults:
-- **review** — invoke \`/review {url}\` if the /review skill exists, otherwise run \`prq review {number}\` to open files changed in browser
-- **nudge** — run \`prq nudge {number} --yes\`
-- **open** — run \`prq open {number}\`
-
-## Step 4: Batch operations
-
-If the user says things like "review all needs-re-review PRs" or "nudge all stale PRs":
-
-1. Filter the queue JSON by the requested category
-2. Confirm the list with the user: "I'll review these 3 PRs: #2439, #2380, #2352. Proceed?"
-3. Execute the action on each PR sequentially
-
-## Examples
-
-**User:** "check my review queue"
-→ Run \`prq status --json\`, present results, ask what to do
-
-**User:** "review 2439"
-→ Look up action for "review", interpolate with PR data, execute
-
-**User:** "nudge all stale PRs"
-→ Filter stale PRs from queue, confirm, run nudge on each
+Categories: \`needs-re-review\`, \`requested\`, \`stale\`, \`waiting-on-others\`.
 
-**User:** "what PRs are waiting on me?"
-→ Run \`prq status --json\`, show only needs-re-review and requested categories
+## Usage
 
-**User:** "/prq" with no context
-→ Run \`prq status --json\`, present full queue, ask what to do
+- When the user asks about their review queue, run \`prq status --json\` and present the results grouped by category.
+- When the user asks to open, review, or nudge a PR, use the corresponding \`prq\` command.
+- For batch operations ("nudge all stale PRs"), filter the JSON output and confirm with the user before acting.
 `;
 function skillCommand(global) {
   if (global) {

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "prq-cli",
-	"version": "0.8.0",
+	"version": "0.9.0",
 	"description": "PR Queue — see what code reviews need your attention",
 	"type": "module",
 	"bin": {