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
Decision gist · record as of 2026-07-27
Detach removes govctl from your project safely, archiving governance history and requiring explicit confirmation before any changes. 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.
Use it when
- Detach's dry-run phase generates a detailed plan showing exactly which govctl-owned files will be removed.
- Yes.
Verify before relying
Read SKILL.md below before installing (1 file). Open directory: indexed for reading, not audited.
Install
govctl-org/govctl/detach · repository language: Rust
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently 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)
File tree — 1 file
.claude/skills/detach/SKILL.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Remove govctl integration from a project while preserving governance history”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
commit creates a coherent, single-outcome VCS change while enforcing governance rules and linking to active work items. It detects your repository type (Jujutsu or Git), validates against govctl policies, and ensures unrelated changes stay separate. The skill handles traceability, commit message formatting, and post-commit verification in one workflow.
migrate helps you add govctl governance to an established project by examining existing evidence—documentation, code structure, VCS history, and configuration—to recover consequential decisions and specifications. It guides you through a discovery phase, presents candidates for backfill as Architecture Decision Records, RFCs, or Work Items, and executes only authorized changes in small coherent batches. The workflow preserves traceability, respects existing artifact state, and stops when evidence conflicts or authorization is unclear.
discuss guides you through governance design conversations grounded in your repository's existing context. It helps identify constraints, compare design options, and produce durable artifacts like RFCs and ADRs that capture decisions and obligations without moving into implementation.
gov delivers substantive code changes within your repository's governance framework, enforcing RFC and ADR authority while maintaining work-item traceability. It establishes current state, validates against normative specifications, and ensures completion evidence before closure.
RFC Writer guides you through composing normative RFCs—product contracts with observable obligations, invariants, and compatibility rules. It enforces separation between specification prose and implementation details, ensures each clause is independently testable, and hands off lifecycle operations to dedicated governance tools. Use it to author the contract itself, not design rationale or execution scope.
Decision Analysis exposes assumptions, failure paths, and success conditions for high-stakes design choices. It uses premortem and backcast reasoning to rank options against constraints, reversibility, and evidence quality, then returns a risk-calibrated recommendation. The skill routes obligations and rationale to their authoritative destinations—RFC, ADR, Work Item, or verification—rather than creating artifacts itself.
More skills adr-writer (MIT) · trello (MIT)