d48cda4081
CI / Test (ubuntu-latest, Node 18.x, bun) (push) Failing after 15m1s
CI / Test (ubuntu-latest, Node 18.x, npm) (push) Failing after 15m1s
CI / Test (ubuntu-latest, Node 18.x, pnpm) (push) Failing after 15m1s
CI / Test (ubuntu-latest, Node 18.x, yarn) (push) Failing after 15m1s
CI / Test (ubuntu-latest, Node 20.x, bun) (push) Failing after 17m13s
CI / Test (ubuntu-latest, Node 20.x, npm) (push) Failing after 18m42s
CI / Test (ubuntu-latest, Node 20.x, pnpm) (push) Failing after 15m0s
CI / Test (ubuntu-latest, Node 20.x, yarn) (push) Failing after 49m44s
CI / Test (ubuntu-latest, Node 22.x, bun) (push) Failing after 51m55s
CI / Test (ubuntu-latest, Node 22.x, pnpm) (push) Failing after 21m57s
CI / Test (ubuntu-latest, Node 22.x, npm) (push) Failing after 37m39s
CI / Test (ubuntu-latest, Node 22.x, yarn) (push) Failing after 34m7s
CI / Validate Components (push) Failing after 37m15s
CI / Python Tests (push) Failing after 10m1s
CI / Security Scan (push) Failing after 10m1s
CI / Lint (push) Failing after 17m12s
CI / Coverage (push) Failing after 20m19s
CI / Test (macos-latest, Node 18.x, bun) (push) Has been cancelled
CI / Test (macos-latest, Node 18.x, npm) (push) Has been cancelled
CI / Test (macos-latest, Node 18.x, pnpm) (push) Has been cancelled
CI / Test (macos-latest, Node 18.x, yarn) (push) Has been cancelled
CI / Test (windows-latest, Node 18.x, npm) (push) Has been cancelled
CI / Test (windows-latest, Node 18.x, pnpm) (push) Has been cancelled
CI / Test (windows-latest, Node 18.x, yarn) (push) Has been cancelled
CI / Test (macos-latest, Node 20.x, bun) (push) Has been cancelled
CI / Test (macos-latest, Node 20.x, npm) (push) Has been cancelled
CI / Test (macos-latest, Node 20.x, pnpm) (push) Has been cancelled
CI / Test (macos-latest, Node 20.x, yarn) (push) Has been cancelled
CI / Test (windows-latest, Node 20.x, npm) (push) Has been cancelled
CI / Test (windows-latest, Node 20.x, pnpm) (push) Has been cancelled
CI / Test (windows-latest, Node 20.x, yarn) (push) Has been cancelled
CI / Test (macos-latest, Node 22.x, bun) (push) Has been cancelled
CI / Test (macos-latest, Node 22.x, npm) (push) Has been cancelled
CI / Test (macos-latest, Node 22.x, pnpm) (push) Has been cancelled
CI / Test (macos-latest, Node 22.x, yarn) (push) Has been cancelled
CI / Test (windows-latest, Node 22.x, npm) (push) Has been cancelled
CI / Test (windows-latest, Node 22.x, pnpm) (push) Has been cancelled
CI / Test (windows-latest, Node 22.x, yarn) (push) Has been cancelled
118 lines
2.0 KiB
Markdown
118 lines
2.0 KiB
Markdown
---
|
|
description: Generate skills from git history analysis
|
|
agent: everything-claude-code:build
|
|
---
|
|
|
|
# Skill Create Command
|
|
|
|
Analyze git history to generate Claude Code skills: $ARGUMENTS
|
|
|
|
## Your Task
|
|
|
|
1. **Analyze commits** - Pattern recognition from history
|
|
2. **Extract patterns** - Common practices and conventions
|
|
3. **Generate SKILL.md** - Structured skill documentation
|
|
4. **Create instincts** - For continuous-learning-v2
|
|
|
|
## Analysis Process
|
|
|
|
### Step 1: Gather Commit Data
|
|
```bash
|
|
# Recent commits
|
|
git log --oneline -100
|
|
|
|
# Commits by file type
|
|
git log --name-only --pretty=format: | sort | uniq -c | sort -rn
|
|
|
|
# Most changed files
|
|
git log --pretty=format: --name-only | sort | uniq -c | sort -rn | head -20
|
|
```
|
|
|
|
### Step 2: Identify Patterns
|
|
|
|
**Commit Message Patterns**:
|
|
- Common prefixes (feat, fix, refactor)
|
|
- Naming conventions
|
|
- Co-author patterns
|
|
|
|
**Code Patterns**:
|
|
- File structure conventions
|
|
- Import organization
|
|
- Error handling approaches
|
|
|
|
**Review Patterns**:
|
|
- Common review feedback
|
|
- Recurring fix types
|
|
- Quality gates
|
|
|
|
### Step 3: Generate SKILL.md
|
|
|
|
```markdown
|
|
# [Skill Name]
|
|
|
|
## Overview
|
|
[What this skill teaches]
|
|
|
|
## Patterns
|
|
|
|
### Pattern 1: [Name]
|
|
- When to use
|
|
- Implementation
|
|
- Example
|
|
|
|
### Pattern 2: [Name]
|
|
- When to use
|
|
- Implementation
|
|
- Example
|
|
|
|
## Best Practices
|
|
|
|
1. [Practice 1]
|
|
2. [Practice 2]
|
|
3. [Practice 3]
|
|
|
|
## Common Mistakes
|
|
|
|
1. [Mistake 1] - How to avoid
|
|
2. [Mistake 2] - How to avoid
|
|
|
|
## Examples
|
|
|
|
### Good Example
|
|
```[language]
|
|
// Code example
|
|
```
|
|
|
|
### Anti-pattern
|
|
```[language]
|
|
// What not to do
|
|
```
|
|
```
|
|
|
|
### Step 4: Generate Instincts
|
|
|
|
For continuous-learning-v2:
|
|
|
|
```json
|
|
{
|
|
"instincts": [
|
|
{
|
|
"trigger": "[situation]",
|
|
"action": "[response]",
|
|
"confidence": 0.8,
|
|
"source": "git-history-analysis"
|
|
}
|
|
]
|
|
}
|
|
```
|
|
|
|
## Output
|
|
|
|
Creates:
|
|
- `skills/[name]/SKILL.md` - Skill documentation
|
|
- `skills/[name]/instincts.json` - Instinct collection
|
|
|
|
---
|
|
|
|
**TIP**: Run `/skill-create --instincts` to also generate instincts for continuous learning.
|