Claude 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?

Keep explanations conversational. For complex concepts, use multiple analogies.

---
name: secure-deploy
description: Deploy the application to production with safety checks
argument-hint: "[environment]"
disable-model-invocation: true
allowed-tools: Bash(npm *) Bash(git *) Read
model: claude-sonnet-4-5
effort: high
context: fork
agent: Explore
paths:
  - "src/**/*.ts"
  - "scripts/**/*.sh"
hooks:
  PreToolUse:
    - matcher: "Bash"
      hooks:
        - type: command
          command: "./scripts/security-check.sh"
---

Deploy $ARGUMENTS to production safely:

1. Run the full test suite
2. Build the application
3. Run security checks
4. Push to the deployment target
5. Verify the deployment succeeded

---
name: fix-issue
description: Fix a GitHub issue
disable-model-invocation: true
---

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: 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 concisely:
1. What problem does it solve?
2. What are the key changes?
3. Are there any potential risks?

---
name: deep-research
description: Research a topic thoroughly in the codebase
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

---
name: code-review
description: Review code for best practices, security, and maintainability
allowed-tools: Read Grep Glob
---

Review the code in $ARGUMENTS.

## Review checklist
- Code clarity and naming
- Error handling
- Security issues (no hardcoded secrets)
- Test coverage

## Additional resources

- For detailed style rules, see [reference.md](reference.md)
- For examples of good vs bad patterns, see [examples/](examples/)

{
  "name": "my-dev-tools",
  "version": "1.0.0",
  "description": "코드 리뷰와 배포 자동화 스킬 모음",
  "author": {
    "name": "Your Name",
    "email": "you@example.com",
    "url": "https://github.com/yourusername"
  },
  "homepage": "https://github.com/yourusername/my-dev-tools",
  "repository": "https://github.com/yourusername/my-dev-tools",
  "license": "MIT",
  "keywords": ["code-review", "deploy", "automation"]
}

---
name: review
description: Review code for quality, security, and maintainability. Use when reviewing code, checking PRs, or analyzing code quality.
allowed-tools: Read Grep Glob
---

Review the code in $ARGUMENTS for:

## Priority: Critical (must fix)
- Security vulnerabilities (hardcoded secrets, SQL injection, XSS)
- Memory leaks or resource leaks
- Incorrect error handling that could cause data loss

## Priority: Warning (should fix)
- Missing input validation
- Functions longer than 50 lines
- Duplicated code blocks

## Priority: Suggestion (consider improving)
- Naming clarity
- Missing tests
- Performance optimizations

Provide specific file and line references for each issue.
Include a code example showing how to fix critical issues.

---
name: deploy
description: Deploy the application to a target environment
argument-hint: "[staging|production]"
disable-model-invocation: true
context: fork
agent: general-purpose
allowed-tools: Bash(npm *) Bash(git *) Bash(gh *) Read
effort: high
---

Deploy the application to $ARGUMENTS environment.

## Pre-deploy checks
1. Run `npm test` and confirm all tests pass
2. Run `npm run build` and confirm build succeeds
3. Check `git status` — working tree must be clean

## Deploy steps
4. Push the current branch to origin
5. Create a deployment tag: `git tag deploy-$(date +%Y%m%d-%H%M%S)`
6. Trigger the deployment pipeline via `gh workflow run deploy.yml -f environment=$ARGUMENTS`

## Post-deploy verification
7. Wait 60 seconds, then check deployment status
8. Report the deployment URL and status