code-style

Analyze project configuration and source code to enforce style conventions.

87|8|Updated Apr 9, 2025
One-click install
npx skills add https://github.com/FilenCloudDienste/filen-rs --skill code-style-filenclouddienste
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-style
Source: https://github.com/FilenCloudDienste/filen-rs/tree/main/.claude/skills/code-style
Command: npx skills add https://github.com/FilenCloudDienste/filen-rs --skill code-style-filenclouddienste

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that all code written or modified precisely matches the existing style conventions of a project, preventing stylistic inconsistencies and maintaining code quality.

Core Features & Use Cases

  • Automated Style Analysis: Scans project files and configuration to identify indentation, quoting, semicolon usage, brace style, and more.
  • Conflict Resolution: Prioritizes actual source code style over potentially outdated configuration files.
  • Use Case: Before contributing to an open-source Rust project, use this Skill to understand and apply its specific rustfmt.toml and .editorconfig settings, ensuring your code integrates seamlessly.

Quick Start

Analyze the current project's code style and prepare to apply it to all future code modifications.

Frequently Asked Questions about code-style

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

FAQPage Schema
How do I ensure new code matches existing project code style automatically?

To enforce code style, this Skill scans your project files and configuration to identify indentation, quoting, semicolon usage, brace style, and comment conventions. It applies these detected rules to all subsequent code modifications, preventing stylistic inconsistencies.

Can I apply code formatting rules across a monorepo with different languages?

Yes, you can apply formatting across a monorepo. The Skill supports monorepos and enforces language-agnostic rules via EditorConfig, ensuring consistent code style formatting across multiple project directories and languages.

What happens if my linter configuration conflicts with the actual source code style?

When configuration conflicts with actual source code style, the Skill prioritizes the real source code style over potentially outdated configuration files. It resolves discrepancies by analyzing the codebase directly to apply the correct formatting.

How do I analyze a project's code style before contributing to an open source repository?

To analyze a project's code style before contributing, the Skill scans configuration files like rustfmt.toml and .editorconfig. It identifies specific indentation, quotes, and brace conventions so your code modifications integrate seamlessly into the repository.

Does this tool work with language-agnostic formatting rules?

Yes, the tool works with language-agnostic formatting rules by leveraging EditorConfig. It reads EditorConfig settings to apply consistent code style, indentation, and trailing comma conventions across different programming languages in your project.