docs: Clarify Skills feature vs slash commands in changelog

Update the 2.0.20 changelog entry to explain that:
- Skills is a new feature for specialized capabilities
- The Skill tool also handles slash command invocation
- This is an internal change, not a replacement of slash commands
- Slash commands continue to work the same way for users

This addresses confusion where people thought slash commands were
being replaced with skills.

CHANGELOG.md

@@ -1,5 +1,71 @@
 # Changelog
 
+## 2.0.74
+
+- Added LSP (Language Server Protocol) tool for code intelligence features like go-to-definition, find references, and hover documentation
+- Added `/terminal-setup` support for Kitty, Alacritty, Zed, and Warp terminals
+- Added ctrl+t shortcut in `/theme` to toggle syntax highlighting on/off
+- Added syntax highlighting info to theme picker
+- Added guidance for macOS users when Alt shortcuts fail due to terminal configuration
+- Fixed skill `allowed-tools` not being applied to tools invoked by the skill
+- Fixed Opus 4.5 tip incorrectly showing when user was already using Opus
+- Fixed a potential crash when syntax highlighting isn't initialized correctly
+- Fixed visual bug in `/plugins discover` where list selection indicator showed while search box was focused
+- Fixed macOS keyboard shortcuts to display 'opt' instead of 'alt'
+- Improved `/context` command visualization with grouped skills and agents by source, slash commands, and sorted token count
+- [Windows] Fixed issue with improper rendering
+- [VSCode] Added gift tag pictogram for year-end promotion message
+
+## 2.0.73
+
+- Added clickable `[Image #N]` links that open attached images in the default viewer
+- Added alt-y yank-pop to cycle through kill ring history after ctrl-y yank
+- Added search filtering to the plugin discover screen (type to filter by name, description, or marketplace)
+- Added support for custom session IDs when forking sessions with `--session-id` combined with `--resume` or `--continue` and `--fork-session`
+- Fixed slow input history cycling and race condition that could overwrite text after message submission
+- Improved `/theme` command to open theme picker directly
+- Improved theme picker UI
+- Improved search UX across resume session, permissions, and plugins screens with a unified SearchBox component
+- [VSCode] Added tab icon badges showing pending permissions (blue) and unread completions (orange)
+
+## 2.0.72
+
+- Added Claude in Chrome (Beta) feature that works with the Chrome extension (https://claude.ai/chrome) to let you control your browser directly from Claude Code
+- Reduced terminal flickering
+- Added scannable QR code to mobile app tip for quick app downloads
+- Added loading indicator when resuming conversations for better feedback
+- Fixed `/context` command not respecting custom system prompts in non-interactive mode
+- Fixed order of consecutive Ctrl+K lines when pasting with Ctrl+Y
+- Improved @ mention file suggestion speed (~3x faster in git repositories)
+- Improved file suggestion performance in repos with `.ignore` or `.rgignore` files
+- Improved settings validation errors to be more prominent
+- Changed thinking toggle from Tab to Alt+T to avoid accidental triggers
+
+## 2.0.71
+
+- Added /config toggle to enable/disable prompt suggestions
+- Added `/settings` as an alias for the `/config` command
+- Fixed @ file reference suggestions incorrectly triggering when cursor is in the middle of a path
+- Fixed MCP servers from `.mcp.json` not loading when using `--dangerously-skip-permissions`
+- Fixed permission rules incorrectly rejecting valid bash commands containing shell glob patterns (e.g., `ls *.txt`, `for f in *.png`)
+- Bedrock: Environment variable `ANTHROPIC_BEDROCK_BASE_URL` is now respected for token counting and inference profile listing
+- New syntax highlighting engine for native build
+
+## 2.0.70
+
+- Added Enter key to accept and submit prompt suggestions immediately (tab still accepts for editing)
+- Added wildcard syntax `mcp__server__*` for MCP tool permissions to allow or deny all tools from a server
+- Added auto-update toggle for plugin marketplaces, allowing per-marketplace control over automatic updates
+- Added `current_usage` field to status line input, enabling accurate context window percentage calculations
+- Fixed input being cleared when processing queued commands while the user was typing
+- Fixed prompt suggestions replacing typed input when pressing Tab
+- Fixed diff view not updating when terminal is resized
+- Improved memory usage by 3x for large conversations
+- Improved resolution of stats screenshots copied to clipboard (Ctrl+S) for crisper images
+- Removed # shortcut for quick memory entry (tell Claude to edit your CLAUDE.md instead)
+- Fix thinking mode toggle in /config not persisting correctly
+- Improve UI for file creation permission dialog
+
 ## 2.0.69
 
 - Minor bugfixes
@@ -304,7 +370,7 @@
 
 ## 2.0.20
 
-- Added support for Claude Skills
+- Added support for Claude Skills. Skills are a new feature that provide specialized capabilities and domain knowledge to Claude. The internal "Skill" tool also handles slash command invocation (previously done by the "SlashCommand" tool) - this is an internal change to how Claude invokes your slash commands, not a replacement of slash commands. Slash commands continue to work exactly the same way for users.
 
 ## 2.0.19
 

plugins/code-review/README.md

@@ -22,23 +22,29 @@ Performs automated code review on a pull request using multiple specialized agen
    - **Agent #4**: Analyze git blame/history for context-based issues
 5. Scores each issue 0-100 for confidence level
 6. Filters out issues below 80 confidence threshold
-7. Posts review comment with high-confidence issues only
+7. Outputs review (to terminal by default, or as PR comment with `--comment` flag)
 
 **Usage:**
 ```bash
-/code-review
+/code-review [--comment]
 ```
 
+**Options:**
+- `--comment`: Post the review as a comment on the pull request (default: outputs to terminal only)
+
 **Example workflow:**
 ```bash
-# On a PR branch, run:
+# On a PR branch, run locally (outputs to terminal):
 /code-review
 
+# Post review as PR comment:
+/code-review --comment
+
 # Claude will:
 # - Launch 4 review agents in parallel
 # - Score each issue for confidence
-# - Post comment with issues ≥80 confidence
-# - Skip posting if no high-confidence issues found
+# - Output issues ≥80 confidence (to terminal or PR depending on flag)
+# - Skip if no high-confidence issues found
 ```
 
 **Features:**
@@ -114,17 +120,23 @@ This plugin is included in the Claude Code repository. The command is automatica
 ### Standard PR review workflow:
 ```bash
 # Create PR with changes
+# Run local review (outputs to terminal)
 /code-review
 
 # Review the automated feedback
 # Make any necessary fixes
+
+# Optionally post as PR comment
+/code-review --comment
+
 # Merge when ready
 ```
 
 ### As part of CI/CD:
 ```bash
 # Trigger on PR creation or update
-# Automatically posts review comments
+# Use --comment flag to post review comments
+/code-review --comment
 # Skip if review already exists
 ```
 

plugins/code-review/commands/code-review.md

@@ -1,5 +1,5 @@
 ---
-allowed-tools: Bash(gh issue view:*), Bash(gh search:*), Bash(gh issue list:*), Bash(gh pr comment:*), Bash(gh pr diff:*), Bash(gh pr view:*), Bash(gh pr list:*)
+allowed-tools: Bash(gh issue view:*), Bash(gh search:*), Bash(gh issue list:*), Bash(gh pr comment:*), Bash(gh pr diff:*), Bash(gh pr view:*), Bash(gh pr list:*), mcp__github_inline_comment__create_inline_comment
 description: Code review a pull request
 ---
 
@@ -11,7 +11,7 @@ To do this, follow these steps precisely:
    - The pull request is closed
    - The pull request is a draft
    - The pull request does not need code review (e.g. automated PR, trivial change that is obviously correct)
-   - You have already submitted a code review on this pull request
+   - Claude has already commented on this PR (check `gh pr view <PR> --comments` for comments left by claude)
 
    If any condition is true, stop and do not proceed.
 
@@ -52,12 +52,30 @@ Note: Still review Claude generated PR's.
 
 6. Filter out any issues that were not validated in step 5. This step will give us our list of high signal issues for our review.
 
-7. Finally, comment on the pull request.
-   When writing your comment, follow these guidelines:
-   a. Keep your output brief
-   b. Avoid emojis
-   c. Link and cite relevant code, files, and URLs for each issue
-   d. When citing CLAUDE.md violations, you MUST quote the exact text from CLAUDE.md that is being violated (e.g., CLAUDE.md says: "Use snake_case for variable names")
+7. If issues were found, skip to step 8 to post inline comments directly.
+
+   If NO issues were found, post a summary comment using `gh pr comment` (if `--comment` argument is provided):
+   "No issues found. Checked for bugs and CLAUDE.md compliance."
+
+8. Post inline comments for each issue using `mcp__github_inline_comment__create_inline_comment`:
+   - `path`: the file path
+   - `line` (and `startLine` for ranges): select the buggy lines so the user sees them
+   - `body`: Brief description of the issue (no "Bug:" prefix). For small fixes (up to 5 lines changed), include a committable suggestion:
+     ```suggestion
+     corrected code here
+     ```
+
+     **Suggestions must be COMPLETE.** If a fix requires additional changes elsewhere (e.g., renaming a variable requires updating all usages), do NOT use a suggestion block. The author should be able to click "Commit suggestion" and have a working fix - no followup work required.
+
+     For larger fixes (6+ lines, structural changes, or changes spanning multiple locations), do NOT use suggestion blocks. Instead:
+     1. Describe what the issue is
+     2. Explain the suggested fix at a high level
+     3. Include a copyable prompt for Claude Code that the user can use to fix the issue, formatted as:
+        ```
+        Fix [file:line]: [brief description of issue and suggested fix]
+        ```
+
+   **IMPORTANT: Only post ONE comment per unique issue. Do not post duplicate comments.**
 
 Use this list when evaluating issues in Steps 4 and 5 (these are false positives, do NOT flag):
 
@@ -72,40 +90,18 @@ Notes:
 
 - Use gh CLI to interact with GitHub (e.g., fetch pull requests, create comments). Do not use web fetch.
 - Create a todo list before starting.
-- You must cite and link each issue (e.g., if referring to a CLAUDE.md, include a link to it).
-- For your final comment, follow the following format precisely (assuming for this example that you found 3 issues):
+- You must cite and link each issue in inline comments (e.g., if referring to a CLAUDE.md, include a link to it).
+- If no issues are found, post a comment with the following format:
 
 ---
 
 ## Code review
 
-Found 3 issues:
-
-1. <brief description of bug> (CLAUDE.md says: "<exact quote from CLAUDE.md>")
-
-<link to file and line with full sha1 + line range for context, eg. https://github.com/anthropics/claude-code/blob/1d54823877c4de72b2316a64032a54afc404e619/README.md#L13-L17>
-
-2. <brief description of bug> (some/other/CLAUDE.md says: "<exact quote from CLAUDE.md>")
-
-<link to file and line with full sha1 + line range for context>
-
-3. <brief description of bug> (bug due to <file and code snippet>)
-
-<link to file and line with full sha1 + line range for context>
-
----
-
-- Or, if you found no issues:
-
----
-
-## Auto code review
-
 No issues found. Checked for bugs and CLAUDE.md compliance.
 
 ---
 
-- When linking to code, follow the following format precisely, otherwise the Markdown preview won't render correctly: https://github.com/anthropics/claude-code/blob/c21d3c10bc8e898b7ac1a2d745bdc9bc4e423afe/package.json#L10-L15
+- When linking to code in inline comments, follow the following format precisely, otherwise the Markdown preview won't render correctly: https://github.com/anthropics/claude-code/blob/c21d3c10bc8e898b7ac1a2d745bdc9bc4e423afe/package.json#L10-L15
   - Requires full git sha
   - You must provide the full sha. Commands like `https://github.com/owner/repo/blob/$(git rev-parse HEAD)/foo/bar` will not work, since your comment will be directly rendered in Markdown.
   - Repo name must match the repo you're code reviewing

plugins/plugin-dev/skills/hook-development/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: Hook Development
-description: This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", "teleport hook", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.
+description: This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.
 version: 0.1.0
 ---
 
@@ -239,12 +239,7 @@ Execute when user submits a prompt. Use to add context, validate, or block promp
 
 Execute when Claude Code session begins. Use to load context and set environment.
 
-**Matchers for SessionStart:**
-- `*` - All session starts
-- `teleport` - Only when session started via teleport (web → CLI)
-- `fresh` - Only for fresh sessions (not teleported)
-
-**Example (general context loading):**
+**Example:**
 ```json
 {
   "SessionStart": [
@@ -261,58 +256,12 @@ Execute when Claude Code session begins. Use to load context and set environment
 }
 ```
 
-**Example (teleport-specific setup):**
-```json
-{
-  "SessionStart": [
-    {
-      "matcher": "teleport",
-      "hooks": [
-        {
-          "type": "command",
-          "command": "bash ${CLAUDE_PLUGIN_ROOT}/scripts/post-teleport.sh"
-        }
-      ]
-    }
-  ]
-}
-```
-
-**Example script (post-teleport.sh):**
-```bash
-#!/bin/bash
-cd "$CLAUDE_PROJECT_DIR" || exit 0
-
-# Pull latest changes from the teleported branch
-if [ -d ".git" ]; then
-  echo "🔄 Pulling latest changes..."
-  git pull origin "$(git branch --show-current)" 2>/dev/null || true
-fi
-
-# Install dependencies if needed
-if [ -f "package.json" ]; then
-  echo "📦 Installing dependencies..."
-  npm install --silent
-fi
-
-# Start dev server (example for common workflow)
-if [ -f "package.json" ] && grep -q '"dev"' package.json; then
-  echo "🚀 Starting dev server..."
-  npm run dev &
-fi
-```
-
 **Special capability:** Persist environment variables using `$CLAUDE_ENV_FILE`:
 ```bash
 echo "export PROJECT_TYPE=nodejs" >> "$CLAUDE_ENV_FILE"
 ```
 
-**Teleport-specific input fields:**
-- `is_teleport`: Boolean indicating if this session started via teleport
-- `source`: Where the session came from ("web" or "cli") - only present for teleports
-- `branch`: The git branch that was teleported - only present for teleports
-
-See `examples/load-context.sh` and `examples/post-teleport.sh` for complete examples.
+See `examples/load-context.sh` for complete example.
 
 ### SessionEnd
 
@@ -689,7 +638,7 @@ echo "$output" | jq .
 | UserPromptSubmit | User input | Context, validation |
 | Stop | Agent stopping | Completeness check |
 | SubagentStop | Subagent done | Task validation |
-| SessionStart | Session begins | Context loading (use `teleport` matcher for teleport-specific setup) |
+| SessionStart | Session begins | Context loading |
 | SessionEnd | Session ends | Cleanup, logging |
 | PreCompact | Before compact | Preserve context |
 | Notification | User notified | Logging, reactions |
@@ -730,7 +679,6 @@ Working examples in `examples/`:
 - **`validate-write.sh`** - File write validation example
 - **`validate-bash.sh`** - Bash command validation example
 - **`load-context.sh`** - SessionStart context loading example
-- **`post-teleport.sh`** - SessionStart teleport matcher setup example
 
 ### Utility Scripts
 

plugins/plugin-dev/skills/hook-development/examples/post-teleport.sh

@@ -1,52 +0,0 @@
-#!/bin/bash
-# Example SessionStart hook with "teleport" matcher for setting up environment
-# after teleporting from web to CLI. This script pulls changes, installs
-# dependencies, and starts the dev server.
-
-set -euo pipefail
-
-# Navigate to project directory
-cd "$CLAUDE_PROJECT_DIR" || exit 0
-
-echo "Setting up environment after teleport..."
-
-# Pull latest changes if in a git repository
-if [ -d ".git" ]; then
-  current_branch=$(git branch --show-current)
-  echo "🔄 Pulling latest changes for branch: $current_branch"
-  git pull origin "$current_branch" 2>/dev/null || echo "Could not pull (may be offline or no upstream)"
-fi
-
-# Install dependencies based on project type
-if [ -f "package.json" ]; then
-  echo "📦 Installing Node.js dependencies..."
-  npm install --silent 2>/dev/null || npm install
-fi
-
-if [ -f "requirements.txt" ]; then
-  echo "🐍 Installing Python dependencies..."
-  pip install -r requirements.txt --quiet 2>/dev/null || pip install -r requirements.txt
-fi
-
-if [ -f "Cargo.toml" ]; then
-  echo "🦀 Building Rust project..."
-  cargo build 2>/dev/null || true
-fi
-
-# Start development server if available
-if [ -f "package.json" ]; then
-  # Check for common dev server scripts
-  if grep -q '"dev:staging"' package.json; then
-    echo "🚀 Starting staging dev server..."
-    npm run dev:staging &
-  elif grep -q '"dev"' package.json; then
-    echo "🚀 Starting dev server..."
-    npm run dev &
-  elif grep -q '"start"' package.json; then
-    echo "🚀 Starting server..."
-    npm start &
-  fi
-fi
-
-echo "✅ Teleport complete! Environment ready."
-exit 0

plugins/plugin-dev/skills/hook-development/references/patterns.md

@@ -344,64 +344,3 @@ fi
 - Per-project settings
 - Team-specific rules
 - Dynamic validation criteria
-
-## Pattern 11: Teleport Workflow Automation
-
-Automate setup when teleporting sessions from web to CLI using the `teleport` matcher:
-
-**SessionStart hook with teleport matcher:**
-```json
-{
-  "SessionStart": [
-    {
-      "matcher": "teleport",
-      "hooks": [
-        {
-          "type": "command",
-          "command": "bash ${CLAUDE_PLUGIN_ROOT}/scripts/post-teleport.sh"
-        }
-      ]
-    }
-  ]
-}
-```
-
-**post-teleport.sh:**
-```bash
-#!/bin/bash
-cd "$CLAUDE_PROJECT_DIR" || exit 0
-
-# Pull latest changes
-if [ -d ".git" ]; then
-  echo "🔄 Pulling latest changes..."
-  git pull origin "$(git branch --show-current)" 2>/dev/null || true
-fi
-
-# Install dependencies
-if [ -f "package.json" ]; then
-  echo "📦 Installing dependencies..."
-  npm install --silent
-fi
-
-# Start dev server
-if [ -f "package.json" ] && grep -q '"dev:staging"' package.json; then
-  echo "🚀 Starting staging dev server..."
-  npm run dev:staging &
-elif [ -f "package.json" ] && grep -q '"dev"' package.json; then
-  echo "🚀 Starting dev server..."
-  npm run dev &
-fi
-
-echo "✅ Teleport complete! Environment ready."
-```
-
-**Available matchers for SessionStart:**
-- `*` - All session starts (both fresh and teleported)
-- `teleport` - Only teleported sessions (web → CLI)
-- `fresh` - Only fresh sessions (not teleported)
-
-**Use for:**
-- Seamless web-to-CLI workflow transitions
-- Automatic dev server startup after teleporting
-- Pulling latest changes and installing dependencies
-- Running project-specific setup scripts