Claude Code Skillsとは？使い方・作り方・おすすめ一覧を完全解説【2026年最新】

.claude/skills/my-skill/
├── SKILL.md           # メインの指示（必須）
├── template.md        # Claude が埋めるテンプレート
├── examples/
│   └── sample.md      # 期待する出力例
└── scripts/
    └── validate.sh    # Claude が実行するスクリプト

mkdir -p ~/.claude/skills/explain-code

---
name: explain-code
description: Explains code with visual diagrams and analogies. Use when explaining how code works, teaching about a codebase, or when the user asks "how does this work?"
---

When explaining code, always include:

1. **Start with an analogy**: Compare the code to something from everyday life
2. **Draw a diagram**: Use ASCII art to show the flow, structure, or relationships
3. **Walk through the code**: Explain step-by-step what happens
4. **Highlight a gotcha**: What's a common mistake or misconception?

---
name: fix-issue
description: Fix a GitHub issue
disable-model-invocation: true
argument-hint: [issue-number]
---

Fix GitHub issue $ARGUMENTS following our coding standards.

1. Read the issue description
2. Understand the requirements
3. Implement the fix
4. Write tests
5. Create a commit

---
name: migrate-component
description: Migrate a component from one framework to another
---

Migrate the $0 component from $1 to $2.
Preserve all existing behavior and tests.

---
name: api-conventions
description: API design patterns for this codebase
---

When writing API endpoints:
- Use RESTful naming conventions
- Return consistent error formats
- Include request validation

---
name: deploy
description: Deploy the application to production
context: fork
disable-model-invocation: true
---

Deploy the application:
1. Run the test suite
2. Build the application
3. Push to the deployment target

---
name: pr-summary
description: Summarize changes in a pull request
context: fork
agent: Explore
allowed-tools: Bash(gh *)
---

## Pull request context
- PR diff: !`gh pr diff`
- PR comments: !`gh pr view --comments`
- Changed files: !`gh pr diff --name-only`

## Your task
Summarize this pull request for the review meeting.

---
name: commit
description: Create a well-formatted git commit following our conventions
disable-model-invocation: true
---

Create a git commit with the following format:

type(scope): subject

Types: feat, fix, docs, style, refactor, test, chore
Subject: imperative mood, 50 chars max
Body: explain the "why", wrapped at 72 chars

1. Run `git diff --staged` to see changes
2. Determine the type and scope
3. Write the commit message
4. Run `git commit`

.claude/skills/code-review/
├── SKILL.md           # レビューの進め方の手順
├── standards.md       # コーディング規約の詳細
└── examples/
    ├── good-code.md   # 良いコードの例
    └── bad-code.md    # 直すべきコードの例

---
name: deep-research
description: Research a topic thoroughly
context: fork
agent: Explore
---

Research $ARGUMENTS thoroughly:

1. Find relevant files using Glob and Grep
2. Read and analyze the code
3. Summarize findings with specific file references