style-guide-adherence

Applies Google style guides and language best practices to code formatting and naming.

Updated Jan 1, 2026
One-click install
npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill style-guide-adherence-sarkarshivaditya-lab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: style-guide-adherence
Source: https://github.com/sarkarshivaditya-lab/WellMate/tree/main/.engineering-skills/troykelly-claude-skills/skills/style-guide-adherence
Command: npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill style-guide-adherence-sarkarshivaditya-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent code style across a codebase makes reviews slower and code harder to read. This Skill enforces a clear priority order—project style first, then Google style guides, then community best practices—so every file follows consistent naming, formatting, and import conventions. ## Core Features & Use Cases - Multi-language style rules: Concrete naming, formatting, and import-order conventions for TypeScript/JavaScript, Python, and Go, with links to all Google style guides. - Tooling enforcement: Maps each language to its formatter and linter (Prettier/ESLint, Black/Ruff, gofmt/golangci-lint) plus pre-commit hook configuration. - Project-style override handling: When a project's established style differs from Google style, the Skill follows the project style and documents the differences in CONTRIBUTING.md. - Use Case: While writing a new Python module, apply Google-style snake_case naming, 80-character line limits, isort-ordered imports, and Google-format docstrings before committing. ## Quick Start Review the code I just wrote and make it conform to the Google style guide for its language, fixing naming, formatting, and import order.

Frequently Asked Questions about style-guide-adherence

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

FAQPage Schema
How do I enforce Google style guide conventions in my code?

Apply the priority order: project-specific style first, then the Google style guide for your language, then community best practices. Automate enforcement with formatters like Prettier, Black, or gofmt plus linters like ESLint, Ruff, or golangci-lint.

What formatter and linter should I use for Python code style?

Use Black for formatting and Pylint or Ruff for linting, configured in pyproject.toml. Combine with isort to order imports into standard library, third-party, and local groups.

What naming conventions does the Google style guide use for TypeScript?

TypeScript uses PascalCase for classes and interfaces without an I prefix, camelCase for functions and variables, UPPER_SNAKE_CASE for constants, and kebab-case for file names. Private members do not use underscore prefixes.

What happens when project style differs from Google style?

Follow the project style, since consistency within the project takes priority. Document the differences in CONTRIBUTING.md and avoid mixing styles across the codebase.

How do I automatically check code style before committing?

Configure pre-commit hooks that run your project's format and lint commands, such as pnpm format and pnpm lint. Run the formatter first, then fix auto-fixable lint issues before committing.