跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
开发与测试

ln-35-surgical-change-implementer

Implements a bounded product-code change through the smallest complete root-cause solution. Use for scoped delivery; not for planning, review, audit, upgrades, modernization, or tuning.

levnikolaevich · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add levnikolaevich/claude-code-skills --skill ln-35-surgical-change-implementer

技能说明


name: ln-35-surgical-change-implementer description: "Implements a bounded product-code change through the smallest complete root-cause solution. Use for scoped delivery; not for planning, review, audit, upgrades, modernization, or tuning."

Surgical Change Implementer

Goal: Deliver one approved product-code change through the smallest complete solution that satisfies the business outcome. Remove superseded code and avoid AI slop, speculative abstraction, duplicate mechanisms, and custom infrastructure already provided by the repository or platform.

Execution contract: Treat the ordered checkbox workflow below as this skill's Definition of Done. Track every checkbox as PENDING, then resolve it to PROVEN with concrete evidence, CLEARED with evidence that its conditional trigger is absent, or UNPROVEN; reading, mentioning, delegating, skipping, or tool failure is not proof. Before returning, resolve every PENDING, count only PROVEN and CLEARED items as complete, apply this skill's verdict, decision, and approval rules to every UNPROVEN, and prepend Checklist: X/Y completeIncomplete: None | section/item — reason; outcome impact; exact next action; list every UNPROVEN item.

Tool Routing

NeedPreferred capabilityFallback
Scope and repository policyUser request, linked task or plan, repository instructions, Git status, and focused diffState bounded assumptions; stop if a choice would materially change product intent
Runtime ownership and impactLanguage server, host-native code intelligence, traces, schemas, routes, and configurationNarrow symbol and text search followed by direct reads of definitions and consumers
Existing capabilityRepository code, manifests, lockfiles, platform APIs, and installed dependency sourceCurrent official documentation and primary sources; mark uncertain claims UNVERIFIED
Safe implementationFocused editor, native formatter, package manager, and generation commandsMinimal manual patch that preserves user changes and generated-file ownership
VerificationRepository-defined build, lint, type, test, smoke, and runtime checksSmallest reproducible check that proves the protected contract; disclose coverage gaps
External semanticsOfficial documentation, specifications, security advisories, registries, and upstream sourcePrimary-source technical material; use secondary expert guidance only for tradeoffs

Do not expand the task into repository-wide cleanup, redesign, dependency work, or performance tuning. Do not modify external systems, persisted data, public contracts, user experience, or unrelated dirty files without explicit authority.

Core Rules

  • KISS is a hard constraint: prefer the fewest concepts, branches, states, files, dependencies, and changed lines that form a complete design.
  • Surgical does not mean superficial. Fix the owning cause once; do not hide it behind adapters, aliases, parallel paths, copied logic, or compatibility layers without a proven consumer.
  • Existing code is not automatically correct, and new code is not automatically necessary. Subtraction, configuration, or no code can be the best implementation.
  • Repository policies, architecture decisions, public contracts, security boundaries, logging and error conventions, and generated-code ownership constrain the solution.
  • Research a concrete semantic or design uncertainty before coding. Prefer current official documentation; record why its guidance applies to the installed version and repository context.
  • Reject an external package when its dependency, license, security, runtime, bundle, operational, or exit cost exceeds the custom behavior it removes.
  • Preserve current user-visible behavior unless the task explicitly changes it. Report every new screen, message, or scenario; never alter an existing flow merely as a refactoring side effect.
  • Never sacrifice correctness, security, data integrity, diagnosability, accessibility, or required compatibility to minimize code.

Checklist

1. Establish the Change Contract

  • Resolve the requested business outcome, affected users or operators, acceptance evidence, constraints, protected behavior, explicit non-goals, and approved mutation scope.
  • Read repository instructions, relevant policies and architecture decisions, and the named task or plan; convert each applicable requirement into a traceable acceptance row.
  • Inspect Git status and the target files before editing; distinguish baseline defects and user-owned changes from work authorized by this task.
  • Trace the actual runtime path from observable entrypoint through owning logic, state, persistence or integrations, and failure handling; do not infer ownership from filenames alone.
  • Inventory public and internal contracts, callers, configuration, data shapes, tests, documentation, and operational behavior that the change can affect.
  • Identify decisions that would alter product intent, user experience, public compatibility, data, dependencies, or external state and obtain direction before making them.
  • Return BLOCKED when the business outcome, ownership boundary, safe edit scope, or essential verification cannot be established without inventing intent.

2. Choose the Smallest Complete Solution

  • Test NO_CHANGE: determine whether current behavior already satisfies the outcome or whether documentation, configuration, or usage correction resolves the request without product-code edits.
  • Test DELETE_OR_CONFIGURE: identify an obsolete path, wrong default, redundant state, feature flag, registration, or configuration that can be removed or corrected directly.
  • Test REUSE_LOCAL: search for the repository's canonical helper, component, service, policy, type, enum, constant, error, or integration before adding another concept.
  • Test USE_PLATFORM_OR_STDLIB: verify whether the language, runtime,
阅读完整来源 ↗