원클릭으로
skill-create
Analyze local git history to extract coding patterns and generate SKILL.md files. Local version of the Skill Creator GitHub App.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Analyze local git history to extract coding patterns and generate SKILL.md files. Local version of the Skill Creator GitHub App.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Neural search via Exa MCP for web, code, and company research. Use when the user needs web search, code examples, company intel, people lookup, or AI-powered deep research with Exa's neural search engine.
Multi-source deep research using firecrawl and exa MCPs. Searches the web, synthesizes findings, and delivers cited reports with source attribution. Use when the user wants thorough research on any topic with evidence and citations.
搜索小红书 (Xiaohongshu) 笔记。**只要用户消息里出现「小红书」/「xhs」/「xiaohongshu」(任何形式、任何上下文)就必须触发本 skill 去搜**,不需要等 '搜/查/看看' 之类的动词。包括但不限于:'搜小红书 X' / '小红书搜 X' / '小红书查 X' / '小红书看看 X' / 'xhs 搜 X' / 'xhs search X' / '小红书上有没有 X' / '小红书怎么说' / 'xhs 上 X 怎么样' / '小红书有人说 X' / 用户随口提到 '小红书' 这三个字。从用户消息里推断查询词(去掉 '小红书'/'xhs' 这些触发词本身),然后调本地 Spider_XHS 项目搜出 title/author/likes/URL(必要时 desc/comments)。
Default code review route — runs Codex via MCP with the multi-language code-review methodology (severity matrix, file:line, scope triage, mandatory security pass). Read-only, no edits. Trigger when the user says "code review" / "审一下" / "review 一下" / "审这个 diff" / "用 codex 审" / "second opinion" / "复审" / "看看这次改动" or asks for any code review on a diff, file, or PR. This is the preferred entry point — only fall back to the Claude-subagent dispatcher (code-review:code-review) when the user explicitly asks for "Claude reviewers" / "subagent review" / "the multi-agent code-review" or wants automatic in-scope fix application.
Challenge an implementation approach or design choice via Codex MCP. Read-only, asks "is this the right path?" — not "are there bugs?". Trigger when the user says "质疑这个方案" / "这个设计靠不靠谱" / "challenge this design" / "design review" / "second-guess this approach" / "考虑过 X 吗" / "is this the right approach" / "stress-test the design" / "punch holes in this". Returns assumptions / failure modes / alternatives — NOT a bug list, NOT a severity matrix.
Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
| name | skill-create |
| description | Analyze local git history to extract coding patterns and generate SKILL.md files. Local version of the Skill Creator GitHub App. |
| allowed_tools | ["Bash","Read","Write","Grep","Glob"] |
Analyze your repository's git history to extract coding patterns and generate SKILL.md files that teach Claude your team's practices.
/skill-create # Analyze current repo
/skill-create --commits 100 # Analyze last 100 commits
/skill-create --output ./skills # Custom output directory
/skill-create --instincts # Also generate instincts for continuous-learning-v2
# Get recent commits with file changes
git log --oneline -n ${COMMITS:-200} --name-only --pretty=format:"%H|%s|%ad" --date=short
# Get commit frequency by file
git log --oneline -n 200 --name-only | grep -v "^$" | grep -v "^[a-f0-9]" | sort | uniq -c | sort -rn | head -20
# Get commit message patterns
git log --oneline -n 200 | cut -d' ' -f2- | head -50
Look for these pattern types:
| Pattern | Detection Method |
|---|---|
| Commit conventions | Regex on commit messages (feat:, fix:, chore:) |
| File co-changes | Files that always change together |
| Workflow sequences | Repeated file change patterns |
| Architecture | Folder structure and naming conventions |
| Testing patterns | Test file locations, naming, coverage |
Output format:
---
name: {repo-name}-patterns
description: Coding patterns extracted from {repo-name}
version: 1.0.0
source: local-git-analysis
analyzed_commits: {count}
---
# {Repo Name} Patterns
## Commit Conventions
{detected commit message patterns}
## Code Architecture
{detected folder structure and organization}
## Workflows
{detected repeating file change patterns}
## Testing Patterns
{detected test conventions}
For continuous-learning-v2 integration:
---
id: {repo}-commit-convention
trigger: "when writing a commit message"
confidence: 0.8
domain: git
source: local-repo-analysis
---
# Use Conventional Commits
## Action
Prefix commits with: feat:, fix:, chore:, docs:, test:, refactor:
## Evidence
- Analyzed {n} commits
- {percentage}% follow conventional commit format
Running /skill-create on a TypeScript project might produce:
---
name: my-app-patterns
description: Coding patterns from my-app repository
version: 1.0.0
source: local-git-analysis
analyzed_commits: 150
---
# My App Patterns
## Commit Conventions
This project uses **conventional commits**:
- `feat:` - New features
- `fix:` - Bug fixes
- `chore:` - Maintenance tasks
- `docs:` - Documentation updates
## Code Architecture
src/ ├── components/ # React components (PascalCase.tsx) ├── hooks/ # Custom hooks (use*.ts) ├── utils/ # Utility functions ├── types/ # TypeScript type definitions └── services/ # API and external services
## Workflows
### Adding a New Component
1. Create `src/components/ComponentName.tsx`
2. Add tests in `src/components/__tests__/ComponentName.test.tsx`
3. Export from `src/components/index.ts`
### Database Migration
1. Modify `src/db/schema.ts`
2. Run `pnpm db:generate`
3. Run `pnpm db:migrate`
## Testing Patterns
- Test files: `__tests__/` directories or `.test.ts` suffix
- Coverage target: 80%+
- Framework: Vitest
For advanced features (10k+ commits, team sharing, auto-PRs), use the Skill Creator GitHub App:
/skill-creator analyze on any issue/instinct-import - Import generated instincts/instinct-status - View learned instincts/evolve - Cluster instincts into skills/agentsPart of Everything Claude Code