skill-create

Analyze git history to detect coding patterns and generate SKILL.md files.

24|5|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/Luohaothu/everything-codex --skill skill-create-luohaothu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-create
Source: https://github.com/Luohaothu/everything-codex/tree/main/skills/skill-create
Command: npx skills add https://github.com/Luohaothu/everything-codex --skill skill-create-luohaothu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes a repository's git history to identify coding patterns and extract team practices, enabling codified guidance for onboarding and process improvement.

Core Features & Use Cases

  • Detect recurring commit patterns, file co-changes, and architectural signals to infer coding standards.
  • Generate SKILL.md templates that codify discovered patterns for documentation and knowledge sharing.
  • Use cases include onboarding new team members, retroactively capturing practices from mature projects, and guiding refactoring decisions.

Quick Start

Run /skill-create to analyze the current repository and generate SKILL.md files in a chosen output directory.

Frequently Asked Questions about skill-create

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract coding patterns from git history for team documentation?

Extract coding patterns from git history by analyzing commit data to identify recurring conventions, file co-changes, and architecture signals. The skill parses this repository data and emits a structured SKILL.md file codifying discovered team practices for onboarding.

What is the best way to generate onboarding documentation from existing repository commits?

Generating onboarding documentation from repository commits involves detecting architectural signals and file co-changes in git history. This approach retroactively captures mature project practices and outputs structured SKILL.md templates for knowledge transfer.

Does this pattern detection work with any software project repository?

Pattern detection applies to any software project where commit history reveals conventions and file co-changes. It requires sufficient git history depth to accurately infer coding standards and architectural signals for codification.

How do I codify team practices into a structured SKILL.md file?

Codify team practices into a SKILL.md file by running the analysis to parse git data and detect patterns. The process automatically generates the required structured frontmatter and body content based on inferred coding standards.

When should I avoid using git history analysis for knowledge transfer?

Avoid git history analysis for knowledge transfer when commit messages lack descriptive context or repositories have shallow histories. Sparse commit data limits accurate pattern detection and diminishes the quality of generated team practices.