feat: recipe list (#2814)

[toyamagu-2021]

Signed-off-by: toyamagu2021 toyamagu-2021@gmail.com

Closes #2814

Motivation

• add recipe list

Verification

recipe list

 ./target/debug/goose recipe list              
github.com
  ✓ Logged in to github.com account toyamagu-2021 (keyring)
  - Active account: true
  - Git operations protocol: https
  - Token: gho_************************************
  - Token scopes: 'gist', 'read:org', 'repo', 'workflow'
Available recipes:
recipe - Create personalized, creative 404 pages using public profile data - local: ./recipe.yaml
create-pr - create-pr by diff - github: toyamagu-2021/shared-goose-recipe/create-pr
update-pr - update-pr based on current PR - github: toyamagu-2021/shared-goose-recipe/update-pr

recipe list --format json

➜ ./target/debug/goose recipe list --format json
github.com
  ✓ Logged in to github.com account toyamagu-2021 (keyring)
  - Active account: true
  - Git operations protocol: https
  - Token: gho_************************************
  - Token scopes: 'gist', 'read:org', 'repo', 'workflow'
[{"name":"recipe","source":"Local","path":"./recipe.yaml","title":"404Portfolio","description":"Create personalized, creative 404 pages using public profile data"},{"name":"create-pr","source":"GitHub","path":"toyamagu-2021/shared-goose-recipe/create-pr","title":"Create GitHub Pull Request","description":"create-pr by diff"},{"name":"update-pr","source":"GitHub","path":"toyamagu-2021/shared-goose-recipe/update-pr","title":"Update GitHub Pull Request Title and Description","description":"update-pr based on current PR"}]

recipe list --verbose

➜ ./target/debug/goose recipe list --verbose
github.com
  ✓ Logged in to github.com account toyamagu-2021 (keyring)
  - Active account: true
  - Git operations protocol: https
  - Token: gho_************************************
  - Token scopes: 'gist', 'read:org', 'repo', 'workflow'
Available recipes:
  recipe - Create personalized, creative 404 pages using public profile data - local: ./recipe.yaml
    Title: 404Portfolio
    Path: ./recipe.yaml
  temp - Create personalized, creative 404 pages using public profile data - local: ./temp.yaml
    Title: 404Portfolio
    Path: ./temp.yaml
  test - Create personalized, creative 404 pages using public profile data - local: recipes/test/test.yaml
    Title: 404Portfolio
    Path: recipes/test/test.yaml
  create-pr - create-pr by diff - github: toyamagu-2021/shared-goose-recipe/create-pr
    Title: Create GitHub Pull Request
    Path: toyamagu-2021/shared-goose-recipe/create-pr
  update-pr - update-pr based on current PR - github: toyamagu-2021/shared-goose-recipe/update-pr
    Title: Update GitHub Pull Request Title and Description
    Path: toyamagu-2021/shared-goose-recipe/update-pr

[alexhancock]

Could we include a more descriptive message explaining that the command relies on gh being installed and configured for auth?

I also wonder if we could interact with the API instead, and just have the user progress through an oauth flow?

[DOsinga]

actually we should just skip here and show the user the recipes that are accessible

[michaelneale]

in some cases goose will then offer to install it for you if the error is returned in an interactive way (eg if an MCP fails), wonder if can do similar here

[toyamagu-2021]

I have made the error message easier to understand.

Since ensure_gh_authenticated is executed beforehand, the login workflow will appear if you are not logged in, as shown below. You can authenticate within this workflow as follows:

➜  goose git:(feat/recipe-list) ./target/release/goose recipe list
You are not logged into any GitHub hosts. To log in, run: gh auth login
GitHub CLI is not authenticated. Launching `gh auth login`...
? Where do you use GitHub? GitHub.com
? How would you like to authenticate GitHub CLI? Login with a web browser