fix(development-pr-workflow): correct Linear MCP tool name, drop git add -A, bump to 2.4.0

Opus 5 migration, remaining broken references plus the mandatory version bump:

- start-linear-task, linear-task-and-pr-from-changes: `mcp__linear__create_issue`
  does not exist. Verified against the live Linear MCP tool list: the real name
  is `save_issue`. `get_user`, `get_issue`, `list_teams`, `list_projects` and
  `list_issue_labels` alongside it are all real and left alone
- linear-task-and-pr-from-changes: `git add -A` replaced with explicit per-file
  staging, with the reason inline so it does not get reverted
- start-linear-task: the `--skip-graphite` example flag is not in the command's
  own argument table; corrected to `--use-graphite false`
- update-graphite-stack: two references to a `pr-issue-resolver` skill that does
  not exist (the skill is `resolve-pr-issues`); removed the optional
  refactorer-agent "verify changes maintain quality" follow-up pass
- pr-guide: concurrency cap on the inline-comment path, matching SKILL.md
- both Linear commands: decorative CRITICAL/ALL-CAPS emphasis softened, wording
  otherwise unchanged
- plugin.json 2.3.0 -> 2.4.0 and the matching root CLAUDE.md row. Both read
  2.3.0 before this change, so they were already in agreement

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Author: wkoutre

CLAUDE.md

@@ -226,7 +226,7 @@ All plugins follow semantic versioning (semver). Key versioning rules:
 | claude-setup               | 1.0.5   |
 | development-codebase-tools | 2.6.2   |
 | development-planning       | 2.0.7   |
-| development-pr-workflow    | 2.3.0   |
+| development-pr-workflow    | 2.4.0   |
 | development-productivity   | 2.4.1   |
 | skill-management           | 1.2.0   |
 | spec-workflow              | 2.0.1   |

