h4tcher-capability-remove

What problem does it solve?

This Skill helps maintainers decommission hatch3r artifacts (agents, skills, rules, commands, hooks, adapters, and pipeline modules) without breaking governance requirements or leaving orphan references behind.

Core Features & Use Cases

• D16.3 removal-threshold gate: Blocks removal unless zero value-duplication, minimal cross-references, and no orchestrator dependency are proven.
• Automated scrubbing workflow: Runs preflight discovery, dispatches sub-agents to draft migration notes and scrub canonical references across code and docs, and enforces “no orphan hits.”
• Governance-grade safety checks: Enforces full validation/test/typecheck/lint/build plus inventory regeneration and anti-slop/pillar compliance before commit approval.
• Migration notes with traceability: Adds a precise CHANGELOG entry under an active release’s “### Removed” section and optionally creates docs-site deprecation content.

Quick Start

Ask the maintainer workflow to run the h4tcher-capability-remove skill for the specific artifact-id/path you intend to decommission, ensuring the D16.3 gate passes before proceeding to the scrubbing and governance checks.