skills.rest
angrysky56
angrysky56COMMUNITY
Explore all skills by this author →
GitHub

coder

Review codebase context before editing to ensure minimal, verified code changes.

Updated May 24, 2026
Search Tags:#software development#code editing#code verification#bug fixes#surgical changes#targeted refactoring
One-click install
npx skills add https://github.com/angrysky56/hermes-ops --skill coder-angrysky56
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coder
Source: https://github.com/angrysky56/hermes-ops/tree/main/skills/coder
Command: npx skills add https://github.com/angrysky56/hermes-ops --skill coder-angrysky56

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of unplanned, messy code edits that introduce bugs, break existing functionality, and waste development time by enforcing structured, thoughtful coding practices before any changes are made.

Core Features & Use Cases

  • Pre-Edit Context Review: Requires reading full codebase context and understanding data flow before opening any files to edit.
  • Simplicity-First Approach: Prioritizes the simplest working solution over complex, over-engineered alternatives.
  • Surgical Targeted Changes: Modifies only the exact code required for the task, with no unrequested refactoring of adjacent code.
  • Step-by-Step Verification: Validates each change produces the expected output before proceeding to the next step. A common use case is fixing critical bugs in production modules: this Skill ensures you only edit the relevant faulty logic instead of refactoring unrelated code, and verifies the fix works with existing tests before marking the task complete.

Quick Start

Use the coder skill to fix the login timeout bug in the auth module and confirm the fix passes all existing test cases.

Frequently Asked Questions about coder

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

FAQPage Schema
How do I make surgical code edits without breaking existing functionality?▼

Surgical code edits require a pre-edit context review to understand data flow before modifying files. By prioritizing the simplest working solution and validating each change step-by-step, you eliminate unplanned modifications and preserve existing functionality.

What is the best way to fix critical bugs in production modules safely?▼

Fixing critical bugs safely involves enforcing structured coding practices by reading full codebase context first. This ensures you modify only the exact faulty logic instead of refactoring unrelated code, then verifies the fix works with existing tests before completion.

How do I prevent unplanned refactoring of adjacent code during bug fixes?▼

Preventing unplanned refactoring requires a simplicity-first approach that modifies only the exact code required for the task. By enforcing pre-edit codebase context review, you ensure targeted changes without unrequested modifications to adjacent code.

Does targeted refactoring require reading the full codebase context before editing?▼

Targeted refactoring requires reading full codebase context and understanding data flow before opening any files. This pre-edit review eliminates error-prone modifications by ensuring you only modify the exact code necessary for the minimal, non-disruptive changes.

How do I verify step-by-step output during software development tasks?▼

Step-by-step output verification validates each change produces the expected output before proceeding to the next step. This ensures code edits satisfy functional requirements by confirming each modification works correctly with existing tests and functionality.

When should I not use automated code editing for bug fixes?▼

You should avoid automated code editing when it bypasses pre-edit codebase context review and data flow understanding. Without enforcing structured practices and step-by-step output verification, automated edits risk introducing bugs and breaking existing functionality.

Related Skills

Explore More Software Engineering Skills→
diShine-digital-agencydiShine-digital-agency
1

shine-map-codebase

Map existing codebases into a structured seven-document codebase map.

Community
Advanced
OutlineDrivenOutlineDriven
5

proceed

Execute predefined implementation plans with per-step verification and optional VCS steps.

Official
Advanced
faramirezsfaramirezs

test-driven-development

Enforce a RED-GREEN-REFACTOR cycle for test-driven development workflows.

Community
Intermediate
louderthanthunderx1louderthanthunderx1

karpathy-guidelines

Provide decision-making guidelines for LLM-assisted coding tasks.

Community
Intermediate