packages/plugins/development-pr-workflow/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "development-pr-workflow",
-  "version": "2.3.0",
+  "version": "2.4.0",
   "description": "Pull request review, issue resolution, and Graphite stack management",
   "author": {
     "name": "Uniswap Labs",

packages/plugins/development-pr-workflow/commands/linear-task-and-pr-from-changes.md

@@ -1,7 +1,7 @@
 ---
 description: Take local changes, create a Linear task, create a branch (optionally in a worktree), commit, and publish a PR
 argument-hint: [--team <id>] [--trunk <branch>] [--create-worktree] [--use-graphite true/false]
-allowed-tools: Bash(*), Read(*), Write(*), AskUserQuestion(*), mcp__graphite__run_gt_cmd(*), mcp__github__create_pull_request(*), mcp__linear__create_issue(*), mcp__linear__get_user(*), mcp__linear__list_teams(*), mcp__linear__list_projects(*), mcp__linear__list_issue_labels(*)
+allowed-tools: Bash(*), Read(*), Write(*), AskUserQuestion(*), mcp__graphite__run_gt_cmd(*), mcp__github__create_pull_request(*), mcp__linear__save_issue(*), mcp__linear__get_user(*), mcp__linear__list_teams(*), mcp__linear__list_projects(*), mcp__linear__list_issue_labels(*)
 ---
 
 # Changes to PR Workflow
@@ -123,7 +123,7 @@ As a [user type], I want [goal/capability] so that [benefit/value].
 
 ### Phase 1: Fetch Linear User and Teams (REQUIRED)
 
-**CRITICAL: Before presenting ANY prompts, you MUST fetch the Linear user to get the username for branch prefix options.**
+**Fetch the Linear user before presenting any prompts** — the username supplies the branch-prefix options.
 
 ```
 # Get current Linear user (for assignee and username prefix)
@@ -150,7 +150,7 @@ Follow the shared configuration collection instructions in `@../shared/linear-ta
 - `TRUNK_BRANCH` from `--trunk` (if provided)
 - `DUE_DATE` from `--due-date` (if provided)
 
-**IMPORTANT: When prompting for branch prefix, the first option MUST be the user's personal namespace:**
+**When prompting for branch prefix, the first option is the user's personal namespace:**
 
 ```
 Branch Prefix options:
@@ -185,7 +185,7 @@ Include these additional questions in the Phase 1 prompt from the shared config:
 Use the Linear MCP to create the task with the **auto-generated user story description** from Step 1.5:
 
 ```
-mcp__linear__create_issue with:
+mcp__linear__save_issue with:
 - team: <selected team>
 - title: <task title - auto-generated or user-provided>
 - description: <AUTO-GENERATED user story from Step 1.5>
@@ -303,9 +303,14 @@ Resolves: <LINEAR-ISSUE-ID>
 
 ## Step 6: Commit Changes
 
+Stage the files this task actually changed, named individually. Never `git add -A` or
+`git add .` — a blanket stage sweeps in untracked secrets, local scratch files, and
+unrelated in-progress work, and it is not obvious from the commit that it happened.
+
 ```bash
 cd "$WORKING_DIR"
-git add -A
+git status --short          # confirm what is present before staging
+git add path/to/file-one path/to/file-two
 SKIP_CLAUDE=1 git commit -m "<generated commit message>"
 ```
 

packages/plugins/development-pr-workflow/commands/start-linear-task.md

@@ -1,7 +1,7 @@
 ---
 description: Start working on a new Linear task by creating a worktree environment. Either provide an existing Linear ticket ID or describe the work to create a new task.
 argument-hint: [<ticket-id> | --prompt "<description>"] [--team <id>] [--trunk <branch>] [--use-graphite true/false] [--start-working] [--start-prompt "<prompt>"]
-allowed-tools: Bash(*), Read(*), Write(*), AskUserQuestion(*), mcp__graphite__run_gt_cmd(*), mcp__github__create_pull_request(*), mcp__linear__create_issue(*), mcp__linear__get_issue(*), mcp__linear__get_user(*), mcp__linear__list_teams(*), mcp__linear__list_projects(*), mcp__linear__list_issue_labels(*)
+allowed-tools: Bash(*), Read(*), Write(*), AskUserQuestion(*), mcp__graphite__run_gt_cmd(*), mcp__github__create_pull_request(*), mcp__linear__save_issue(*), mcp__linear__get_issue(*), mcp__linear__get_user(*), mcp__linear__list_teams(*), mcp__linear__list_projects(*), mcp__linear__list_issue_labels(*)
 ---
 
 # Start Linear Task Workflow
@@ -90,7 +90,7 @@ AskUserQuestion:
 
 ### Phase 2: Fetch Linear User and Teams (REQUIRED)
 
-**CRITICAL: Before presenting ANY prompts, you MUST fetch the Linear user to get the username for branch prefix options.**
+**Fetch the Linear user before presenting any prompts** — the username supplies the branch-prefix options.
 
 ```
 # Get current Linear user (for assignee and username prefix)
@@ -118,7 +118,7 @@ Follow the shared configuration collection instructions in `@../shared/linear-ta
 - `WORKTREE_BASE` from `--worktree_base` (if provided)
 - `DUE_DATE` from `--due-date` (if provided)
 
-**IMPORTANT: When prompting for branch prefix, the first option MUST be the user's personal namespace:**
+**When prompting for branch prefix, the first option is the user's personal namespace:**
 
 ```
 Branch Prefix options:
@@ -187,7 +187,7 @@ As a [user type], I want [goal/capability] so that [benefit/value].
 **Create the task:**
 
 ```
-mcp__linear__create_issue with:
+mcp__linear__save_issue with:
 - team: TEAM
 - title: <generated from PROMPT or user-provided>
 - description: <generated user story>
@@ -403,7 +403,7 @@ Or with Graphite (if USE_GRAPHITE was enabled):
 ### With full configuration
 
 ```
-/start-linear-task DEV-456 --trunk develop --branch-prefix feature --skip-graphite
+/start-linear-task DEV-456 --trunk develop --branch-prefix feature --use-graphite false
 ```
 
 ### Interactive mode (no arguments)

packages/plugins/development-pr-workflow/skills/resolve-pr-issues/pr-guide.md

@@ -201,7 +201,7 @@ Use the inline comment as the canonical item (it has file/line context). Discard
 
 | Item Type                              | Agent                                            | Notes                                                                |
 | -------------------------------------- | ------------------------------------------------ | -------------------------------------------------------------------- |
-| Inline comments (grouped by file)      | `development-pr-workflow:comment-resolver-agent` | One agent per file group                                             |
+| Inline comments (grouped by file)      | `development-pr-workflow:comment-resolver-agent` | One agent per file group; cap at 3 concurrent agents                 |
 | Review body items (with file location) | `development-pr-workflow:comment-resolver-agent` | Grouped with that file's inline comments                             |
 | Review body items (no file location)   | `development-pr-workflow:comment-resolver-agent` | Batch up to 3 items per agent; receives full PR diff                 |
 | CI failures (specific file)            | `development-pr-workflow:comment-resolver-agent` | Include CI logs in prompt                                            |

packages/plugins/development-pr-workflow/skills/update-graphite-stack/SKILL.md

@@ -8,7 +8,7 @@ model: opus
 
 Automate Graphite PR stack updates by resolving comments and syncing PRs.
 
-> **Note:** This skill requires Graphite CLI (`gt`) as PR stacking is a Graphite-specific concept. For standard Git workflows, use the `pr-issue-resolver` skill to address PR comments on individual PRs.
+> **Note:** This skill requires Graphite CLI (`gt`) as PR stacking is a Graphite-specific concept. For standard Git workflows, use the `resolve-pr-issues` skill to address PR comments on individual PRs.
 
 ## When to Activate
 
@@ -24,7 +24,7 @@ Automate Graphite PR stack updates by resolving comments and syncing PRs.
 - **Repository initialized** with Graphite: `gt repo init`
 - **Existing Graphite stack** with PRs to update
 
-> **Why Graphite-only?** This skill manages PR stacks, which is a Graphite-specific workflow. For standard Git workflows, use `pr-issue-resolver` to address comments on individual PRs.
+> **Why Graphite-only?** This skill manages PR stacks, which is a Graphite-specific workflow. For standard Git workflows, use `resolve-pr-issues` to address comments on individual PRs.
 
 ## What It Does
 
@@ -68,10 +68,6 @@ Progress summary with:
 - Remaining unresolved items
 - Stack synchronization status
 
-## Optional Follow-up
-
-After updates, can invoke **refactorer-agent** to verify changes maintain quality.
-
 ## Examples
 
 ```