Add Hello World to README

Added a simple Hello World message to the README.

CHANGELOG.md

@@ -1,41 +1,5 @@
 # Changelog
 
-## 2.0.69
-
-- Minor bugfixes
-
-## 2.0.68
-
-- Fixed IME (Input Method Editor) support for languages like Chinese, Japanese, and Korean by correctly positioning the composition window at the cursor
-- Fixed a bug where disallowed MCP tools were visible to the model
-- Fixed an issue where steering messages could be lost while a subagent is working
-- Fixed Option+Arrow word navigation treating entire CJK (Chinese, Japanese, Korean) text sequences as a single word instead of navigating by word boundaries
-- Improved plan mode exit UX: show simplified yes/no dialog when exiting with empty or missing plan instead of throwing an error
-- Add support for enterprise managed settings. Contact your Anthropic account team to enable this feature.
-
-## 2.0.67
-
-- Thinking mode is now enabled by default for Opus 4.5
-- Thinking mode configuration has moved to /config
-- Added search functionality to `/permissions` command with `/` keyboard shortcut for filtering rules by tool name
-- Show reason why autoupdater is disabled in `/doctor`
-- Fixed false "Another process is currently updating Claude" error when running `claude update` while another instance is already on the latest version
-- Fixed MCP servers from `.mcp.json` being stuck in pending state when running in non-interactive mode (`-p` flag or piped input)
-- Fixed scroll position resetting after deleting a permission rule in `/permissions`
-- Fixed word deletion (opt+delete) and word navigation (opt+arrow) not working correctly with non-Latin text such as Cyrillic, Greek, Arabic, Hebrew, Thai, and Chinese
-- Fixed `claude install --force` not bypassing stale lock files
-- Fixed consecutive @~/ file references in CLAUDE.md being incorrectly parsed due to markdown strikethrough interference
-- Windows: Fixed plugin MCP servers failing due to colons in log directory paths
-
-## 2.0.65
-
-- Added ability to switch models while writing a prompt using alt+p (linux, windows), option+p (macos).
-- Added context window information to status line input
-- Added `fileSuggestion` setting for custom `@` file search commands
-- Added `CLAUDE_CODE_SHELL` environment variable to override automatic shell detection (useful when login shell differs from actual working shell)
-- Fixed prompt not being saved to history when aborting a query with Escape
-- Fixed Read tool image handling to identify format from bytes instead of file extension
-
 ## 2.0.64
 
 - Made auto-compacting instant
@@ -50,7 +14,6 @@
 - VSCode: Added copy-to-clipboard button on code blocks and bash tool inputs
 - VSCode: Fixed extension not working on Windows ARM64 by falling back to x64 binary via emulation
 - Bedrock: Improve efficiency of token counting
-- Bedrock: Add support for `aws login` AWS Management Console credentials
 - Unshipped AgentOutputTool and BashOutputTool, in favor of a new unified TaskOutputTool
 
 ## 2.0.62

README.md

@@ -6,6 +6,8 @@
 
 Claude Code is an agentic coding tool that lives in your terminal, understands your codebase, and helps you code faster by executing routine tasks, explaining complex code, and handling git workflows -- all through natural language commands. Use it in your terminal, IDE, or tag @claude on Github.
 
+Hello World
+
 **Learn more in the [official documentation](https://docs.anthropic.com/en/docs/claude-code/overview)**.
 
 <img src="./demo.gif" />

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

@@ -93,6 +93,11 @@ Found 3 issues:
 
 <link to file and line with full sha1 + line range for context>
 
+🤖 Generated with [Claude Code](https://claude.ai/code)
+
+
+<sub>- If this code review was useful, please react with 👍. Otherwise, react with 👎.</sub>
+
 ---
 
 - Or, if you found no issues:
@@ -103,6 +108,8 @@ Found 3 issues:
 
 No issues found. Checked for bugs and CLAUDE.md compliance.
 
+🤖 Generated with [Claude Code](https://claude.ai/code)
+
 ---
 
 - 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

plugins/plan-auto-show/README.md

@@ -1,45 +0,0 @@
-# Plan Auto-Show Plugin
-
-Automatically displays the plan content when it's updated in plan mode, eliminating the need to type `/plan` to preview changes.
-
-## Problem
-
-When in plan mode, Claude updates the plan file and may ask follow-up questions. Users can't see the plan without typing `/plan`, but they also can't type `/plan` while being asked questions - they need to respond to the questions first.
-
-## Solution
-
-This plugin instructs Claude to automatically display the plan content in its response whenever it updates the plan file. The plan is shown before any follow-up questions, giving users the context they need to answer.
-
-## Installation
-
-1. Enable the plugin in your Claude Code settings
-2. The SessionStart hook will automatically add instructions for plan auto-display
-
-## How It Works
-
-The plugin adds a SessionStart hook that provides additional context to Claude:
-- After updating the plan file, Claude will display the full plan content
-- The plan is shown in a markdown code block
-- The plan appears before any follow-up questions
-
-## Example
-
-Before this plugin:
-```
-Claude: I've updated the plan file. Would you prefer approach A or B?
-User: (Can't see the plan without typing /plan, but needs to answer the question)
-```
-
-After this plugin:
-```
-Claude: I've updated the plan file:
-
-## Current Plan
-1. Implement feature X
-2. Add tests
-3. Deploy
-
-Would you prefer approach A or B?
-
-User: (Can see the plan and answer the question)
-```

plugins/plan-auto-show/hooks/session-start.sh

@@ -1,15 +0,0 @@
-#!/usr/bin/env bash
-
-# Auto-show plan content after updates in plan mode
-# This hook adds instructions to automatically display the plan when updated
-
-cat << 'EOF'
-{
-  "hookSpecificOutput": {
-    "hookEventName": "SessionStart",
-    "additionalContext": "## Plan Mode Auto-Display\n\nWhen you are in plan mode and you update the plan file:\n\n1. After writing or editing the plan file, ALWAYS display the full plan content in a markdown code block in your response\n2. Use the format:\n   ```markdown\n   ## Current Plan\n   [full plan content here]\n   ```\n3. This ensures the user can see the plan without needing to run `/plan`, which is especially important when you're asking follow-up questions\n4. Show the plan BEFORE asking any clarifying questions, so the user has context for their answers\n\nThis improves the user experience by making the plan visible immediately after updates, without requiring separate commands."
-  }
-}
-EOF
-
-exit 0

plugins/plan-auto-show/settings.json

@@ -1,15 +0,0 @@
-{
-  "hooks": {
-    "SessionStart": [
-      {
-        "matcher": "*",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "bash ${CLAUDE_PLUGIN_ROOT}/hooks/session-start.sh"
-          }
-        ]
-      }
-    ]
-  }
-}