[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79C8THNP6FNEE4S5Z1HQNQQ":3,"skill-same:01M79C8THNP6FNEE4S5Z1HQNQQ":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M79C8THNP6FNEE4S5Z1HQNQQ","gh",null,"Patterns for invoking the GitHub CLI (gh) from agents. Covers structured output, pagination, repo targeting, search vs list, gh api fallback.","dhcgn\u002Fimmich-admin-cli","dhcgn","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6566207?v=4","01M79C8N70VH5NC77K0K15FS3N","Daniel","01M79C8N7Y7DR9KS4TYETQ9KJE",2,"MIT","https:\u002F\u002Fgithub.com\u002Fdhcgn\u002Fimmich-admin-cli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgh\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: gh\ndescription: Patterns for invoking the GitHub CLI (gh) from agents. Covers structured output, pagination, repo targeting, search vs list, gh api fallback.\n---\n\n# Reference\n\n## Interactivity policy\n\n`gh` already does the right thing in non-TTY contexts: it skips the pager,\nstrips ANSI color, and errors out fast with a helpful message instead of\nprompting (e.g. `must provide --title and --body when not running interactively`).\nYou don't need to defensively set `GH_PAGER` or pass `--no-pager` (no such\nflag exists).\n\n## Parsing JSON\n\nHuman output from `gh` is column-formatted. If you want structured data:\n\n- Add `--json field1,field2,...` for structured output.\n- Run a command with `--json` and **no field list** to print the full set of\n  available fields, then pick what you need.\n- Use `--jq '\u003Cexpr>'` for filtering without piping through a separate `jq`.\n- Use `--template '\u003Cgo-template>'` (alongside `--json`) when you want shaped\n  text output. Note that `--template`\u002F`-T` collides with a body-template flag\n  on a few commands (e.g. `gh pr create -T`, `gh issue create -T`); always\n  check `--help` before assuming which one you're hitting.\n\n## Pagination and silent truncation\n\nList commands cap results.\n\n- `gh issue list`, `gh pr list`, `gh search ...`: pass `-L N` (`--limit N`).\n  The default is usually 30.\n- `gh issue list` \u002F `gh pr list` do not expose aggregate totals like\n  `totalCount` via `--json`. If you need a true total, use `gh api graphql`\n  to query `totalCount`; otherwise, treat `-L` as the cap for the current call.\n- For raw API calls use `gh api --paginate \u003Cpath>`. Combine with\n  `--jq` and (optionally) `--slurp` to assemble one array.\n\n## Repo targeting\n\n`gh` infers the repo from the cwd's git remotes. \n\nPass `--repo OWNER\u002FREPO` (`-R`) to override the resolved CWD repo.\n\n## Search vs list\n\n- `gh search issues|prs|code|repos|commits|users` uses GitHub's search\n  index and accepts the full search syntax (`is:open`, `author:`,\n  `label:`, `repo:owner\u002Fname`, `in:title`, ...). Pass each qualifier as\n  its own bare token, not as one quoted string:\n  `gh search issues repo:cli\u002Fcli is:open author:monalisa` works, but\n  `gh search issues \"repo:cli\u002Fcli is:open\"` is treated as a single keyword (parsed as `repo:\"cli\u002Fcli is:open\"`)\n  and fails with `Invalid search query`. Quote only multi-word free text\n  (`gh search issues \"broken feature\"`). Most qualifiers also have a\n  dedicated flag (`--repo`, `--author`, `--label`, ...). Prefer search for\n  anything cross-repo or filtered by author\u002Flabel.\n- `gh issue list --search \"...\"` and `gh pr list --search \"...\"` take the\n  query as one quoted string (it is a flag value) and are scoped to one repo.\n- Bots author as GitHub Apps, so `--author dependabot` matches nothing. Use\n  `--app dependabot` (on `pr`\u002F`issue list` and `search prs|issues`; expands\n  to `author:app\u002F\u003Cslug>`) or `--author \"dependabot[bot]\"`.\n- `gh search issues` also takes `--search-type \u003Clexical|semantic|hybrid>`\n  (github.com\u002FGHEC only, issues only): use `semantic` when the user describes a\n  problem in natural language rather than exact terms, and `hybrid` to blend\n  keyword and semantic ranking; `lexical` (default) is exact matching.\n\n## Issue types, sub-issues, and relationships\n\nNewer `gh issue` subcommands model issue types, sub-issue hierarchy, and\nblocked-by\u002Fblocking relationships.\n\n- `gh issue create`: `--type \u003Cname>`, `--parent \u003Cnumber|url>` (creates the\n  new issue as a sub-issue), `--blocked-by \u003Cnumber|url,...>`, `--blocking \u003Cnumber|url,...>`.\n- `gh issue edit` (edits one or more issues in the same repo, e.g.\n  `gh issue edit 23 34`): `--type \u003Cname>` \u002F `--remove-type`,\n  `--parent \u003Cn|url>` \u002F `--remove-parent`,\n  `--add-sub-issue \u003Cn,n>` \u002F `--remove-sub-issue \u003Cn,n>`,\n  `--add-blocked-by \u003Cn,n>` \u002F `--remove-blocked-by \u003Cn,n>`,\n  `--add-blocking \u003Cn,n>` \u002F `--remove-blocking \u003Cn,n>`. Relationship and parent\n  refs are issue numbers or URLs; a URL may point to another repo on the same\n  host, but a different host is rejected. `--add-sub-issue` cannot be used\n  when editing more than one issue.\n- `gh issue list --type \u003Cname>` filters by issue type.\n- `gh issue view` and `gh issue list` accept these as `--json` fields (prefer\n  them over scraping the default text output): `issueType`, `parent`,\n  `subIssues`, `subIssuesSummary`, `blockedBy`, `blocking`. `subIssues`,\n  `blockedBy`, and `blocking` are objects shaped\n  `{\"nodes\": [...], \"totalCount\": N}` (not flat arrays), and `nodes` is capped\n  (`subIssues` at 100, `blockedBy`\u002F`blocking` at 50), so compare the node count\n  against `totalCount` to detect truncation.\n- GHES: issue types and sub-issues need 3.17+; blocked-by\u002Fblocking\n  relationships need 3.19+.\n\n## Attaching images and videos\n\n`--attach \u003Cpath>` is available on `gh issue create`, `gh issue edit`,\n`gh issue comment`, `gh pr create`, `gh pr edit`, and `gh pr comment`.\n\n- Repeat `--attach` to upload multiple files:\n  `gh issue comment 12 --attach .\u002Fbefore.png --attach .\u002Fafter.png`.\n- Each command invocation accepts at most 50 `--attach` values total across\n  images and videos.\n- Supported files are `png`, `jpg`, `jpeg`, `gif`, `webp`, `svg`, `mp4`,\n  `mov`, and `webm`.\n- For an image, append alt text to the path after `#`. Quote the value so the\n  shell does not treat `#` as a comment:\n  `gh pr create --attach '.\u002Flogin.png#The login error state'`. Without alt\n  text, the filename is used.\n- `--attach` paths and local Markdown destinations may be absolute or relative\n  to the directory where `gh` runs.\n- If the body references an attached path, `gh` rewrites that Markdown\n  reference to the uploaded URL. The reference keeps its existing alt text.\n  Otherwise, `gh` appends the attachment to the body. For example:\n  `gh pr edit 23 --body '![error](.\u002Flogin.png)' --attach .\u002Flogin.png`.\n- Videos cannot take alt text. A standalone `![recording](.\u002Frepro.mp4)` becomes\n  a bare player URL, while an inline video image becomes a link. A\n  reference-style video image such as `![recording][clip]` with\n  `[clip]: .\u002Frepro.mp4` is rejected; use a reference-style link instead.\n- `gh issue create` and `gh pr create`: `--attach` cannot be used with\n  `--web`. `gh pr create --attach` also cannot be used with `--dry-run`.\n- `gh issue edit`: `--attach` can edit only one issue at a time.\n- `gh issue comment` and `gh pr comment`: `--attach` cannot be used with\n  `--web` or `--delete-last`. It works alone, with `--edit-last`, or with one\n  of `--body`, `--body-file`, or `--editor`.\n- Uploads require GitHub.com or a GHE.com tenant, an OAuth token, classic PAT,\n  or fine-grained PAT, and `WRITE`, `MAINTAIN`, or `ADMIN` repository\n  permission. GitHub Enterprise Server and GitHub App tokens are unsupported.\n- Uploads stop at the first failure. If earlier files uploaded, `gh` still\n  writes those attachments and exits non-zero. Create and edit commands also\n  print the issue or pull request URL.\n\n## Discussions (`gh discussion`)\n\nPreview command set, subject to change. Subcommands:\n\n- `gh discussion list [--state open|closed|all] [--category \u003Cname>] [--author \u003Chandle>] [--label \u003Cname>,...] [--answered] [--search \u003Cquery>] [--sort created|updated] [--order asc|desc] [--limit N] [--after \u003Ccursor>] [--json \u003Cfields>] [--web]`\n  lists a repo's discussions. `--state` defaults to open, `--sort` to updated,\n  `--order` to desc. `--answered` is tri-state (`--answered=false` for\n  unanswered) for Q&A categories.\n- `gh discussion view {\u003Cnumber>|\u003Curl>|\u003Ccomment-id>|\u003Ccomment-url>} [--comments] [--order oldest|newest] [--limit N] [--after \u003Ccursor>] [--json \u003Cfields>] [--web]`\n  shows a discussion's body; add `--comments` for its comments, or pass a\n  comment ID\u002FURL as the argument to list that comment's replies (no\n  `--replies` flag; `--comments` is rejected with a comment argument).\n  `--order` (default newest), `--limit`, and `--after` apply only to comment\n  and reply listings.\n- `gh discussion create [--title \u003Ct>] [--body \u003Cb> | --body-file \u003Cpath>] [--category \u003Cname>] [--label \u003Cname>,...]`\n  creates a discussion. `--title`, a body (`--body` or `--body-file`), and\n  `--category` are required non-interactively; omitting any will prompt on a\n  terminal.\n- `gh discussion edit {\u003Cnumber>|\u003Curl>} [--title \u003Ct>] [--body \u003Cb>] [--body-file \u003Cpath>] [--category \u003Cname>] [--add-label \u003Cname>,...] [--remove-label \u003Cname>,...]`\n  edits title, body, category, or labels.\n- `gh discussion comment {\u003Cnumber>|\u003Cdiscussion-url>|\u003Ccomment-id>|\u003Ccomment-url>} [--body \u003Cb>] [--body-file \u003Cpath>] [--edit] [--delete] [--yes]`\n  adds a top-level comment (when given a discussion) or a reply (when given a\n  comment); `--edit` or `--delete` updates or removes a comment\u002Freply and\n  needs a comment ID or URL. `--yes` skips the `--delete` confirmation.\n- `--json`\u002F`--jq`\u002F`--template` are available on `list` and `view` only;\n  `create` and `edit` print the discussion URL. `comment` prints the discussion comment (or reply) URL.\n\n## Reading files and directories (`gh repo read-file` \u002F `read-dir`)\n\nPreview commands, subject to change. They read a repo's contents over the API\nwithout cloning, and honor `--repo OWNER\u002FREPO` (`-R`) and `--ref \u003Cbranch|tag|commit>`\n(default branch when omitted).\n\n- `gh repo read-file \u003Cpath> [--ref \u003Cref>] [--output \u003Cpath> [--clobber]] [--allow-escape-sequences] [--json \u003Cfields>] [--jq \u003Cexpr>]`\n  prints a file's contents. In non-TTY contexts the raw bytes go straight to\n  stdout (pipe-friendly); binary files are written as-is when piped but are\n  refused on a TTY. By default, a file containing terminal escape sequences is\n  refused; pass `--allow-escape-sequences` to read it anyway. `--output \u003Cpath>` (`-o`) writes to\n  disk instead of stdout (a trailing slash writes under a directory using the\n  remote file name; `--clobber` allows overwrite); writing to disk always\n  includes the raw bytes regardless of escape sequences. `--output` and `--json` are\n  mutually exclusive. `--json` fields include `name`, `path`, `gitSHA`, `size`,\n  `type`, `encoding`, and `content` (base64 encoded).\n- `gh repo read-dir [\u003Cpath>] [--ref \u003Cref>] [--json \u003Cfields>] [--jq \u003Cexpr>]`\n  lists a directory; with no path it lists the repo root. Non-TTY output is tab\n  separated as type, name, octal mode, and byte size. `--json` fields include\n  `name`, `path`, `type`, `gitType`, `mode`, `modeOctal`, `gitSHA`, `size`, and\n  `submodule`. A path pointing at a file errors and points you at `read-file`\n  (and vice versa).\n\n## Fall back to `gh api` for anything `--json` doesn't expose\n\nSometimes useful data isn't on the typed commands. Examples:\n\n- Review-thread comments on a PR: `gh api repos\u002F{owner}\u002F{repo}\u002Fpulls\u002F{n}\u002Fcomments`\n  (the `--comments` flag on `gh pr view` shows issue-level comments only).\n- Arbitrary GraphQL: `gh api graphql -f query='...' -F var=value`.\n- REST shortcuts: `gh api repos\u002F{owner}\u002F{repo}\u002F...` - note the\n  `{owner}\u002F{repo}` placeholder is filled in for you when run from a repo\n  with detected remotes; pass them literally if you want determinism.\n\n## Authentication\n\n- `gh auth status` prints the active host(s), user, and which env var (if\n  any) is being honored.\n- `gh auth status --json` is supported.\n\n## Other notes\n\n- `gh pr checkout \u003Cn>` switches branches. Use `gh pr diff \u003Cn>` or\n  `gh pr view \u003Cn>` if you only need to read.\n- `gh pr checkout \u003Cn> --worktree \u003Cpath>` checks the PR out into a git worktree\n  at `\u003Cpath>` instead of switching the current branch.\n- `gh issue develop \u003Cn> --checkout` creates a linked branch for the issue and\n  checks it out. Add `--worktree \u003Cpath>` to check that branch out into a git\n  worktree at `\u003Cpath>` instead of switching the current branch;\n  `--worktree` requires `--checkout`, cannot be blank, and cannot be combined\n  with `--list`.\n- `NO_COLOR`, `CLICOLOR_FORCE`, and `GH_FORCE_TTY` are honored. Set\n  `GH_FORCE_TTY=1` if you want TTY-style output (colors, tables, the\n  pager, interactivity) inside an agent harness; leave it unset unless needed.","# Reference\n\n## Interactivity policy\n\n`gh` already does the right thing in non-TTY contexts: it skips the pager,\nstrips ANSI color, and errors out fast with a helpful message instead of\nprompting (e.g. `must provide --title and --body when not running interactively`).\nYou don't need to defensively set `GH_PAGER` or pass `--no-pager` (no such\nflag exists).\n\n## Parsing JSON\n\nHuman output from `gh` is column-formatted. If you want structured data:\n\n- Add `--json field1,field2,...` for structured output.\n- Run a command with `--json` and **no field list** to print the full set of\n  available fields, then pick what you need.\n- Use `--jq '\u003Cexpr>'` for filtering without piping through a separate `jq`.\n- Use `--template '\u003Cgo-template>'` (alongside `--json`) when you want shaped\n  text output. Note that `--template`\u002F`-T` collides with a body-template flag\n  on a few commands (e.g. `gh pr create -T`, `gh issue create -T`); always\n  check `--help` before assuming which one you're hitting.\n\n## Pagination and silent truncation\n\nList commands cap results.\n\n- `gh issue list`, `gh pr list`, `gh search ...`: pass `-L N` (`--limit N`).\n  The default is usually 30.\n- `gh issue list` \u002F `gh pr list` do not expose aggregate totals like\n  `totalCount` via `--json`. If you need a true total, use `gh api graphql`\n  to query `totalCount`; otherwise, treat `-L` as the cap for the current call.\n- For raw API calls use `gh api --paginate \u003Cpath>`. Combine with\n  `--jq` and (optionally) `--slurp` to assemble one array.\n\n## Repo targeting\n\n`gh` infers the repo from the cwd's git remotes. \n\nPass `--repo OWNER\u002FREPO` (`-R`) to override the resolved CWD repo.\n\n## Search vs list\n\n- `gh search issues|prs|code|repos|commits|users` uses GitHub's search\n  index and accepts the full search syntax (`is:open`, `author:`,\n  `label:`, `repo:owner\u002Fname`, `in:title`, ...). Pass each qualifier as\n  its own bare token, not as one quoted string:\n  `gh search issues repo:cli\u002Fcli is:open author:monalisa` works, but\n  `gh search issues \"repo:cli\u002Fcli is:open\"` is treated as a single keyword (parsed as `repo:\"cli\u002Fcli is:open\"`)\n  and fails with `Invalid search query`. Quote only multi-word free text\n  (`gh search issues \"broken feature\"`). Most qualifiers also have a\n  dedicated flag (`--repo`, `--author`, `--label`, ...). Prefer search for\n  anything cross-repo or filtered by author\u002Flabel.\n- `gh issue list --search \"...\"` and `gh pr list --search \"...\"` take the\n  query as one quoted string (it is a flag value) and are scoped to one repo.\n- Bots author as GitHub Apps, so `--author dependabot` matches nothing. Use\n  `--app dependabot` (on `pr`\u002F`issue list` and `search prs|issues`; expands\n  to `author:app\u002F\u003Cslug>`) or `--author \"dependabot[bot]\"`.\n- `gh search issues` also takes `--search-type \u003Clexical|semantic|hybrid>`\n  (github.com\u002FGHEC only, issues only): use `semantic` when the user describes a\n  problem in natural language rather than exact terms, and `hybrid` to blend\n  keyword and semantic ranking; `lexical` (default) is exact matching.\n\n## Issue types, sub-issues, and relationships\n\nNewer `gh issue` subcommands model issue types, sub-issue hierarchy, and\nblocked-by\u002Fblocking relationships.\n\n- `gh issue create`: `--type \u003Cname>`, `--parent \u003Cnumber|url>` (creates the\n  new issue as a sub-issue), `--blocked-by \u003Cnumber|url,...>`, `--blocking \u003Cnumber|url,...>`.\n- `gh issue edit` (edits one or more issues in the same repo, e.g.\n  `gh issue edit 23 34`): `--type \u003Cname>` \u002F `--remove-type`,\n  `--parent \u003Cn|url>` \u002F `--remove-parent`,\n  `--add-sub-issue \u003Cn,n>` \u002F `--remove-sub-issue \u003Cn,n>`,\n  `--add-blocked-by \u003Cn,n>` \u002F `--remove-blocked-by \u003Cn,n>`,\n  `--add-blocking \u003Cn,n>` \u002F `--remove-blocking \u003Cn,n>`. Relationship and parent\n  refs are issue numbers or URLs; a URL may point to another repo on the same\n  host, but a different host is rejected. `--add-sub-issue` cannot be used\n  when editing more than one issue.\n- `gh issue list --type \u003Cname>` filters by issue type.\n- `gh issue view` and `gh issue list` accept these as `--json` fields (prefer\n  them over scraping the default text output): `issueType`, `parent`,\n  `subIssues`, `subIssuesSummary`, `blockedBy`, `blocking`. `subIssues`,\n  `blockedBy`, and `blocking` are objects shaped\n  `{\"nodes\": [...], \"totalCount\": N}` (not flat arrays), and `nodes` is capped\n  (`subIssues` at 100, `blockedBy`\u002F`blocking` at 50), so compare the node count\n  against `totalCount` to detect truncation.\n- GHES: issue types and sub-issues need 3.17+; blocked-by\u002Fblocking\n  relationships need 3.19+.\n\n## Attaching images and videos\n\n`--attach \u003Cpath>` is available on `gh issue create`, `gh issue edit`,\n`gh issue comment`, `gh pr create`, `gh pr edit`, and `gh pr comment`.\n\n- Repeat `--attach` to upload multiple files:\n  `gh issue comment 12 --attach .\u002Fbefore.png --attach .\u002Fafter.png`.\n- Each command invocation accepts at most 50 `--attach` values total across\n  images and videos.\n- Supported files are `png`, `jpg`, `jpeg`, `gif`, `webp`, `svg`, `mp4`,\n  `mov`, and `webm`.\n- For an image, append alt text to the path after `#`. Quote the value so the\n  shell does not treat `#` as a comment:\n  `gh pr create --attach '.\u002Flogin.png#The login error state'`. Without alt\n  text, the filename is used.\n- `--attach` paths and local Markdown destinations may be absolute or relative\n  to the directory where `gh` runs.\n- If the body references an attached path, `gh` rewrites that Markdown\n  reference to the uploaded URL. The reference keeps its existing alt text.\n  Otherwise, `gh` appends the attachment to the body. For example:\n  `gh pr edit 23 --body '![error](.\u002Flogin.png)' --attach .\u002Flogin.png`.\n- Videos cannot take alt text. A standalone `![recording](.\u002Frepro.mp4)` becomes\n  a bare player URL, while an inline video image becomes a link. A\n  reference-style video image such as `![recording][clip]` with\n  `[clip]: .\u002Frepro.mp4` is rejected; use a reference-style link instead.\n- `gh issue create` and `gh pr create`: `--attach` cannot be used with\n  `--web`. `gh pr create --attach` also cannot be used with `--dry-run`.\n- `gh issue edit`: `--attach` can edit only one issue at a time.\n- `gh issue comment` and `gh pr comment`: `--attach` cannot be used with\n  `--web` or `--delete-last`. It works alone, with `--edit-last`, or with one\n  of `--body`, `--body-file`, or `--editor`.\n- Uploads require GitHub.com or a GHE.com tenant, an OAuth token, classic PAT,\n  or fine-grained PAT, and `WRITE`, `MAINTAIN`, or `ADMIN` repository\n  permission. GitHub Enterprise Server and GitHub App tokens are unsupported.\n- Uploads stop at the first failure. If earlier files uploaded, `gh` still\n  writes those attachments and exits non-zero. Create and edit commands also\n  print the issue or pull request URL.\n\n## Discussions (`gh discussion`)\n\nPreview command set, subject to change. Subcommands:\n\n- `gh discussion list [--state open|closed|all] [--category \u003Cname>] [--author \u003Chandle>] [--label \u003Cname>,...] [--answered] [--search \u003Cquery>] [--sort created|updated] [--order asc|desc] [--limit N] [--after \u003Ccursor>] [--json \u003Cfields>] [--web]`\n  lists a repo's discussions. `--state` defaults to open, `--sort` to updated,\n  `--order` to desc. `--answered` is tri-state (`--answered=false` for\n  unanswered) for Q&A categories.\n- `gh discussion view {\u003Cnumber>|\u003Curl>|\u003Ccomment-id>|\u003Ccomment-url>} [--comments] [--order oldest|newest] [--limit N] [--after \u003Ccursor>] [--json \u003Cfields>] [--web]`\n  shows a discussion's body; add `--comments` for its comments, or pass a\n  comment ID\u002FURL as the argument to list that comment's replies (no\n  `--replies` flag; `--comments` is rejected with a comment argument).\n  `--order` (default newest), `--limit`, and `--after` apply only to comment\n  and reply listings.\n- `gh discussion create [--title \u003Ct>] [--body \u003Cb> | --body-file \u003Cpath>] [--category \u003Cname>] [--label \u003Cname>,...]`\n  creates a discussion. `--title`, a body (`--body` or `--body-file`), and\n  `--category` are required non-interactively; omitting any will prompt on a\n  terminal.\n- `gh discussion edit {\u003Cnumber>|\u003Curl>} [--title \u003Ct>] [--body \u003Cb>] [--body-file \u003Cpath>] [--category \u003Cname>] [--add-label \u003Cname>,...] [--remove-label \u003Cname>,...]`\n  edits title, body, category, or labels.\n- `gh discussion comment {\u003Cnumber>|\u003Cdiscussion-url>|\u003Ccomment-id>|\u003Ccomment-url>} [--body \u003Cb>] [--body-file \u003Cpath>] [--edit] [--delete] [--yes]`\n  adds a top-level comment (when given a discussion) or a reply (when given a\n  comment); `--edit` or `--delete` updates or removes a comment\u002Freply and\n  needs a comment ID or URL. `--yes` skips the `--delete` confirmation.\n- `--json`\u002F`--jq`\u002F`--template` are available on `list` and `view` only;\n  `create` and `edit` print the discussion URL. `comment` prints the discussion comment (or reply) URL.\n\n## Reading files and directories (`gh repo read-file` \u002F `read-dir`)\n\nPreview commands, subject to change. They read a repo's contents over the API\nwithout cloning, and honor `--repo OWNER\u002FREPO` (`-R`) and `--ref \u003Cbranch|tag|commit>`\n(default branch when omitted).\n\n- `gh repo read-file \u003Cpath> [--ref \u003Cref>] [--output \u003Cpath> [--clobber]] [--allow-escape-sequences] [--json \u003Cfields>] [--jq \u003Cexpr>]`\n  prints a file's contents. In non-TTY contexts the raw bytes go straight to\n  stdout (pipe-friendly); binary files are written as-is when piped but are\n  refused on a TTY. By default, a file containing terminal escape sequences is\n  refused; pass `--allow-escape-sequences` to read it anyway. `--output \u003Cpath>` (`-o`) writes to\n  disk instead of stdout (a trailing slash writes under a directory using the\n  remote file name; `--clobber` allows overwrite); writing to disk always\n  includes the raw bytes regardless of escape sequences. `--output` and `--json` are\n  mutually exclusive. `--json` fields include `name`, `path`, `gitSHA`, `size`,\n  `type`, `encoding`, and `content` (base64 encoded).\n- `gh repo read-dir [\u003Cpath>] [--ref \u003Cref>] [--json \u003Cfields>] [--jq \u003Cexpr>]`\n  lists a directory; with no path it lists the repo root. Non-TTY output is tab\n  separated as type, name, octal mode, and byte size. `--json` fields include\n  `name`, `path`, `type`, `gitType`, `mode`, `modeOctal`, `gitSHA`, `size`, and\n  `submodule`. A path pointing at a file errors and points you at `read-file`\n  (and vice versa).\n\n## Fall back to `gh api` for anything `--json` doesn't expose\n\nSometimes useful data isn't on the typed commands. Examples:\n\n- Review-thread comments on a PR: `gh api repos\u002F{owner}\u002F{repo}\u002Fpulls\u002F{n}\u002Fcomments`\n  (the `--comments` flag on `gh pr view` shows issue-level comments only).\n- Arbitrary GraphQL: `gh api graphql -f query='...' -F var=value`.\n- REST shortcuts: `gh api repos\u002F{owner}\u002F{repo}\u002F...` - note the\n  `{owner}\u002F{repo}` placeholder is filled in for you when run from a repo\n  with detected remotes; pass them literally if you want determinism.\n\n## Authentication\n\n- `gh auth status` prints the active host(s), user, and which env var (if\n  any) is being honored.\n- `gh auth status --json` is supported.\n\n## Other notes\n\n- `gh pr checkout \u003Cn>` switches branches. Use `gh pr diff \u003Cn>` or\n  `gh pr view \u003Cn>` if you only need to read.\n- `gh pr checkout \u003Cn> --worktree \u003Cpath>` checks the PR out into a git worktree\n  at `\u003Cpath>` instead of switching the current branch.\n- `gh issue develop \u003Cn> --checkout` creates a linked branch for the issue and\n  checks it out. Add `--worktree \u003Cpath>` to check that branch out into a git\n  worktree at `\u003Cpath>` instead of switching the current branch;\n  `--worktree` requires `--checkout`, cannot be blank, and cannot be combined\n  with `--list`.\n- `NO_COLOR`, `CLICOLOR_FORCE`, and `GH_FORCE_TTY` are honored. Set\n  `GH_FORCE_TTY=1` if you want TTY-style output (colors, tables, the\n  pager, interactivity) inside an agent harness; leave it unset unless needed.",{"name":5,"description":7},"main","ad3f6e2cb2cbbc5e8c6e4297889c80bd1492e6ee",".agents\u002Fskills\u002Fgh","https:\u002F\u002Fgithub.com\u002Fdhcgn\u002Fimmich-admin-cli","https:\u002F\u002Fgithub.com\u002Fdhcgn","https:\u002F\u002Fhdev.io\u002F","Father, Head of AI, Coach and Developer (Go\u002FC#).\r\nInto cryptography, confidential computing and post-quantum crypto.","2026-10-30 19:51:12",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add dhcgn\u002Fimmich-admin-cli --skill gh",{"tool":38,"command":39},"bunx","bunx skills add dhcgn\u002Fimmich-admin-cli --skill gh",{"tool":41,"command":42},"pnpm","pnpm dlx skills add dhcgn\u002Fimmich-admin-cli --skill gh","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdhcgn\u002Fimmich-admin-cli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgh\u002FSKILL.md",true,[],[47,53,60,67,74,81],{"skillNo":48,"name":49,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M79CAT3KJJVN9EH4MG3ZS475","immich-admin-cli","https:\u002F\u002Fgithub.com\u002Fdhcgn\u002Fimmich-admin-cli\u002Fblob\u002Fmain\u002Fimmich-admin-cli\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M79CAPHVJ2F3VFBJNCQXNAJG","wsl","Windows Subsystem for Linux (WSL) allows you to run a Linux environment directly on Windows, unmodified, without the overhead of a traditional virtual machine. If you need to run Linux commands, scripts, or applications on a Windows machine, WSL is the way to go. This skill provides guidance on how to use WSL effectively.","https:\u002F\u002Fgithub.com\u002Fdhcgn\u002Fimmich-admin-cli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwsl\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M79CAJX50X8219K95BQRW3R1","rtk","Prefix covered shell commands with rtk so output is filtered\u002Fcompressed before it reaches LLM context — git, gh, cargo, pytest, go test, docker, kubectl, aws, ls, grep, and more. Applies whenever a covered command is about to be executed in a shell.","https:\u002F\u002Fgithub.com\u002Fdhcgn\u002Fimmich-admin-cli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frtk\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M79CAC8XQREJV9SXQ6JEKJ7D","ponytail","Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says \"ponytail\", \"be lazy\", \"lazy mode\", \"simplest solution\", \"minimal solution\", \"yagni\", \"do less\", or \"shortest path\", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).","https:\u002F\u002Fgithub.com\u002Fdhcgn\u002Fimmich-admin-cli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fponytail\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M79CA837C6EWD2VVTCG03G8A","ponytail-review","Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says \"review for over-engineering\", \"what can we delete\", \"is this over-engineered\", \"simplify review\", or invokes \u002Fponytail-review. Complements correctness-focused review, this one only hunts complexity.","https:\u002F\u002Fgithub.com\u002Fdhcgn\u002Fimmich-admin-cli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fponytail-review\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M79CA3ZAFH4XFC624JWS270B","ponytail-help","Quick-reference card for all ponytail modes, skills, and commands. One-shot display, not a persistent mode. Trigger: \u002Fponytail-help, \"ponytail help\", \"what ponytail commands\", \"how do I use ponytail\".","https:\u002F\u002Fgithub.com\u002Fdhcgn\u002Fimmich-admin-cli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fponytail-help\u002FSKILL.md",[],[]]