claude-code-setup
An official Claude Code plugin from Anthropic that analyzes a codebase and provides tailored recommendations for Claude Code automation configuration, covering Hooks, Subagents, Skills, MCP Servers, and Plugins. It operates in read-only mode and does not modify files.
Timeline (last 90 days)
The recommended scope of claude-code-setup covers five categories: Hooks, Subagents, Skills, MCP Servers, and Plugins.
claude-code-setup is read-only and never creates or modifies any files.
By default, claude-code-setup gives only 1-2 suggestions per category, expanding to 3-5 when the user explicitly requests a certain category.
claude-code-setup infers the project type and toolchain by reading files such as package.json and the directory structure.
In Claude Code, the command to install the claude-code-setup plugin is /plugin install claude-code-setup@claude-plugins-official.
claude-code-setup suggested a PostToolUse hook for this project: after each edit to files under src/, automatically run npx jest --findRelatedTests to run only the related tests.
claude-code-setup suggested a PreToolUse hook for this project that blocks direct editing of version-management-related files (manifest.json, src/version.js, package-lock.json, coverage/), because the project synchronizes the version numbers of three files via npm run version:*.
claude-code-setup suggested creating two Skills for this project: release (triggered only by the user) and netflix-dom-check (Claude-only background knowledge).
claude-code-setup recommended two Subagents for this project, extension-security-reviewer (targeting host_permissions of MV3 extensions, XSS risks in DOM operations, and missing validation in message passing) and service-worker-reviewer, the latter based on the fact that PR #1 in the repository previously fixed a Service Worker issue after PC sleep.
The reason claude-code-setup recommends Playwright MCP is that Jest runs on jsdom and cannot verify real popup UI and content script behavior.
1 more timeline events
All Facts (11)
The recommended scope of claude-code-setup covers five categories: Hooks, Subagents, Skills, MCP Servers, and Plugins.
50%Unverifiedclaude-code-setup is read-only and never creates or modifies any files.
50%UnverifiedBy default, claude-code-setup gives only 1-2 suggestions per category, expanding to 3-5 when the user explicitly requests a certain category.
50%Unverifiedclaude-code-setup infers the project type and toolchain by reading files such as package.json and the directory structure.
50%UnverifiedIn Claude Code, the command to install the claude-code-setup plugin is /plugin install claude-code-setup@claude-plugins-official.
50%Unverifiedclaude-code-setup suggested a PostToolUse hook for this project: after each edit to files under src/, automatically run npx jest --findRelatedTests to run only the related tests.
50%Unverifiedclaude-code-setup suggested a PreToolUse hook for this project that blocks direct editing of version-management-related files (manifest.json, src/version.js, package-lock.json, coverage/), because the project synchronizes the version numbers of three files via npm run version:*.
50%Unverifiedclaude-code-setup suggested creating two Skills for this project: release (triggered only by the user) and netflix-dom-check (Claude-only background knowledge).
50%Unverifiedclaude-code-setup recommended two Subagents for this project, extension-security-reviewer (targeting host_permissions of MV3 extensions, XSS risks in DOM operations, and missing validation in message passing) and service-worker-reviewer, the latter based on the fact that PR #1 in the repository previously fixed a Service Worker issue after PC sleep.
50%UnverifiedThe reason claude-code-setup recommends Playwright MCP is that Jest runs on jsdom and cannot verify real popup UI and content script behavior.
50%UnverifiedThe first suggestion claude-code-setup gave itself is to first create CLAUDE.md, recording how npm test is run, the version synchronization rules, and the role of .kiro/specs.
50%