[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7587Y8NX94228WP508KKPKT":3,"skill-same:01M7587Y8NX94228WP508KKPKT":45},{"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":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7587Y8NX94228WP508KKPKT","gnit-release",null,"Cuts a Gnit release: runs pre-release checks (fmt, clippy, tests, clean tree, auth, fetched tags), proposes the next semver from the commits since the last tag, sweeps docs (README, site guide, the bundled CLI skill) for release-tied updates, bumps the version in Cargo.toml and Cargo.lock, commits and pushes the bump to master, then tags vX.Y.Z and pushes the tag so the tag-driven release workflow builds the binaries and publishes the GitHub release. Use this skill whenever the user says \"release\", \"cut a release\", \"new version\", \"bump the version\", \"ship vX.Y.Z\", or anything about shipping a new version of gnit.","mostlydev\u002Fgnit","mostlydev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F67087?v=4","01M6CHTC319DK6Z2ASSDJFQ50V","Wojtek Grabski","01M7587QRY0RPJ5YGGE1BWB8DE",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmostlydev\u002Fgnit\u002Fblob\u002Fmaster\u002Fskills\u002Fgnit-release\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: gnit-release\ndescription: >\n  Cuts a Gnit release: runs pre-release checks (fmt, clippy, tests, clean tree,\n  auth, fetched tags), proposes the next semver from the commits since the last\n  tag, sweeps docs (README, site guide, the bundled CLI skill) for release-tied\n  updates, bumps the version in Cargo.toml and Cargo.lock, commits and pushes the\n  bump to master, then tags vX.Y.Z and pushes the tag so the tag-driven release\n  workflow builds the binaries and publishes the GitHub release. Use this skill\n  whenever the user says \"release\", \"cut a release\", \"new version\", \"bump the\n  version\", \"ship vX.Y.Z\", or anything about shipping a new version of gnit.\n---\n\n# Gnit release\n\nThis skill cuts a release of the `gnit` CLI. The pipeline is **tag-driven**:\npushing a `v*` tag triggers `.github\u002Fworkflows\u002Frelease.yml`, which builds the\nbinaries for every target and publishes the GitHub release. Two other workflows\nreact to the same push to `master`: `ci.yml` (fmt + clippy + tests on Ubuntu and\nmacOS) and `deploy-site.yml` (redeploys the VitePress site).\n\nGnit is a single Rust binary with no submodules, no Docker images, and no runtime\ninfra pins — so a release is just: get `master` green and version-bumped, push\nit, then push the tag. The release workflow does the building and publishing.\n\nYour job is to prepare everything locally, push the version-bump commit to\n`master`, then push the release tag and verify the workflows go green.\n\n## Step 1: Pre-release sanity checks\n\n```bash\n# Clean working tree — don't fold unrelated work into a release.\ngit status --short\n\n# Local tags lag the remote badly; sync before you reason about versions.\ngit fetch --tags\n\n# Releases publish via gh in the workflow, but check your own auth for the\n# manual steps (release notes, verification).\ngh auth status\n\n# Run the exact gate CI runs on the tag. If this fails locally, the release\n# build fails too.\ncargo fmt --check\ncargo clippy --all-targets -- -D warnings\ncargo test --locked\n```\n\nIf the working tree is dirty, decide with the user whether those changes belong\nin this release or should be committed\u002Fstashed separately.\n\nCI runs clippy with the **current stable** toolchain and `-D warnings`. If your\nlocal toolchain lags, a lint that is clean locally can fail CI on the tag. Run\n`rustup update stable && cargo clippy --all-targets -- -D warnings` before\ntagging to catch newer lints in one pass.\n\n## Step 2: Determine the version\n\n```bash\ngit tag --sort=-v:refname | head -3      # latest tags\ngh release list --limit 5                # latest GitHub releases\ngit log \"$(git describe --tags --abbrev=0)..HEAD\" --oneline   # commits since last tag\n```\n\nPropose a semver bump from the commits and confirm with the user (or use the\nversion the user already named):\n\n- **patch** (0.x.**Y**) — bug fixes, doc updates, dependency bumps, internal\n  refactors, diagnostics.\n- **minor** (0.**X**.0) — new subcommands or flags, new capabilities, changed\n  default behavior that is additive.\n- **major** (**X**.0.0) — breaking changes (not applicable pre-1.0).\n\nIf there are no commits since the last tag, there is nothing to release — say so.\n\n## Step 3: Docs sweep\n\nRelease changes ripple into docs. Sweep each before bumping the version, and\ncommit doc changes as their own focused commit(s) ahead of the version bump.\n\n### README — `README.md`\n\n- Quickstart commands, flags, and example output still accurate.\n- The feature\u002Fcommand list reflects reality (new commands, new behavior).\n- The \"Repository Layout\" and install sections are current.\n- Any version strings.\n\n### Site guide — `site\u002Fguide\u002F*.md`\n\n- `cli.md` — new\u002Fchanged subcommands, flags, default behavior, output examples,\n  new error conditions. This is the command reference; keep it exhaustive.\n- `quickstart.md`, `concepts.md`, `design.md` (locked-decision list).\n- Validate the build before committing:\n  ```bash\n  cd site && npm run build   # vitepress build; output is the gitignored dist\u002F\n  ```\n\n### Bundled CLI skill — `skills\u002Fgnit\u002FSKILL.md`\n\nThis is the **shipped** agent skill: it is embedded into the `gnit` binary via\n`include_str!(\"..\u002Fskills\u002Fgnit\u002FSKILL.md\")` in `src\u002Fskills.rs` and is what\n`gnit skills install` puts into agent harnesses. Any user-visible CLI change must\nbe reflected here, or every agent using the installed skill gives stale guidance.\n\n(This `gnit-release` skill is **not** shipped — `gnit skills install` is hardcoded\nto `skills\u002Fgnit\u002F` only, so the maintainer skills under `skills\u002F` never reach end\nusers.)\n\n### Decisions and examples\n\n- `docs\u002Fdecisions\u002F` — if a decision changed user-visible behavior, make sure the\n  README and guide reflect it.\n- Keep example identifiers and output snippets consistent with current formats\n  (e.g. Change\u002FPin ids).\n\nGrep for stale version strings:\n\n```bash\ngrep -rn \"0\\.[0-9][0-9]*\\.[0-9]\" README.md site\u002F skills\u002F --include='*.md'\n```\n\n## Step 4: Bump the version\n\nEdit the version in both files — in `Cargo.lock`, change only the `name = \"gnit\"`\npackage's `version`:\n\n- `Cargo.toml` → `version = \"X.Y.Z\"` under `[package]`.\n- `Cargo.lock` → the `version` line directly under `name = \"gnit\"`.\n\nVerify the bump is internally consistent and reported correctly:\n\n```bash\ncargo build --locked            # fails if Cargo.lock drifted from Cargo.toml\n.\u002Ftarget\u002Fdebug\u002Fgnit --version    # should print: gnit X.Y.Z\n```\n\n## Step 5: Commit and push master first\n\nStage explicitly — do not use `git add -A`:\n\n```bash\ngit add Cargo.toml Cargo.lock\ngit commit -m \"Bump version to X.Y.Z\"\ngit push origin master\n```\n\nMatch the existing history: the version bump is its own commit (message exactly\n`Bump version to X.Y.Z`), and the release tag points at it. Push `master` before\ntagging so the release build checks out a commit that exists on the remote\ndefault branch.\n\nDo **not** add a signature or `Co-Authored-By` trailer to the commit (repo\nconvention).\n\nIf the push is rejected because the remote moved, rebase and re-push before any\ntag work:\n\n```bash\ngit pull --rebase origin master\ngit push origin master\n```\n\n## Step 6: Tag and push the release\n\nGnit tags are **lightweight** and sit on the bump commit (match `v0.8.0`,\n`v0.8.1`):\n\n```bash\ngit tag vX.Y.Z\ngit push origin vX.Y.Z\n```\n\nPushing the tag triggers `release.yml`. The build job compiles three targets —\n`linux-x86_64`, `darwin-x86_64`, `darwin-aarch64` — packages each as\n`gnit-X.Y.Z-\u003Cos>-\u003Carch>.tar.gz`, and the release job creates the GitHub release\nwith those tarballs plus `checksums.txt`. GitHub marks the newest release Latest\nautomatically.\n\n## Step 7: Verify\n\n```bash\ngh run list --limit 6\ngh run watch \u003Crelease-run-id> --exit-status   # watch the Release run to green\n```\n\nThen confirm the published release:\n\n```bash\ngh release view vX.Y.Z --json tagName,isDraft,isPrerelease,assets \\\n  --jq '{tag: .tagName, draft: .isDraft, prerelease: .isPrerelease, assets: [.assets[].name]}'\ngh release list --limit 3   # vX.Y.Z should be Latest\n```\n\nExpect: not draft, not prerelease, marked Latest, and four assets —\n`checksums.txt`, `gnit-X.Y.Z-darwin-aarch64.tar.gz`,\n`gnit-X.Y.Z-darwin-x86_64.tar.gz`, `gnit-X.Y.Z-linux-x86_64.tar.gz`.\n\nAlso confirm CI went green on both the master push and the tag, and watch the\n`Deploy Site` run to success if the release touched `site\u002F`:\n\n```bash\ngh run list --limit 8\ngh run watch \u003Cdeploy-site-run-id> --exit-status\n```\n\nReport the result to the user with links:\n\n- Release: `https:\u002F\u002Fgithub.com\u002Fmostlydev\u002Fgnit\u002Freleases\u002Ftag\u002FvX.Y.Z`\n- Site: `https:\u002F\u002Fmostlydev.github.io\u002Fgnit\u002F`\n\n### Optional: enrich the release notes\n\nThe workflow publishes bare notes (`Gnit vX.Y.Z`). For a notable release, replace\nthem with synthesized highlights grouped by theme — not a raw commit list:\n\n```bash\ngh release edit vX.Y.Z --notes \"$(cat \u003C\u003C'EOF'\n## Highlights\n\n- **Feature** — what changed and why it matters.\n\n## Fixes\n\n- Fix: brief description.\nEOF\n)\"\n```\n\n## Edge cases\n\n- **No commits since the last tag** — nothing to release; tell the user.\n- **Dirty working tree** — warn before starting; don't mix unrelated changes\n  into the bump commit.\n- **Local clippy passes, CI clippy fails** — CI uses current stable with\n  `-D warnings`. `rustup update stable && cargo clippy --all-targets -- -D warnings`\n  before tagging.\n- **`cargo build --locked` fails after the bump** — the `Cargo.lock` gnit entry\n  was not bumped; update it to match `Cargo.toml`.\n- **Push rejected (remote ahead)** — `git pull --rebase origin master`, then\n  re-push master before tagging.\n- **Tag points at the wrong commit (e.g. after a rebase)** — delete and re-push\n  the tag; if the workflow already created a partial release, delete it first:\n  ```bash\n  gh release delete vX.Y.Z --yes\n  git push origin :refs\u002Ftags\u002FvX.Y.Z\n  git tag -d vX.Y.Z && git tag vX.Y.Z && git push origin vX.Y.Z\n  ```\n- **Release came out as draft\u002Fnot-latest** — the workflow publishes a normal\n  public release and GitHub auto-marks the newest as Latest. If you ever create\n  one by hand, pass `--latest`.\n","# Gnit release\n\nThis skill cuts a release of the `gnit` CLI. The pipeline is **tag-driven**:\npushing a `v*` tag triggers `.github\u002Fworkflows\u002Frelease.yml`, which builds the\nbinaries for every target and publishes the GitHub release. Two other workflows\nreact to the same push to `master`: `ci.yml` (fmt + clippy + tests on Ubuntu and\nmacOS) and `deploy-site.yml` (redeploys the VitePress site).\n\nGnit is a single Rust binary with no submodules, no Docker images, and no runtime\ninfra pins — so a release is just: get `master` green and version-bumped, push\nit, then push the tag. The release workflow does the building and publishing.\n\nYour job is to prepare everything locally, push the version-bump commit to\n`master`, then push the release tag and verify the workflows go green.\n\n## Step 1: Pre-release sanity checks\n\n```bash\n# Clean working tree — don't fold unrelated work into a release.\ngit status --short\n\n# Local tags lag the remote badly; sync before you reason about versions.\ngit fetch --tags\n\n# Releases publish via gh in the workflow, but check your own auth for the\n# manual steps (release notes, verification).\ngh auth status\n\n# Run the exact gate CI runs on the tag. If this fails locally, the release\n# build fails too.\ncargo fmt --check\ncargo clippy --all-targets -- -D warnings\ncargo test --locked\n```\n\nIf the working tree is dirty, decide with the user whether those changes belong\nin this release or should be committed\u002Fstashed separately.\n\nCI runs clippy with the **current stable** toolchain and `-D warnings`. If your\nlocal toolchain lags, a lint that is clean locally can fail CI on the tag. Run\n`rustup update stable && cargo clippy --all-targets -- -D warnings` before\ntagging to catch newer lints in one pass.\n\n## Step 2: Determine the version\n\n```bash\ngit tag --sort=-v:refname | head -3      # latest tags\ngh release list --limit 5                # latest GitHub releases\ngit log \"$(git describe --tags --abbrev=0)..HEAD\" --oneline   # commits since last tag\n```\n\nPropose a semver bump from the commits and confirm with the user (or use the\nversion the user already named):\n\n- **patch** (0.x.**Y**) — bug fixes, doc updates, dependency bumps, internal\n  refactors, diagnostics.\n- **minor** (0.**X**.0) — new subcommands or flags, new capabilities, changed\n  default behavior that is additive.\n- **major** (**X**.0.0) — breaking changes (not applicable pre-1.0).\n\nIf there are no commits since the last tag, there is nothing to release — say so.\n\n## Step 3: Docs sweep\n\nRelease changes ripple into docs. Sweep each before bumping the version, and\ncommit doc changes as their own focused commit(s) ahead of the version bump.\n\n### README — `README.md`\n\n- Quickstart commands, flags, and example output still accurate.\n- The feature\u002Fcommand list reflects reality (new commands, new behavior).\n- The \"Repository Layout\" and install sections are current.\n- Any version strings.\n\n### Site guide — `site\u002Fguide\u002F*.md`\n\n- `cli.md` — new\u002Fchanged subcommands, flags, default behavior, output examples,\n  new error conditions. This is the command reference; keep it exhaustive.\n- `quickstart.md`, `concepts.md`, `design.md` (locked-decision list).\n- Validate the build before committing:\n  ```bash\n  cd site && npm run build   # vitepress build; output is the gitignored dist\u002F\n  ```\n\n### Bundled CLI skill — `skills\u002Fgnit\u002FSKILL.md`\n\nThis is the **shipped** agent skill: it is embedded into the `gnit` binary via\n`include_str!(\"..\u002Fskills\u002Fgnit\u002FSKILL.md\")` in `src\u002Fskills.rs` and is what\n`gnit skills install` puts into agent harnesses. Any user-visible CLI change must\nbe reflected here, or every agent using the installed skill gives stale guidance.\n\n(This `gnit-release` skill is **not** shipped — `gnit skills install` is hardcoded\nto `skills\u002Fgnit\u002F` only, so the maintainer skills under `skills\u002F` never reach end\nusers.)\n\n### Decisions and examples\n\n- `docs\u002Fdecisions\u002F` — if a decision changed user-visible behavior, make sure the\n  README and guide reflect it.\n- Keep example identifiers and output snippets consistent with current formats\n  (e.g. Change\u002FPin ids).\n\nGrep for stale version strings:\n\n```bash\ngrep -rn \"0\\.[0-9][0-9]*\\.[0-9]\" README.md site\u002F skills\u002F --include='*.md'\n```\n\n## Step 4: Bump the version\n\nEdit the version in both files — in `Cargo.lock`, change only the `name = \"gnit\"`\npackage's `version`:\n\n- `Cargo.toml` → `version = \"X.Y.Z\"` under `[package]`.\n- `Cargo.lock` → the `version` line directly under `name = \"gnit\"`.\n\nVerify the bump is internally consistent and reported correctly:\n\n```bash\ncargo build --locked            # fails if Cargo.lock drifted from Cargo.toml\n.\u002Ftarget\u002Fdebug\u002Fgnit --version    # should print: gnit X.Y.Z\n```\n\n## Step 5: Commit and push master first\n\nStage explicitly — do not use `git add -A`:\n\n```bash\ngit add Cargo.toml Cargo.lock\ngit commit -m \"Bump version to X.Y.Z\"\ngit push origin master\n```\n\nMatch the existing history: the version bump is its own commit (message exactly\n`Bump version to X.Y.Z`), and the release tag points at it. Push `master` before\ntagging so the release build checks out a commit that exists on the remote\ndefault branch.\n\nDo **not** add a signature or `Co-Authored-By` trailer to the commit (repo\nconvention).\n\nIf the push is rejected because the remote moved, rebase and re-push before any\ntag work:\n\n```bash\ngit pull --rebase origin master\ngit push origin master\n```\n\n## Step 6: Tag and push the release\n\nGnit tags are **lightweight** and sit on the bump commit (match `v0.8.0`,\n`v0.8.1`):\n\n```bash\ngit tag vX.Y.Z\ngit push origin vX.Y.Z\n```\n\nPushing the tag triggers `release.yml`. The build job compiles three targets —\n`linux-x86_64`, `darwin-x86_64`, `darwin-aarch64` — packages each as\n`gnit-X.Y.Z-\u003Cos>-\u003Carch>.tar.gz`, and the release job creates the GitHub release\nwith those tarballs plus `checksums.txt`. GitHub marks the newest release Latest\nautomatically.\n\n## Step 7: Verify\n\n```bash\ngh run list --limit 6\ngh run watch \u003Crelease-run-id> --exit-status   # watch the Release run to green\n```\n\nThen confirm the published release:\n\n```bash\ngh release view vX.Y.Z --json tagName,isDraft,isPrerelease,assets \\\n  --jq '{tag: .tagName, draft: .isDraft, prerelease: .isPrerelease, assets: [.assets[].name]}'\ngh release list --limit 3   # vX.Y.Z should be Latest\n```\n\nExpect: not draft, not prerelease, marked Latest, and four assets —\n`checksums.txt`, `gnit-X.Y.Z-darwin-aarch64.tar.gz`,\n`gnit-X.Y.Z-darwin-x86_64.tar.gz`, `gnit-X.Y.Z-linux-x86_64.tar.gz`.\n\nAlso confirm CI went green on both the master push and the tag, and watch the\n`Deploy Site` run to success if the release touched `site\u002F`:\n\n```bash\ngh run list --limit 8\ngh run watch \u003Cdeploy-site-run-id> --exit-status\n```\n\nReport the result to the user with links:\n\n- Release: `https:\u002F\u002Fgithub.com\u002Fmostlydev\u002Fgnit\u002Freleases\u002Ftag\u002FvX.Y.Z`\n- Site: `https:\u002F\u002Fmostlydev.github.io\u002Fgnit\u002F`\n\n### Optional: enrich the release notes\n\nThe workflow publishes bare notes (`Gnit vX.Y.Z`). For a notable release, replace\nthem with synthesized highlights grouped by theme — not a raw commit list:\n\n```bash\ngh release edit vX.Y.Z --notes \"$(cat \u003C\u003C'EOF'\n## Highlights\n\n- **Feature** — what changed and why it matters.\n\n## Fixes\n\n- Fix: brief description.\nEOF\n)\"\n```\n\n## Edge cases\n\n- **No commits since the last tag** — nothing to release; tell the user.\n- **Dirty working tree** — warn before starting; don't mix unrelated changes\n  into the bump commit.\n- **Local clippy passes, CI clippy fails** — CI uses current stable with\n  `-D warnings`. `rustup update stable && cargo clippy --all-targets -- -D warnings`\n  before tagging.\n- **`cargo build --locked` fails after the bump** — the `Cargo.lock` gnit entry\n  was not bumped; update it to match `Cargo.toml`.\n- **Push rejected (remote ahead)** — `git pull --rebase origin master`, then\n  re-push master before tagging.\n- **Tag points at the wrong commit (e.g. after a rebase)** — delete and re-push\n  the tag; if the workflow already created a partial release, delete it first:\n  ```bash\n  gh release delete vX.Y.Z --yes\n  git push origin :refs\u002Ftags\u002FvX.Y.Z\n  git tag -d vX.Y.Z && git tag vX.Y.Z && git push origin vX.Y.Z\n  ```\n- **Release came out as draft\u002Fnot-latest** — the workflow publishes a normal\n  public release and GitHub auto-marks the newest as Latest. If you ever create\n  one by hand, pass `--latest`.\n",{"name":5,"description":7},"master","14a8c89c0a7fb6b17c944f9c6e2926ef480e8a64","skills\u002Fgnit-release","https:\u002F\u002Fgithub.com\u002Fmostlydev\u002Fgnit","https:\u002F\u002Fgithub.com\u002Fmostlydev","Husband, father, runner, biker, full stack dev.","2026-07-30 04:45:41",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add mostlydev\u002Fgnit --skill gnit-release",{"tool":37,"command":38},"bunx","bunx skills add mostlydev\u002Fgnit --skill gnit-release",{"tool":40,"command":41},"pnpm","pnpm dlx skills add mostlydev\u002Fgnit --skill gnit-release","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmostlydev\u002Fgnit\u002Fblob\u002Fmaster\u002Fskills\u002Fgnit-release\u002FSKILL.md",true,[],[46,53,58,63],{"skillNo":47,"name":48,"nameZh":6,"description":49,"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},"01M75882QC4P5Q498T2W2NR99V","gnit","Use when working in a Gnit workspace (a `.gnit\u002F` directory or `.gnit\u002Froster.yaml` is present), or when a single change spans several independent Git repositories. Teaches the Change \u002F Pin \u002F branch-aware-checkout \u002F ordered-push workflow through the `gnit` CLI instead of hand-managing submodules or raw Git across repos.","https:\u002F\u002Fgithub.com\u002Fmostlydev\u002Fgnit\u002Fblob\u002Fmaster\u002Fskills\u002Fgnit\u002FSKILL.md",[],[],{"skillNo":54,"name":5,"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":55,"categories":56,"keywords":57,"publishedAt":19},"01M7587W308EAC20TWAB3EAE9J","https:\u002F\u002Fgithub.com\u002Fmostlydev\u002Fgnit\u002Fblob\u002Fmaster\u002F.grok\u002Fskills\u002Fgnit-release\u002FSKILL.md",[],[],{"skillNo":59,"name":5,"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":60,"categories":61,"keywords":62,"publishedAt":19},"01M7587TT6M6VEQSGG86EQEFVX","https:\u002F\u002Fgithub.com\u002Fmostlydev\u002Fgnit\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fgnit-release\u002FSKILL.md",[],[],{"skillNo":64,"name":5,"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":65,"categories":66,"keywords":67,"publishedAt":19},"01M7587SX41MSM0N7098BS3YCX","https:\u002F\u002Fgithub.com\u002Fmostlydev\u002Fgnit\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fgnit-release\u002FSKILL.md",[],[]]