detach
Detach cleanly unwinds govctl integration from a project through an ownership-aware process that archives the governance tree, identifies and removes only project-local assets, and surgically edits configuration to eliminate integration hooks. Every mutation requires explicit approval after a detailed dry-run plan, and the skill preserves governance history, unrelated user configuration, and meaningful context throughout.
Detach removes govctl from your project safely, archiving governance history and requiring explicit confirmation before any changes.
AI-generated summary based on this skill's SKILL.md
Install
govctl-org/govctl/detach · repository language: Rust
git clone https://github.com/govctl-org/govctl
cp -r govctl/.claude/skills/detach ~/.claude/skills/detachnpx skillfed install govctl-org/govctl/detachFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I remove govctl from my project safely?
Detach provides a safe removal process for govctl integration. It archives your governance tree, identifies project-local assets owned by govctl, and surgically removes only those files while preserving unrelated configuration. Every change requires explicit approval after reviewing a detailed dry-run plan, ensuring governance history and user data remain intact.
What does detach do during a dry-run confirmation?
Detach's dry-run phase generates a detailed plan showing exactly which govctl-owned files will be removed, which configuration hooks will be edited, and what governance history will be archived. You review this plan before approving any mutations, giving you full visibility into the detachment process before changes take effect.
Can detach preserve my governance history when I uninstall govctl?
Yes. Detach archives your complete governance tree as part of the detachment process, preserving all historical context. This archive enables recovery if you need to restore govctl integration later, and ensures your governance decisions remain documented even after removing the active integration.
How does detach avoid deleting my own project configuration?
Detach uses ownership awareness to distinguish govctl-owned assets from your project's own files. It identifies and removes only integration-specific assets while leaving unrelated configuration untouched. This surgical approach prevents accidental loss of your own settings during cleanup.
Can I restore govctl after using detach if removal fails?
Yes. Detach archives all govctl configuration and assets during the detachment process. If you need to reverse the removal or restore integration, the archived materials enable recovery, allowing you to reinstate govctl integration without losing the governance context that was preserved.
What is the detach skill's license?
Detach is released under the MIT license, allowing free use, modification, and distribution with minimal restrictions.
SKILL.md
rendered from the published skill — quoted content, verbatim
Detach Govctl
Stop using govctl in a project while preserving its governance history and unrelated user configuration. Detachment is destructive integration cleanup, not artifact deletion.
Read-Only Inventory
Do not mutate anything during discovery. Inspect:
gov/config.tomland the fullgov/tree;- configured documentation, source-scan, and agent-asset paths;
- project-local skills and reviewer agents attributable to govctl;
- hooks, plugin metadata, project instructions, and editor configuration that invoke or require govctl;
[[RFC-...]],[[ADR-...]],[[WI-...]], and other governed references in source and configuration; and- the logical-to-resolved mapping for every candidate path, using symlink metadata to inspect each existing ancestor without assuming containment; and
- existing
gov.archived/, working-copy changes, ignore rules, and destination collisions.
Use structured
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
.claude/skills/detach/SKILL.md