Skill Create from Git History

Generate project-specific SKILL.md files from git commit history.

1|1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/zb-ss/claude-plugin-workflow --skill skill-create-from-git-history
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Skill Create from Git History
Source: https://github.com/zb-ss/claude-plugin-workflow/tree/main/skills/skill-create
Command: npx skills add https://github.com/zb-ss/claude-plugin-workflow --skill skill-create-from-git-history

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents you from manually writing and maintaining project-specific coding guidelines by turning your existing git history into reusable, context-aware skills.

Core Features & Use Cases

  • Pattern discovery from git history: Detects commit message conventions, file co-change relationships, directory structure organization, and test organization from recent commits.
  • Auto-generation of SKILL.md files: Produces multiple project-specific skill documents (e.g., commit conventions, architecture, workflow, naming/testing patterns) ready for Claude Code to load.
  • Save-ready output for iterative improvement: Writes generated skills to a configurable output directory so the project’s conventions can evolve with new commits.

Core Use Case: When you join an unfamiliar repo, run the generator to quickly create skills that reflect how the codebase is actually structured and how changes are typically made.

Quick Start

Run /workflow:skill-create with commits set to 100 and output left at the default to generate new project skills from your recent git history.

Frequently Asked Questions about Skill Create from Git History

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

FAQPage Schema
How do I generate coding conventions from git history?

To generate coding conventions from git history, this Skill analyzes recent commits to detect message patterns, file co-change relationships, and directory structures, then outputs SKILL.md files to a selected directory.

What is the best way to document repository architecture for onboarding?

Documenting repository architecture for onboarding is best achieved by analyzing git commit patterns to infer directory organization and test conventions, auto-generating context-aware skill documents for Claude Code to load.

Can I infer testing patterns and naming conventions from existing commits?

Yes, you can infer testing patterns and naming conventions by analyzing established git commit workflows, detecting recurring file co-change relationships and test organization structures to output reusable skill documents.

Does this git history analysis require a minimum number of commits to work?

This git history analysis works on repositories with established workflows and test conventions. By default, it analyzes 100 recent commits to ensure sufficient data for detecting recurring patterns and generating accurate skill files.

How do I keep generated project skills updated as the codebase evolves?

To keep generated project skills updated as the codebase evolves, re-run the generator to write new SKILL.md files to your configurable output directory, allowing the project conventions to reflect recent commit changes iteratively.