메뉴
Use when Claude Code is not reliably opening MCP session turns, running MCP stop gates, or running MCP post-tool verification on every request. Installs the MCP plugin hook chain into the active Claude settings file.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when the user asks to "start session", "log session", "begin turn", "update turn", "complete turn", or "query session history"
Use when asked to "wrap up", "export requirements", or "close out" MCP-backed work: reconcile MCP requirements, export wiki documents, run validation, commit and push with an appropriate commit message, reconcile the session log, and complete the turn.
Use when the user asks to "ingest text into graphrag", "add document to knowledge graph", "create entity", "create relationship", "query knowledge graph", "list graph entities", "delete document"
Use when the user asks to "list requirements", "add requirement", "create FR", "create TR", "create test requirement", "generate requirements document", or "ingest requirements".
Use when the user asks to "create a todo", "list todos", "update todo", "query tasks", "check todo status", "plan implementation", or "mark todo done".
Use when an MCP workspace marker tells Claude Code to validate active MCP hook enforcement. Verifies active Claude settings and installs missing MCP hooks through the claude-hook-wiring skill.
| name | Claude MCP Hook Wiring |
| description | Use when Claude Code is not reliably opening MCP session turns, running MCP stop gates, or running MCP post-tool verification on every request. Installs the MCP plugin hook chain into the active Claude settings file. |
Claude Code can have the McpServer plugin installed while the active Claude settings file still does not invoke the plugin hooks. This skill wires the MCP hooks directly into the active Claude settings so enforcement is driven by Claude's hook runtime, not by model memory or prompt compliance.
Use this skill when:
hooks/hooks.json exists in the plugin package but the active Claude settings do not run UserPromptSubmit, Stop, or PostToolUse MCP hooks.Do not replace existing user hooks. Merge MCP hook entries into settings.json and preserve existing hook groups such as timestamp hooks, shell blockers, or unrelated workflow hooks.
Run the installer from the Claude plugin root:
pwsh -NoLogo -NoProfile -NonInteractive -File "$env:CLAUDE_PLUGIN_ROOT/skills/claude-hook-wiring/scripts/install-claude-mcp-hooks.ps1"
If CLAUDE_PLUGIN_ROOT is not set, pass the plugin root explicitly:
pwsh -NoLogo -NoProfile -NonInteractive -File "F:/GitHub/mcpserver-claude-code-plugin/skills/claude-hook-wiring/scripts/install-claude-mcp-hooks.ps1" -PluginRoot "F:/GitHub/mcpserver-claude-code-plugin"
The installer reads the plugin's hooks/hooks.json, merges it into the active Claude settings file, and writes a timestamped backup unless -NoBackup is supplied.
After wiring, the active Claude settings must contain MCP entries for:
UserPromptSubmit: opens an MCP session-log turn before Claude starts work.Stop: blocks or auto-closes incomplete turns before Claude emits a final response.PostToolUse: runs plan synchronization and code verification after relevant tool calls.SessionStart, SessionEnd, PreCompact, and PostCompact: maintain session continuity around lifecycle events.After installation:
settings.json and confirm existing hooks are still present.${CLAUDE_PLUGIN_ROOT}/hooks/scripts/user-prompt-submit.ps1, ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/stop-gate.ps1, and ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/code-verify.ps1.PostToolUse runs code verification.If the merge fails, do not claim Claude is enforced. Report the failure and leave the existing settings unchanged by restoring the backup.