coding-guidelines

Apply behavioral guidelines to writing, reviewing, and refactoring code.

59|14|Updated Mar 10, 2026

Search Tags:#debugging #quality #coding #guidelines #best-practices #code-review

Ready to run

npx skills add https://github.com/guilhermemarketing/esc-skills --skill coding-guidelines-guilhermemarketing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: coding-guidelines
Source: https://github.com/guilhermemarketing/esc-skills/tree/main/skills/coding-guidelines
Command: npx skills add https://github.com/guilhermemarketing/esc-skills --skill coding-guidelines-guilhermemarketing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides behavioral guidelines to help engineers and AI agents avoid common coding mistakes during writing, modification, and review, promoting safer, clearer, and more maintainable code.

Core Features & Use Cases

Explicit reasoning: require stating assumptions and surfacing tradeoffs before coding.
Minimal changes: encourage surgical edits and avoidance of unnecessary refactors.
Consistency and safety: enforce consistent style, alignment with existing code, and traceable changes across implementation, debugging, and reviews.

Quick Start

Follow these guidelines when you write or review code to minimize mistakes and maximize clarity.

Frequently Asked Questions about coding-guidelines

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

FAQPage Schema

How do I identify and fix common coding mistakes during code review?▼

To identify and fix coding mistakes during code review, apply structured behavioral guidelines that enforce consistency, minimal changes, and explicit validation. This surfaces assumptions and tradeoffs before code is merged.

What are the best practices for writing maintainable code with minimal changes?▼

Best practices for maintainable code include making surgical edits, avoiding unnecessary refactors, and enforcing consistent style alignment. Explicit reasoning and traceable changes ensure clarity across diverse projects.

How can I prevent unnecessary refactoring when modifying existing code?▼

Prevent unnecessary refactoring by applying behavioral guidelines that encourage minimal, surgical edits. This approach requires stating assumptions first and ensuring changes align with the existing codebase safely.

Does applying coding guidelines help with debugging and maintenance tasks?▼

Applying coding guidelines directly supports debugging and maintenance by providing step-by-step guidance and guardrails. This structured approach ensures traceable changes and explicit validation across implementation tasks.

What is the best way to enforce code quality and consistency across diverse teams?▼

Enforce code quality and consistency by applying structured behavioral guidelines to writing and reviewing code. This requires engineers to state assumptions, surface tradeoffs, and maintain alignment with existing project standards.

When should I require explicit reasoning and assumption surfacing before coding?▼

Require explicit reasoning before coding to prevent common mistakes during implementation and review. Surfacing assumptions and tradeoffs early promotes safer, clearer, and more maintainable code across all project modifications.