with one click
skill-create
Imported from everything-codex command skill-create
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Imported from everything-codex command skill-create
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
AI-native code annotation protocol that encodes intent, risk, dependencies, constraints, and test expectations in machine-parseable comments.
Professional Codex-native multi-agent code review with confidence scoring
架构规划专家 - 使用 Codex 本地上下文、仓库证据和只读 child agent 进行大型系统架构设计与规划。
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
Imported from everything-codex command checkpoint
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
| name | skill-create |
| description | Imported from everything-codex command skill-create |
| version | 0.1.0 |
| source | fork |
| checksum | d56e4f2dfbc58d31166886cba2f4c12b7cb614b5714c6eb4ecd42de47f8373e6 |
| updated_at | "2026-02-11T01:29:16.000Z" |
| intent | skill-management |
| layer | meta |
Codex supports native subagents. Delegate with spawn_agent, coordinate with send_input, collect via wait_agent, and clean up with close_agent.
Execution preference:
[ANALYST]/[ARCHITECT]/[EXECUTOR]/[REVIEWER] structure in a single response.Minimal orchestration pattern:
spawn_agent -> send_input (optional) -> wait_agent -> close_agent
Analyze your repository's git history to extract coding patterns and generate SKILL.md files that teach Codex 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
$skill-development refinementTreat $skill-create as draft generation, then run quality refinement and validation:
$skill-create - Generate skill drafts from repo history$skill-development - Refine structure, trigger quality, and progressive disclosure$skill-quality-analyzer - Score and identify documentation defects$skill-tester - Verify functional behavior with concrete test promptsDefinition of done:
# 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 Codex