菜单
Interactive setup wizard for technology proficiency levels. Creates or updates ~/.claude/technology-explainer.json. Run this command to configure how Claude adapts explanation depth per technology. Keywords: technology explainer setup, configure proficiency, explanation depth.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Configure the minimal single-line compact Claude Code statusline (repo, worktree, branch, model, effort, context window, context %, and session cost). Detects and resolves conflicts with an existing statusline before switching.
Show the full Claude Code session context assembled in load order. Outputs all CLAUDE.md files, auto-memory, SessionStart hook output, and skill listings in one document with source separators. Prints a summary table to stderr with scope, type, source, status, lines, tokens, and context% per source. Keywords: session context, what is loaded, show context, debug context, rules, hooks, skills.
Interactive setup wizard for git branch naming conventions. Creates or updates .claude-plugin/git-branch-naming.json with project-specific rules. Run this command to configure prefixes, ticket patterns, enforcement levels, and protected branches. Keywords: setup branch naming, configure conventions, branch config, git naming setup.
Analyze documentation health: run structural checks (broken links, orphans, duplicates, CLAUDE.md overflow, mandatory docs), then semantic analysis (README compliance, terminology, ADR completeness, content actuality). Create GitHub epic with linked issues for findings. Keywords: documentation audit, kb grooming, doc health, knowledge base.
Interactive setup wizard for fast-changing technology watchlist. Creates or updates ~/.claude/fresh-guides.json or .claude-plugin/fresh-guides.json. Run this command to configure which technologies require doc verification. Keywords: fresh-guides setup, configure watchlist, fast-changing technology, doc verification.
Display current fresh-guides watchlist configuration. Shows all watched technologies and their doc URLs. Keywords: show watchlist, fresh-guides config, current technologies.
| name | technology-explainer-setup |
| description | Interactive setup wizard for technology proficiency levels. Creates or updates ~/.claude/technology-explainer.json. Run this command to configure how Claude adapts explanation depth per technology. Keywords: technology explainer setup, configure proficiency, explanation depth. |
Configure how Claude adapts explanation depth based on your proficiency with each technology.
Explain the three proficiency levels to the user:
Explain that "technology" is broadly defined: operating systems (Linux, macOS), programming languages (Python, Java), tools (Docker, Git), platforms (AWS, GCP), workflows (CI/CD, Agile), and anything else the user works with.
Read ~/.claude/technology-explainer.json. If it exists, display the current configuration as a formatted table showing technologies grouped by level, the default level, and any configured sources. If it doesn't exist, say "No proficiency config found — let's create one."
Use AskUserQuestion with a free-text "Other" option. Remind the criteria: "Technologies you know deeply. Claude will give brief, no-theory answers."
Suggest common categories: operating systems, shells, languages, IDEs, version control.
Use AskUserQuestion with a free-text "Other" option. Remind the criteria: "Technologies you're actively studying. Claude will provide detailed theory, examples, and step-by-step explanations."
Use AskUserQuestion with a free-text "Other" option. Remind the criteria: "Technologies you use regularly but in limited scope. Claude will explain nuances and gotchas but skip basics."
Use AskUserQuestion:
Use AskUserQuestion: "Do you want to add preferred documentation or style guides for specific technologies?" (e.g., terraform → HashiCorp docs, python → PEP 8).
If yes, ask for technology name and URL/reference pairs. Collect as many as the user wants.
Write ~/.claude/technology-explainer.json with the collected data. Display a summary table and remind: "Restart your session or run /clear for changes to take effect."
