style-guide

Define coding style rules for NixOS, Neovim, and Git configurations.

Updated May 16, 2019
One-click install
npx skills add https://github.com/cgeorgii/dots --skill style-guide-cgeorgii
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: style-guide
Source: https://github.com/cgeorgii/dots/tree/main/.claude/skills/style-guide
Command: npx skills add https://github.com/cgeorgii/dots --skill style-guide-cgeorgii

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coding style inconsistencies across NixOS configurations, Neovim setups, and Git workflows cause confusion and slow collaboration. A centralized set of rules reduces bikeshedding and speeds onboarding.

Core Features & Use Cases

  • Indentation, formatting, and naming conventions for NixOS, Neovim, and Git configurations.
  • Guidance on using tooling such as nixfmt for Nix code and consistent commit messages and documentation practices.
  • Use Case: Teams collaborating on NixOS configurations can align on style to speed up reviews and reduce bikeshedding.

Quick Start

Start by auditing your NixOS modules, Neovim configs, and Git workflows to align with the style guidelines.

Frequently Asked Questions about style-guide

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

FAQPage Schema
How do I enforce consistent coding style across NixOS, Neovim, and Git configurations?

To enforce consistent coding style, apply centralized rules for indentation, formatting, and naming conventions across NixOS modules, Neovim setups, and Git workflows to reduce collaboration friction.

What is the best way to format Nix code in a collaborative environment?

The best way to format Nix code is using nixfmt alongside defined style guidelines, ensuring consistent indentation and formatting across NixOS configurations to streamline collaborative version-control workflows.

How do I set up Neovim coding standards for a team?

To set up Neovim coding standards, define editor configurations that enforce consistent indentation, formatting, and naming conventions, aligning with your broader coding standards to speed up onboarding and reviews.

Do I need specific Git commit guidelines for NixOS configuration projects?

You need Git commit guidelines for NixOS projects to maintain consistent documentation practices and version-control workflows, which reduces confusion and accelerates collaboration when multiple contributors review configuration changes.

Can I use these style guidelines to audit existing configuration files?

You can use these style guidelines to audit existing NixOS modules, Neovim configs, and Git workflows by checking your current files against the specified indentation, formatting, and naming conventions to quickly align your setup.