coding-implementation

Diagnose root causes and implement minimal scoped code changes with verification.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implement scoped code changes with minimal diffs and explicit verification after the goal, affected layer, and success criteria are clear.

Core Features & Use Cases

  • Scoped edits focus on root-cause fixes with minimal surface area.
  • Verification gates ensure changes are validated against the owning tests and workflows.
  • Clear handoff provides a repeatable process for code review and deployment.

Quick Start

Identify the goal and affected code path, then implement the smallest change that fixes the root cause and runs the verification.

Frequently Asked Questions about coding-implementation

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

FAQPage Schema
How do I make scoped code changes with minimal diffs?

Scoped code changes with minimal diffs require diagnosing the root cause, mapping the affected code path, applying the smallest surgical edit, and validating it against owning tests to ensure minimal surface area impact.

What is the best way to verify a root-cause fix before code handoff?

Verifying a root-cause fix requires running explicit verification gates against the owning tests and workflows, then delivering a proof run with results to ensure repeatable validation for code review and deployment.

How do I apply surgical edits to fix a bug without affecting unrelated code paths?

Surgical edits are applied by restating the goal, mapping the affected code paths and tests, and implementing the smallest change that fixes the root cause while keeping the diff surface area strictly minimal.

When do I need explicit verification gates in my engineering workflow?

Explicit verification gates are needed in an engineering workflow when delivering scoped changes, ensuring that surgical edits are validated against the owning tests and workflows to provide a repeatable handoff process.

Does this approach to code diffs work without setting up a specific testing framework?

Applying scoped code diffs with explicit verification relies on validating changes against existing owning tests and workflows, requiring a defined test environment to run the proof validation and deliver results.