coding-guidelines

Guide deliberate software changes with minimal scope and verification.

Updated May 25, 2026

Search Tags:#software engineering #code review #refactoring #implementation #coding #bug fixes

Ready to run

npx skills add https://github.com/Yairama/mine-rs --skill coding-guidelines-yairama

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps prevent common LLM coding mistakes by encouraging careful reasoning, minimal implementations, and disciplined changes before modifying software.

Core Features & Use Cases

Cautious Implementation Guidance: Encourages explicit assumptions, clarification of ambiguity, and consideration of simpler solutions before coding.
Focused Code Modification: Promotes surgical edits, avoiding unnecessary refactors, speculative features, and unrelated cleanup.
Goal-Driven Development: Helps define verification criteria for coding tasks such as bug fixes, refactoring, and feature implementation.

Quick Start

Use the coding-guidelines skill when modifying code to review assumptions, keep changes minimal, and verify implementation goals.

Frequently Asked Questions about coding-guidelines

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

FAQPage Schema

How do I prevent coding errors when implementing new software features?▼

Prevent coding errors during feature implementation by establishing explicit assumptions, clarifying ambiguity, and defining verification criteria before coding. Maintain focused code modifications and avoid unnecessary refactors to ensure safer software changes.

What is the best way to approach refactoring without breaking existing functionality?▼

Approach refactoring safely by enforcing minimal scope changes and surgical edits. Avoid unrelated cleanup and speculative features, ensuring disciplined reasoning and goal-driven verification criteria to preserve existing software functionality during code modifications.

How do I keep code modifications focused during bug fixes?▼

Keep code modifications focused during bug fixes by avoiding unnecessary refactors and speculative features. Define verification criteria upfront, apply surgical edits, and maintain minimal scope changes to ensure the bug fix does not introduce new coding errors.

Do I need to define verification criteria before starting a code review or implementation?▼

Yes, you need to define verification criteria before starting implementation. Goal-driven development requires establishing these criteria upfront to guide deliberate software changes, verify implementation success, and prevent common LLM coding mistakes during code modifications.

Why does adding speculative features during code modifications cause bugs?▼

Adding speculative features causes bugs because it expands the scope of code modifications beyond the original implementation goal. Unnecessary refactors and unrelated cleanup introduce untested changes, bypassing the disciplined reasoning needed for safer software changes.

When should I not use minimal scope changes for software engineering tasks?▼

You should not use minimal scope changes when a task explicitly requires broad architectural updates or large-scale refactoring. This approach focuses on surgical edits and cautious implementation, making it unsuitable for scenarios needing extensive, sweeping code modifications.