Feature Request: Add goose recipe list

[toyamagu-2021]

Please explain the motivation behind the feature request.

Currently, Goose CLI provides recipe management commands like validate and deeplink, but there's no way to discover what recipes are available. Users must know the exact recipe name to use them, which creates a poor discovery experience. This feature would solve the problem of recipe discoverability by allowing users to see all available recipes from both local directories and configured GitHub repositories.

Describe the solution you'd like

Add a new goose recipe list command that displays all available recipes from both local and remote sources. The command should:

1. Search the same locations as the existing recipe retrieval system
2. Support multiple output formats (text and JSON) for both human and programmatic use
3. Include a verbose mode that shows recipe titles and descriptions
4. Follow the existing CLI patterns established by other recipe commands

The implementation would extend the existing RecipeCommand enum and leverage the current recipe search infrastructure that already handles both local paths and GitHub repositories.

Describe alternatives you've considered

Alternative approaches considered: N/A

Additional context

This feature builds on the existing recipe infrastructure in Goose CLI. The current recipe system already supports:

• Local recipe discovery via GOOSE_RECIPE_PATH environment variable
• GitHub repository integration via GOOSE_RECIPE_GITHUB_REPO configuration
• Recipe validation and sharing capabilities

The implementation would be consistent with other CLI tools that provide list commands (e.g., docker images, kubectl get pods) and would enhance the developer experience by making recipe discovery as easy as recipe execution.

• I have verified this does not duplicate an existing feature request###

[DOsinga]

I like this a lot - one question though is how to recognize something as a recipe. currently they can have a yaml or json extension, so listing all those is probably no good. so we'd possibly have to load them all up to see which one are valid

[toyamagu-2021]

Only recipe.yaml or recipe.json are valid as shared-recipe files, as shown here. Therefore, it should be sufficient to query only for these.

[DOsinga]

yes, all recipes are either .yaml or .json, but not all yaml or jsons are valid recipes is my point. but we can fix that up later too!

[toyamagu-2021]

In the current implementation, only valid recipes are listed, and invalid ones are not. It might be clearer to mark them as invalid.

https://github.com/toyamagu-2021/goose/blob/b85f9cf74d6e9948b8543ca4c99e2621eadb2db0/crates/goose-cli/src/recipes/github_recipe.rs#L246-L247