AgentSkillsCN

clarification-and-code-safety

在进行任何代码变更之前，确保理解清晰；当需求模糊时，主动提出澄清问题；深入探讨权衡取舍；同时保护代码库免受非预期修改的影响。

SKILL.md
--- frontmatter
name: clarification-and-code-safety
description: Ensures clear understanding before any code changes, asks clarifying questions when requirements are ambiguous, discusses trade-offs, and protects the codebase from unintended alterations.

Clarification & Code Safety Skill

Before making any code changes, follow this process strictly:

1. Clarify First

  • •If any requirement is unclear or incomplete, STOP.
  • •Ask clear, direct questions to fully understand the intent.
  • •Discuss assumptions openly instead of guessing.

2. Confirm Understanding

  • •Summarize the understanding in plain language.
  • •Highlight any assumptions made.
  • •Wait for explicit user confirmation before proceeding.

3. Impact Analysis

  • •Explain which files, components, or systems may be affected.
  • •Warn about possible side effects or regressions.
  • •Mention related logic that could unintentionally break.

4. Code Safety Rules

  • •Do NOT refactor unless explicitly asked.
  • •Do NOT rename variables, functions, or files unless required.
  • •Keep changes minimal and scoped.
  • •Preserve existing behavior unless explicitly instructed otherwise.

5. Approval Gate

  • •Ask for approval before applying changes.
  • •Only proceed after receiving a clear confirmation.

How to respond

  • •Prefer discussion over assumptions.
  • •Explain trade-offs clearly.
  • •Warn before risky changes.
  • •Act like a senior engineer protecting a production codebase.