code-standard

Enforce pragmatic coding standards across software development tasks.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/abereghici/skills --skill code-standard-abereghici
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-standard
Source: https://github.com/abereghici/skills/tree/main/skills/code-standard
Command: npx skills add https://github.com/abereghici/skills --skill code-standard-abereghici

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pragmatic coding standards help teams write concise, maintainable code, avoid over-engineering, and eliminate unnecessary comments across languages and frameworks.

Core Features & Use Cases

  • Rule-based guidelines (SRP, DRY, KISS, YAGNI) and explicit naming conventions.
  • One-thing-per-function philosophy, early guard clauses, and minimal nesting to improve readability.
  • Encourages inline self-documenting code and discourages unnecessary comments.

Quick Start

Start applying these pragmatic standards to every new file and code change to enforce clean, maintainable code.

Frequently Asked Questions about code-standard

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

FAQPage Schema
How do I enforce coding standards and clean code principles like SRP and DRY during refactoring?

To enforce clean code during refactoring, apply rule-based guidelines like SRP, DRY, KISS, and YAGNI alongside explicit naming conventions. This approach ensures concise, maintainable code while eliminating unnecessary comments and over-engineering across any language or framework.

What is the best way to improve code readability and reduce function nesting?

The best way to improve code readability is to adopt a one-thing-per-function philosophy using early guard clauses and minimal nesting. This pragmatic coding standard creates direct, self-documenting code that is easier to maintain and review.

Can I apply these coding standards across different languages and frameworks?

Yes, you can apply these coding standards across different languages and frameworks. The guidelines enforce language-agnostic principles like KISS, YAGNI, and clear naming to guide implementation and maintainability throughout writing, debugging, and code reviews.

When should I write comments vs self-documenting code?

You should write self-documenting code instead of unnecessary comments. This coding standard encourages inline self-documenting code through explicit naming conventions and clear logic, eliminating redundant comments while maintaining high code quality and readability.

How do I avoid over-engineering when writing maintainable code?

To avoid over-engineering when writing maintainable code, apply the YAGNI and KISS principles. These pragmatic coding standards ensure you write only what is necessary, keeping functions concise, direct, and focused on a single responsibility.

Does this code standard skill work for automated code reviews?

Yes, this code standard skill works for automated code reviews by enforcing pragmatic coding standards and core rules like SRP and DRY. It guides the review process to identify unnecessary nesting, unclear naming, and redundant comments across engineering tasks.