diff --git a/.claude/settings.json b/.claude/settings.json
deleted file mode 100644
index 1bd167c..0000000
--- a/.claude/settings.json
+++ /dev/null
@@ -1,28 +0,0 @@
-{
-  "hooks": {
-    "PostToolUse": [
-      {
-        "matcher": "Edit|Write|Bash",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "git rev-parse --git-dir >/dev/null 2>&1 && code-review-graph update --skip-flows --repo \"/Users/liulujian/Documents/code/TopFansByGithub\" || true",
-            "timeout": 30
-          }
-        ]
-      }
-    ],
-    "SessionStart": [
-      {
-        "matcher": "",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "git rev-parse --git-dir >/dev/null 2>&1 && code-review-graph status --repo \"/Users/liulujian/Documents/code/TopFansByGithub\" || echo 'Not a git repo, skipping'",
-            "timeout": 10
-          }
-        ]
-      }
-    ]
-  }
-}
diff --git a/.claude/settings.local.json b/.claude/settings.local.json
deleted file mode 100644
index 443a56a..0000000
--- a/.claude/settings.local.json
+++ /dev/null
@@ -1,16 +0,0 @@
-{
-  "permissions": {
-    "allow": [
-      "Skill(superpowers:subagent-driven-development)",
-      "Skill(superpowers:subagent-driven-development:*)",
-      "Bash(go build:*)",
-      "Bash(go vet:*)",
-      "mcp__code-review-graph__semantic_search_nodes_tool",
-      "Skill(superpowers:brainstorming)"
-    ]
-  },
-  "enableAllProjectMcpServers": true,
-  "enabledMcpjsonServers": [
-    "code-review-graph"
-  ]
-}
diff --git a/.claude/skills/debug-issue/skill.md b/.claude/skills/debug-issue/skill.md
deleted file mode 100644
index ef1b38a..0000000
--- a/.claude/skills/debug-issue/skill.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-name: Debug Issue
-description: Systematically debug issues using graph-powered code navigation
----
-
-## Debug Issue
-
-Use the knowledge graph to systematically trace and debug issues.
-
-### Steps
-
-1. Use `semantic_search_nodes` to find code related to the issue.
-2. Use `query_graph` with `callers_of` and `callees_of` to trace call chains.
-3. Use `get_flow` to see full execution paths through suspected areas.
-4. Run `detect_changes` to check if recent changes caused the issue.
-5. Use `get_impact_radius` on suspected files to see what else is affected.
-
-### Tips
-
-- Check both callers and callees to understand the full context.
-- Look at affected flows to find the entry point that triggers the bug.
-- Recent changes are the most common source of new issues.
-
-## Token Efficiency Rules
-- ALWAYS start with `get_minimal_context(task="<your task>")` before any other graph tool.
-- Use `detail_level="minimal"` on all calls. Only escalate to "standard" when minimal is insufficient.
-- Target: complete any review/debug/refactor task in ≤5 tool calls and ≤800 total output tokens.
diff --git a/.claude/skills/explore-codebase/skill.md b/.claude/skills/explore-codebase/skill.md
deleted file mode 100644
index dc7ad10..0000000
--- a/.claude/skills/explore-codebase/skill.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-name: Explore Codebase
-description: Navigate and understand codebase structure using the knowledge graph
----
-
-## Explore Codebase
-
-Use the code-review-graph MCP tools to explore and understand the codebase.
-
-### Steps
-
-1. Run `list_graph_stats` to see overall codebase metrics.
-2. Run `get_architecture_overview` for high-level community structure.
-3. Use `list_communities` to find major modules, then `get_community` for details.
-4. Use `semantic_search_nodes` to find specific functions or classes.
-5. Use `query_graph` with patterns like `callers_of`, `callees_of`, `imports_of` to trace relationships.
-6. Use `list_flows` and `get_flow` to understand execution paths.
-
-### Tips
-
-- Start broad (stats, architecture) then narrow down to specific areas.
-- Use `children_of` on a file to see all its functions and classes.
-- Use `find_large_functions` to identify complex code.
-
-## Token Efficiency Rules
-- ALWAYS start with `get_minimal_context(task="<your task>")` before any other graph tool.
-- Use `detail_level="minimal"` on all calls. Only escalate to "standard" when minimal is insufficient.
-- Target: complete any review/debug/refactor task in ≤5 tool calls and ≤800 total output tokens.
diff --git a/.claude/skills/refactor-safely/skill.md b/.claude/skills/refactor-safely/skill.md
deleted file mode 100644
index cf84420..0000000
--- a/.claude/skills/refactor-safely/skill.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-name: Refactor Safely
-description: Plan and execute safe refactoring using dependency analysis
----
-
-## Refactor Safely
-
-Use the knowledge graph to plan and execute refactoring with confidence.
-
-### Steps
-
-1. Use `refactor_tool` with mode="suggest" for community-driven refactoring suggestions.
-2. Use `refactor_tool` with mode="dead_code" to find unreferenced code.
-3. For renames, use `refactor_tool` with mode="rename" to preview all affected locations.
-4. Use `apply_refactor_tool` with the refactor_id to apply renames.
-5. After changes, run `detect_changes` to verify the refactoring impact.
-
-### Safety Checks
-
-- Always preview before applying (rename mode gives you an edit list).
-- Check `get_impact_radius` before major refactors.
-- Use `get_affected_flows` to ensure no critical paths are broken.
-- Run `find_large_functions` to identify decomposition targets.
-
-## Token Efficiency Rules
-- ALWAYS start with `get_minimal_context(task="<your task>")` before any other graph tool.
-- Use `detail_level="minimal"` on all calls. Only escalate to "standard" when minimal is insufficient.
-- Target: complete any review/debug/refactor task in ≤5 tool calls and ≤800 total output tokens.
diff --git a/.claude/skills/review-changes/skill.md b/.claude/skills/review-changes/skill.md
deleted file mode 100644
index 6bb3558..0000000
--- a/.claude/skills/review-changes/skill.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-name: Review Changes
-description: Perform a structured code review using change detection and impact
----
-
-## Review Changes
-
-Perform a thorough, risk-aware code review using the knowledge graph.
-
-### Steps
-
-1. Run `detect_changes` to get risk-scored change analysis.
-2. Run `get_affected_flows` to find impacted execution paths.
-3. For each high-risk function, run `query_graph` with pattern="tests_for" to check test coverage.
-4. Run `get_impact_radius` to understand the blast radius.
-5. For any untested changes, suggest specific test cases.
-
-### Output Format
-
-Provide findings grouped by risk level (high/medium/low) with:
-- What changed and why it matters
-- Test coverage status
-- Suggested improvements
-- Overall merge recommendation
-
-## Token Efficiency Rules
-- ALWAYS start with `get_minimal_context(task="<your task>")` before any other graph tool.
-- Use `detail_level="minimal"` on all calls. Only escalate to "standard" when minimal is insufficient.
-- Target: complete any review/debug/refactor task in ≤5 tool calls and ≤800 total output tokens.
diff --git a/.gitignore b/.gitignore
index ae2758c..2b6f9a0 100644
--- a/.gitignore
+++ b/.gitignore
@@ -24,4 +24,5 @@ package-lock.json
 # Added by code-review-graph
 .code-review-graph/
 .claude/
-hookify.*.local.md
\ No newline at end of file
+hookify.*.local.md
+.mcp.json
\ No newline at end of file
diff --git a/.mcp.json b/.mcp.json
deleted file mode 100644
index c3391d2..0000000
--- a/.mcp.json
+++ /dev/null
@@ -1,13 +0,0 @@
-{
-  "mcpServers": {
-    "code-review-graph": {
-      "command": "uvx",
-      "args": [
-        "code-review-graph",
-        "serve"
-      ],
-      "cwd": "/Users/liulujian/Documents/code/TopFansByGithub",
-      "type": "stdio"
-    }
-  }
-}