spec-kitty-bulk-edit-classification

What problem does it solve?

This Skill prevents silent breakage by recognizing when a user request requires changing the same existing string (e.g., identifier, path, key, label) across many files and then enforcing the occurrence-classification workflow before implementation.

Core Features & Use Cases

• Bulk edit intent detection: Identifies rename/migration patterns and gate error messages that indicate a bulk-edit scenario.
• Guardrail activation during specify/plan: Sets the mission to change_mode: bulk_edit, ensures the rename target is explicitly named, and prepares the required classification artifact.
• Occurrence map generation with validation constraints: Produces a occurrence_map.yaml with all required standard categories and valid per-category actions so the runtime gate can reliably check admissibility and diff compliance.

Quick Start

Ask the AI to plan a cross-codebase rename like "Rename Customer to Account across the codebase" and ensure it prepares an occurrence map for approval before any changes are made.