Migrate Cobra-based CLIs and Go libraries into Forge project structures.
npx skills add https://github.com/reliant-labs/forge --skill cli-reliant-labs
Please help me install this Agent Skill. Skill: cli Source: https://github.com/reliant-labs/forge/tree/main/internal/templates/project/skills/forge/migration/cli Command: npx skills add https://github.com/reliant-labs/forge --skill cli-reliant-labs
This skill helps you migrate an existing Cobra-based CLI binary or Go library into the Forge project layout so you can keep evolving with Forge conventions, config, and generation workflows.
--kind cli (or --kind library) so you start with the expected modules, workspace layout, and forge.yaml.-next suffix at final renaming.forge generate is mostly a no-op for CLI kind, and when it still must be run to refresh mocks for internal/*/contract.go.Ask your AI assistant to scaffold your repository as a Forge CLI migration by running: forge new <name>-next --kind cli --mod github.com/<owner>/<name>-next.
High-intent search queries and answers about installing and using this skill.
To migrate a Cobra CLI to a Forge project structure, run the scaffold command with `--kind cli` or `--kind library`, then port your existing commands into internal packages. This aligns your project with Forge conventions and generation workflows.
Yes, you can use Forge generation to refresh mocks for internal contract files. While `forge generate` is mostly a no-op for CLI projects, it must still be run to refresh mocks defined in `internal/*/contract.go` files.
The correct way to handle binary naming during a Forge cutover is to initially scaffold the project with a `-next` suffix. You then point to the generated Cobra root file location and handle the suffix removal at final renaming.
A Go library migration requires a different Forge scaffold than a Cobra CLI. You must use `--kind library` for pure Go libraries and `--kind cli` for Cobra-based binaries to ensure the correct modules and workspace layout are created.
Your Forge project needs Go workspaces during a CLI migration to correctly structure the expected modules. Scaffolding with `--kind cli` creates the required workspace layout and `forge.yaml` configuration.
You should not use the Forge CLI kind for a Go project migration if your source is a pure Go library without Cobra commands. In that case, scaffolding with `--kind library` is the correct approach.
reliant-labsMigrate Go projects onto Forge scaffolds with safe porting order.
reliant-labsGenerates mocks and observability wiring from a contract.go file for Go packages.
JustineDevsAutomate Roblox UI component implementation from visual references with verification.
cacackAudit Go source code for idiomatic patterns, error handling, concurrency, and performance issues.