From govctl
Sets up govctl in the current project: installs Rust binary via cargo if missing, runs govctl init for governance structure and config.toml. Use before govctl workflows.
How this skill is triggered — by the user, by Claude, or both
Slash command
/govctl:initThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Set up govctl in the current project.
Set up govctl in the current project.
Outputs: Initialized governance structure, verified local setup, and a recommended next workflow.
govctl with cargo install govctl.govctl if it is already available. When working in the govctl repo itself, prefer cargo run --quiet -- before installing a global binary.govctl init./commit rather than embedding raw VCS commands here.govctl --version
If you are working in the govctl repository itself, prefer:
cargo run --quiet -- --version
If that works, use cargo run --quiet -- <subcommand> for the rest of this workflow instead of installing a global binary.
If no usable local invocation exists, ask permission, then install it:
cargo install govctl
If cargo is also missing, tell the user to install Rust first: https://rustup.rs
If gov/config.toml does not exist:
govctl init
If it already exists, skip — the project is already initialized.
govctl status
Show the user what was created and confirm everything is working.
/discuss for design work/spec for governance-only artifact maintenance/gov for implementation-bearing work/quick for trivial non-behavioral cleanupnpx claudepluginhub govctl-org/govctl --plugin govctlBootstraps repo-local governance (CLAUDE.md, README, VERSION) in empty or undocumented workspaces before feature workflows. Use for projects lacking clear structure.
Initializes new Python, Rust, or TypeScript projects interactively with git repo, GitHub workflows, pre-commit hooks, Makefile, and standard configs. Updates existing projects too.