搜索

PythonReactSEOPDF
GitHub Skill

claude-config-optimizer

Claude Code config optimization skill. Use when: - Editing CLAUDE.md, rules/, skills/, agents/, commands/ - User asks about config best practices - Checking optimization status - User says "claude code changelog" or "claude code updates" - User asks about new features or breaking changes in Claude Code

i9wa4☆ 6 仓库 Stars0 仓库 Forks

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求,再添加到工作流。

查看来源 ↗使用指南

技能说明

Claude Config Optimizer Skill

Rules and tracking for Claude Code configuration optimization.

1. Config File Location

User's Claude Code config is stored at:

~/ghq/github.com/i9wa4/dotfiles/config/claude/

Key files:

  • settings.json - Main settings
  • CLAUDE.md - Persona and core rules
  • rules/ - Detailed rules (auto-loaded at startup)
  • skills/ - Specialized knowledge (loaded on demand)
  • agents/ - Custom agents
  • commands/ - Slash commands

2. Fetch CHANGELOG

Use gh command to fetch the latest CHANGELOG:

gh api repos/anthropics/claude-code/contents/CHANGELOG.md \
  --jq '.content' | base64 -d > .i9wa4/tmp/claude-code-changelog.md

Then read the file to analyze.

3. CHANGELOG Operations

3.1. Latest Release Summary
  1. Fetch CHANGELOG using the command above
  2. Extract the first ## x.x.x section
  3. Categorize changes into:
    • New features (Added)
    • Bug fixes (Fixed)
    • Improvements (Improved/Changed)
    • Deprecations (Deprecated)
  4. Present in Japanese with brief explanations
3.2. Version Diff
  1. Ask user for start and end versions
  2. Extract all sections between those versions
  3. Summarize cumulative changes
  4. Highlight breaking changes and deprecations
3.3. Breaking Changes Detection
  1. Search for keywords: Deprecated, Removed, Breaking, Changed
  2. List affected settings and migration paths
  3. Check user's config for affected settings

4. Specification Reference

For detailed questions about Claude Code specifications, features, and usage:

  • YOU MUST: Use the claude-code-guide subagent via Task tool
  • Example queries: hooks, MCP servers, settings, IDE integrations
Task tool with subagent_type: claude-code-guide

5. Settings Categories

Category Examples
Display showTurnDuration, language
Behavior respectGitignore, autoUpdate
Tools disallowedTools, allowedTools
MCP MCP server configurations
Hooks PreToolUse, PostToolUse, Stop hooks
Plans plansDirectory

6. CLAUDE.md Design Guidelines

  • YOU MUST: Focus only on persona and core guidelines
  • YOU MUST: Split detailed rules into rules/
  • NEVER: Include unnecessary information at startup (reference links, usage details)

7. Configuration Usage

Type Load Timing Purpose
CLAUDE.md / rules/ Full load at startup Global rules always applied
commands/ Explicit user invocation Predefined prompts, workflows
skills/ Auto-triggered by conversation Specialized knowledge
agents/ Delegated via Task tool Independent context

8. Optimization Checklist

Check the following when editing CLAUDE.md:

  • Is the persona definition concise?
  • Are basic rules truly needed at all times?
  • Can detailed explanations be moved to rules/ or skills/?
  • Have reference links been moved to skills/?

9. File Structure Maintenance

When adding/removing files in rules/, skills/, agents/, or commands/:

  • YOU MUST: Update corresponding table in CLAUDE.md section 4
  • YOU MUST: Keep tables alphabetically sorted or logically grouped
  • IMPORTANT: Verify actual files match documentation after changes

10. Optimization Tracking

Last reviewed Claude Code version: v2.1.19 (2026-01-24)

10.1. Applied Optimizations
  • Persona definition minimized
  • Rules split into rules/ directory
  • Skills split into skills/ directory
  • Agents split into agents/ directory
  • Commands split into commands/ directory
  • Reference links moved to skills
  • language setting - set to "follow CLAUDE.md's instructions"
  • mcpToolSearch setting - set to "auto:1"
  • ENABLE_TOOL_SEARCH env - set to "true" (force enable)
  • plansDirectory setting - set to ".i9wa4/plans"
10.2. Pending Considerations
  • showTurnDuration setting - hide "Cooked for Xm Xs" messages
  • Keybindings customization via ~/.claude/keybindings.json
10.3. Version Notes
  • v2.1.19: CLAUDE_CODE_ENABLE_TASKS env, $ARGUMENTS[0] syntax, skill approval change
  • v2.1.18: Customizable keybindings (/keybindings command)
  • v2.1.16: New task management system with dependency tracking
  • v2.1.15: npm deprecation notice, React Compiler UI perf, MCP stdio timeout fix
  • v2.1.14: Bash history autocomplete, plugin pinning to git SHA, memory fixes
  • v2.1.10: Setup hook, OAuth URL copy shortcut, heredoc template literal fix
  • v2.1.9: plansDirectory, auto:N for MCP, PreToolUse additionalContext
  • v2.1.7: keybindings.json, showTurnDuration, MCP tool search auto mode
  • v2.1.3: Merged slash commands and skills
  • v2.1.0: language setting, skill hot-reload, context: fork

11. Response Format (CHANGELOG)

# Claude Code vX.X.X

## New Features
- [Feature]: [Description]

## Bug Fixes
- [Fix description]

## Improvements
- [Improvement description]

## Deprecated/Removed
- [Affected settings and migration path]

---
Source: https://github.com/anthropics/claude-code

12. site2skill Usage

Convert documentation websites into Claude Agent Skills.

Requirements: Python 3.10+, wget (brew install wget)

uvx --from git+https://github.com/laiso/site2skill site2skill <URL> <SKILL_NAME>

# Example
uvx --from git+https://github.com/laiso/site2skill site2skill https://docs.pay.jp/v1/ payjp

Options:

  • --output, -o - Output directory (default: .claude/skills)
  • --skill-output - Where to save .skill file (default: current directory)
  • --skip-fetch - Skip download (reuse existing files)
  • --clean - Remove temporary files after completion

To update existing skill docs, re-run without --skip-fetch.

13. Reference Links

Official Documentation:

Community Resources:

使用示例

查看来源仓库中的使用示例与配置说明。

查看来源 ↗

来源历史

收录时间
2026-01-20
索引更新时间
2026-01-26
Branch
main

收录与同步日期属于本站记录。源码修改历史请查看来源仓库。

GitHub ↗

chat Comments (0)

chat_bubble_outline

No comments yet. Be the first to share your thoughts!