메뉴
Pre-edit backup + post-edit validation for safe file edits. Use to capture file state before edits, validate changes after edits, revert files to prior state, or ensure edit safety via auto backup/validation hooks.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | cfn-edit-safety |
| description | Pre-edit backup + post-edit validation for safe file edits. Use to capture file state before edits, validate changes after edits, revert files to prior state, or ensure edit safety via auto backup/validation hooks. |
| version | 1.0.0 |
| tags | ["mega-skill","backup","hooks","validation","safety"] |
| status | production |
Version: 1.0.0 Purpose: Pre-edit backup and post-edit validation Status: Production Consolidates: cfn-hook-pipeline, pre-edit-backup Confidence: 8.5/10 (mandatory paired workflow in CLAUDE.md)
This mega-skill provides complete edit safety:
edit-safety/
├── SKILL.md
├── lib/
│ ├── backup/ # From pre-edit-backup
│ └── hooks/ # From cfn-hook-pipeline
└── cli/
edit-safety/lib/backup/ captures file stateedit-safety/lib/hooks/ validates changes| Old Path | New Path |
|---|---|
| pre-edit-backup/ | edit-safety/lib/backup/ |
| cfn-hook-pipeline/ | edit-safety/lib/hooks/ |
Tiered planning orchestrator. Runs the full SPARC+ pipeline (research, spec, decide, pseudo, data, arch, ux, design, test, ops) as a parallel DAG, scaled by build stage (mvp/beta/enterprise) via inclusion profiles. Enforces two gates: every success criterion is executable (verifiable-done) and every step is unambiguous (haiku-executable). Use as the entry point for any non-trivial build instead of cfn-spa-plan.
Post-planning completeness review. Extracts assumptions, traces dependencies, analyzes blast radius, checks alpha-readiness, surfaces gaps before implementation. Use after writing any plan that touches data, APIs, or shared state.
SPARC Specification phase. Make testable acceptance criteria, edge cases, pre/post conditions, invariants BEFORE planning implementation. Use when starting any non-trivial task to lock intent, surface ambiguity early.
Test-strategy phase of cfn-megaplan. Designs test depth properly: fixtures/test-data, the unit/integration/contract/e2e/load split, mocking strategy, and non-functional tests, instead of lumping everything into a vague red phase. Feeds Bar A (verifiable-done): every acceptance criterion becomes a concrete runnable check. Use after cfn-spec, cfn-arch, and (if frontend) cfn-ux.
Extract complete Redis coordination data from completed CFN Loop tasks and structure into comprehensive JSON analysis files
Coordinates FAST code generation via Z.ai glm-4.6 with CodeSearch pattern learning. Use when agents need rapid test generation, bulk code creation, or repetitive boilerplate. Tracks successful prompts for continuous improvement. Ideal for high-volume, low-complexity code tasks.