style

Extract coding style rules from reference files into a Markdown guide.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/lostsolution/makelele --skill style-lostsolution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: style
Source: https://github.com/lostsolution/makelele/tree/main/skill-graph/skills/style
Command: npx skills add https://github.com/lostsolution/makelele --skill style-lostsolution

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps establish and maintain consistent code style across a development team, reducing cognitive load and improving code readability.

Core Features & Use Cases

  • Style Rule Extraction: Analyzes reference files to identify concrete coding style guidelines.
  • Codestyle Documentation: Generates a Markdown file (.claude/skill-graph/codestyle.md) detailing extracted rules for naming, error handling, module structure, and more.
  • Use Case: A new developer joins a project and needs to understand the established coding conventions. This Skill can quickly generate a reference document based on existing well-styled code.

Quick Start

Use the style skill to extract code style rules from the files in the 'src/' directory.

Frequently Asked Questions about style

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

FAQPage Schema
How do I generate a coding style guide from existing source files?

You can generate a style guide by analyzing reference files to extract rules for naming conventions, error handling, and module structure, which produces a structured Markdown document for your team.

What is the best way to enforce consistent coding practices across a software development team?

The best way to enforce consistent coding practices is to codify extracted programming style rules into a shared Markdown file, ensuring all developers reference the same structural and formatting guidelines.

Can I extract code style rules from any directory in my project?

You can extract code style rules by pointing the analysis at any directory containing reference files, such as 'src/', to evaluate file patterns and comment styles.

How does analyzing reference files help maintain code readability?

Analyzing reference files maintains code readability by identifying established conventions and generating a structured guide, which reduces cognitive load for developers joining the project.

What specific coding conventions are extracted when documenting a code style?

The specific coding conventions extracted include file naming conventions, error handling patterns, module structure, and comment styles.

Do I need external linting dependencies to codify my team's coding style?

No external linting dependencies are required to codify your team's coding style; the Skill operates independently to analyze files and generate a Markdown style guide.