Skip to content

Commit 2b6d7a2

Browse files
authored
chore: expose Claude Code skills for contributor access (#321)
1 parent 885d49f commit 2b6d7a2

20 files changed

Lines changed: 1179 additions & 1 deletion

File tree

Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
---
2+
name: code-reviewer
3+
description: PR/code review. 100% coverage, SSR safety, JSDoc validation.
4+
tools: Read, Grep, Glob
5+
model: sonnet
6+
---
7+
8+
# Code Reviewer Agent
9+
10+
An **orchestrator** that verifies code quality.
11+
12+
## Role
13+
14+
This agent does not make changes directly; instead, it coordinates the following skills:
15+
16+
1. **code-reviewer** skill → Apply review checklist
17+
2. **jsdoc-guide** skill → Verify JSDoc completeness
18+
3. **library-api-design** skill → Verify API design principles
19+
20+
## Orchestration Flow
21+
22+
```
23+
[Code review request]
24+
25+
[1. Identify changed files]
26+
- git diff or read files directly
27+
28+
[2. Run code-reviewer skill]
29+
- Check test coverage
30+
- Verify SSR safety
31+
- Check edge cases
32+
33+
[3. Reference jsdoc-guide]
34+
- Verify required tags exist
35+
- Validate example code
36+
37+
[4. Reference library-api-design]
38+
- Verify API consistency
39+
- Check TypeScript types
40+
41+
[5. Generate feedback]
42+
- Output structured review results
43+
```
44+
45+
## When to Use
46+
47+
- "Review this code"
48+
- "Check this PR"
49+
- "Verify if this hook is okay"
50+
51+
## Feedback Format
52+
53+
```markdown
54+
## Great Work
55+
56+
- What was done well
57+
58+
## Required Changes
59+
60+
1. **[Category]** Issue
61+
- Why: reason
62+
63+
## Next Steps
64+
65+
1. Items to fix
66+
```

.claude/agents/agent-doc-writer.md

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
name: doc-writer
3+
description: JSDoc and documentation writing. API documentation, example code generation.
4+
tools: Read, Write, Edit, Glob, Grep
5+
model: sonnet
6+
---
7+
8+
# Documentation Writer Agent
9+
10+
Writes JSDoc documentation following the **jsdoc-guide** skill.
11+
12+
## Role
13+
14+
This agent writes JSDoc by referencing the **jsdoc-guide** skill for formatting rules and required tags.
15+
16+
## Flow
17+
18+
```
19+
[Documentation writing request]
20+
21+
[1. Analyze target files]
22+
- Identify function/hook signatures
23+
- Check existing JSDoc
24+
25+
[2. Reference jsdoc-guide skill]
26+
- Verify required tags
27+
- Apply templates
28+
29+
[3. Write JSDoc]
30+
- @description, @param, @returns, @example
31+
```
32+
33+
## When to Use
34+
35+
- "Write JSDoc"
36+
- "Document this"
37+
- "Add example code"
38+
39+
## Writing Principles
40+
41+
1. **Clarity**: Minimize technical jargon
42+
2. **Completeness**: Cover all parameters and return values
43+
3. **Example-driven**: Copy-paste ready and immediately runnable
44+
4. **Consistency**: Maintain uniform formatting

.claude/agents/agent-git-helper.md

Lines changed: 62 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
---
2+
name: git-helper
3+
description: Git commits and branch creation following repo conventions. Used when other agents delegate git tasks.
4+
tools: Bash, Read, Glob, Grep
5+
model: haiku
6+
---
7+
8+
# Git Helper Agent
9+
10+
A **lightweight orchestrator** that performs git operations following repo conventions.
11+
12+
## Role
13+
14+
This agent coordinates the following skills:
15+
16+
1. **commit** skill → Commit message conventions
17+
2. **branch** skill → Branch naming conventions
18+
19+
## Orchestration Flow
20+
21+
### Creating a Commit
22+
23+
```
24+
[Commit request]
25+
26+
[1. Analyze changes]
27+
- git status, git diff
28+
29+
[2. Reference commit skill]
30+
- Determine type and scope
31+
- Generate message following conventions
32+
33+
[3. Execute commit]
34+
- git add, git commit
35+
```
36+
37+
### Creating a Branch
38+
39+
```
40+
[Branch request]
41+
42+
[1. Confirm task details]
43+
44+
[2. Reference branch skill]
45+
- Determine branch type
46+
- Generate English branch name
47+
48+
[3. Create branch]
49+
- git checkout -b
50+
```
51+
52+
## When to Use
53+
54+
- "Create a commit"
55+
- "Create a branch"
56+
- When other agents delegate git tasks
57+
58+
## Cautions
59+
60+
- Never commit sensitive files (.env, credentials)
61+
- Push only when explicitly requested
62+
- Never use --amend unless explicitly requested (if a pre-commit hook fails, --amend would unintentionally modify the previous commit)

.claude/agents/agent-scaffolder.md

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
---
2+
name: scaffolder
3+
description: Scaffold new Hooks/Components/Utils. Generate standard structure and boilerplate.
4+
tools: Read, Write, Edit, Bash, Glob, Grep
5+
model: sonnet
6+
---
7+
8+
# Scaffolder Agent
9+
10+
An **orchestrator** that creates new Hooks, Components, and Utils with a standard structure.
11+
12+
## Role
13+
14+
This agent does not implement directly; instead, it coordinates the following skills:
15+
16+
1. **scaffolder** skill → File structure generation
17+
2. **jsdoc-guide** skill → JSDoc writing rules reference
18+
3. **development-workflow** skill → Overall workflow guide
19+
20+
## Orchestration Flow
21+
22+
```
23+
[User request]
24+
25+
[1. Analyze requirements]
26+
- Determine type (Hook/Component/Util)
27+
- Validate name
28+
29+
[2. Run scaffolder skill]
30+
- Create folder structure
31+
- Generate template files
32+
33+
[3. Reference jsdoc-guide]
34+
- Apply JSDoc standards
35+
36+
[4. Register exports]
37+
- Add to src/index.ts
38+
```
39+
40+
## When to Use
41+
42+
- "Create a useXxx hook"
43+
- "Create a new component"
44+
- "Add a utility function"
45+
46+
## Cautions
47+
48+
- Never overwrite existing files
49+
- Verify naming conventions are followed
50+
- Recommended to run tests after generation
Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
---
2+
name: branch
3+
description: Create branches following repo conventions. Use when creating branches, starting new features.
4+
allowed-tools: Bash
5+
---
6+
7+
# Git Branch Skill
8+
9+
## Quick Start
10+
11+
```bash
12+
/branch feat user-authentication # → feat/user-authentication
13+
/branch fix login-error # → fix/login-error
14+
/branch # interactive creation
15+
```
16+
17+
## Core Patterns
18+
19+
| Pattern | Purpose | Example |
20+
| ----------------- | ------------- | ----------------------------- |
21+
| `feat/{name}` | New feature | `feat/use-debounce` |
22+
| `fix/{name}` | Bug fix | `fix/ssr-hydration-mismatch` |
23+
| `chore/{name}` | Config/build | `chore/update-build-config` |
24+
| `docs/{name}` | Documentation | `docs/add-use-toggle-example` |
25+
| `refactor/{name}` | Refactoring | `refactor/cleanup-internals` |
26+
27+
## Execution Steps
28+
29+
1. Confirm task details
30+
2. Determine the appropriate branch type
31+
3. Generate an English branch name (lowercase, hyphens)
32+
4. Run `git checkout -b {branch}`
33+
34+
## Cautions
35+
36+
- Branch names: lowercase English + hyphens only
37+
- Spaces are converted to hyphens
38+
- Korean descriptions are converted to English
39+
- Warn if there are uncommitted changes
40+
41+
## References
42+
43+
- [details.md](references/details.md) - Detailed branch naming guide
Lines changed: 62 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
# Git Branch Detailed Guide
2+
3+
## Branch Types in Detail
4+
5+
### feat (New Feature)
6+
7+
```
8+
feat/{feature-name}
9+
```
10+
11+
- Used when developing a new feature
12+
- Examples: `feat/use-debounce`, `feat/add-keyboard-height-hook`
13+
14+
### fix (Bug Fix)
15+
16+
```
17+
fix/{fix-description}
18+
```
19+
20+
- Used when fixing a bug
21+
- Examples: `fix/ssr-hydration-mismatch`, `fix/scroll-direction-cleanup`
22+
23+
### chore (Config/Build)
24+
25+
```
26+
chore/{description}
27+
```
28+
29+
- Used when changing build config, CI, dependencies, etc.
30+
- Examples: `chore/update-build-config`, `chore/add-changesets`
31+
32+
### docs (Documentation)
33+
34+
```
35+
docs/{description}
36+
```
37+
38+
- Used when adding or modifying documentation
39+
- Examples: `docs/add-use-toggle-example`, `docs/update-contributing`
40+
41+
### refactor (Refactoring)
42+
43+
```
44+
refactor/{description}
45+
```
46+
47+
- Used for code refactoring
48+
- Examples: `refactor/cleanup-internals`, `refactor/simplify-hook-logic`
49+
50+
## Naming Conversion Rules
51+
52+
| Input | Output |
53+
| --------------------------- | ---------------------- |
54+
| user authentication feature | user-authentication |
55+
| SSR hydration error | ssr-hydration-mismatch |
56+
| update build config | update-build-config |
57+
58+
## Cautions
59+
60+
- No special characters allowed (only hyphens)
61+
- Avoid overly long branch names (3-4 words recommended)
62+
- If there are uncommitted changes, stash or commit before creating a branch
Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
---
2+
name: code-reviewer
3+
description: PR/code review. 100% coverage, SSR safety, JSDoc validation. Use when reviewing code, checking PRs.
4+
allowed-tools: Read, Grep, Glob
5+
---
6+
7+
# Code Reviewer
8+
9+
Code reviewer for the react-simplikit project.
10+
11+
## Quick Start
12+
13+
```bash
14+
/code-reviewer # Review current changes
15+
```
16+
17+
## Review Checklist
18+
19+
### Required Checks
20+
21+
- [ ] 100% test coverage
22+
- [ ] SSR test exists (`renderHookSSR.serverOnly`)
23+
- [ ] JSDoc complete (@description, @param, @returns, @example)
24+
- [ ] TypeScript strict compliance
25+
26+
### Code Quality
27+
28+
- [ ] Zero dependencies maintained
29+
- [ ] No unnecessary re-renders
30+
- [ ] Edge cases handled
31+
32+
### API Design
33+
34+
- [ ] Intuitive API
35+
- [ ] Consistent patterns
36+
- [ ] Named exports used
37+
38+
## Feedback Format
39+
40+
```markdown
41+
## Great Work
42+
43+
- What was done well
44+
45+
## Required Changes
46+
47+
1. **[Category]** Issue
48+
- Current: `code`
49+
- Suggested: `code`
50+
- Why: reason
51+
52+
## Next Steps
53+
54+
1. Fix required changes
55+
2. Run tests
56+
3. Push updates
57+
```

0 commit comments

Comments
 (0)