CC Core Defensive
SkillDev toolsGeneral defensive coding guidelines for cross-language code changes: minimal edits, handling real boundaries, targeted verification, and constraining over-engineering or abstraction driven by hypothetical risks; does not cover language-specific details, formal review, or structured debugging.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the CC Core Defensive skill
What this skill tells your AI
The instructions your AI receives, as published by doccker/cc-use-exp in .codex/skills/cc-core-defensive/SKILL.md and read by ahel’s review.
在修改现有代码、配置或脚本时，优先使用本技能控制改动范围、决策方式和验证深度。
不要用于：
- 语言或框架细节
- 正式 code review 工作流
- 结构化 debug 工作流
- 生产环境或系统级操作安全
核心规则
- 优先做最小有效改动。
- 优先复用现有模式，再考虑新抽象。
- 根因清楚时修根因；根因不清楚时先继续收集证据。
- 不修改测试去适配错误实现。
- 缺失真实边界上的必要校验和错误处理、明显回归都算真实问题。
- 不要为了假想风险增加吞错逻辑、额外包装层或无需求的容灾状态。
- 改动后做受影响范围内最小但有意义的验证。
工作方式
- 先读相关代码路径，再决定怎么改。
- 明确当前问题边界和直接影响面。
- 做最小改动。
- 做定向验证。
- 若必须扩大范围，先明确说明原因。
按需展开
- 边界判断：
references/change-boundary.md - 验证深度：
references/verification.md - 决策原则：
references/decision-principles.md
Signals
- GitHub stars
- 1k
- Forks
- 112
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
cc-core-defensive- Source
- github.com/doccker/cc-use-exp