style

Enforce coding and review conventions across git repository changes.

4|2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/alexanderguy/skills --skill style-alexanderguy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: style
Source: https://github.com/alexanderguy/skills/tree/main/skills/style
Command: npx skills add https://github.com/alexanderguy/skills --skill style-alexanderguy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents messy, hard-to-maintain code by enforcing consistent engineering conventions during writing and review.

Core Features & Use Cases

  • Documentation discipline: Avoids redundant comments and ensures TODO markers represent real external blockers.
  • Commit and git workflow quality: Establishes commit-message structure and safe history editing practices.
  • Scope and change hygiene: Reduces drive-by changes and clarifies what is truly in scope.
  • Safer engineering defaults: Requires data validation at boundaries and mandates full build verification.
  • Attribution and compliance: Guides safe handling of external code with licensing and audit-friendly commits.

Quick Start

Load the style skill and use it to check a proposed change for scope discipline, comment/TODO misuse, and whether a full build verification is required.

Frequently Asked Questions about style

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

FAQPage Schema
How do I enforce clean code conventions during a code review?

Code review conventions are enforced by checking changes for redundant comments, proper TODO usage, disciplined scope, and boundary data validation. This ensures clean, maintainable code by applying consistent engineering standards across any programming language.

What is the proper structure for git commit messages and workflow?

Proper git workflow requires a structured commit-message format and safe history editing practices. It enforces clean coding conventions by standardizing how changes are documented and attributed in the repository.

How do I handle external code attribution and compliance in a git repository?

External code attribution is handled by guiding safe integration with licensing and audit-friendly commits. This maintains clean, maintainable code by ensuring proper compliance tracking when incorporating external changes.

Why does my code build verification fail before marking work complete?

Build verification fails because running the full build is mandated before marking work complete. This enforces clean coding conventions by ensuring all changes compile and function correctly without introducing regressions.

When should I use TODO markers and data validation during refactoring?

TODO markers should represent real external blockers, and data validation is required at boundaries during refactoring. This enforces clean, maintainable code by preventing misuse and ensuring safer engineering defaults.

Does this coding conventions skill apply to any programming language?

Yes, this coding conventions skill applies to any programming language. It enforces clean, maintainable code by applying consistent engineering standards for documentation, refactoring, and git workflow regardless of the language used.