[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FES8S3CKDB3R79XFH88PYR":3,"skill-same:01M7FES8S3CKDB3R79XFH88PYR":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},"01M7FES8S3CKDB3R79XFH88PYR","address-pr-comments",null,"Address a GitHub pull request's review comments and failing checks with the gh CLI. Fixes broken checks at the source; for every comment either fixes it (commit, push, reply citing the commit) or rebuts it in its own thread, then resolves the conversation. Use when asked to address, handle, answer or resolve PR comments, review feedback or failing PR checks.","heynemann\u002Fdotfiles-stow","heynemann","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F60965?v=4","01M7DFBD9ZDB2J2QE7R4AR0PES","Bernardo Heynemann","01M7FERV0J6GMQ0RHEH6EHGYRW",0,"MIT","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fskills-sh\u002F.agents\u002Fskills\u002Faddress-pr-comments\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: address-pr-comments\ndescription: Address a GitHub pull request's review comments and failing checks with the gh CLI. Fixes broken checks at the source; for every comment either fixes it (commit, push, reply citing the commit) or rebuts it in its own thread, then resolves the conversation. Use when asked to address, handle, answer or resolve PR comments, review feedback or failing PR checks.\n---\n\n# Address PR comments\n\nWork through one pull request until every check is green and every comment is\nanswered and resolved. Run autonomously: triage, fix, push, reply and resolve\nwithout pausing for approval.\n\n## Rules\n\n- **Reply where the comment lives.** A review thread gets a reply in that\n  thread. A top-level comment or review summary gets its own quote-reply. Each\n  comment gets its own reply; the PR body and any all-in-one summary comment\n  stay untouched.\n- **Every comment ends answered and closed:** threads resolved, top-level\n  comments and review summaries minimized as `RESOLVED`.\n- **Fix the source.** A red check turns green because the code, test or config\n  is now correct. Skipping or deleting tests, `--no-verify`, `continue-on-error`,\n  loosened lint rules, lowered thresholds and blindly regenerated snapshots are\n  not fixes.\n- **Push fast-forward only** to the PR's head branch. Never force-push.\n- **Replies are short and specific:** what changed, or why not, with evidence.\n  No filler, no thanks-for-the-catch.\n- Prefer `gh` subcommands; use `gh api` \u002F `gh api graphql` where `gh` has no\n  subcommand (threads, replies, resolve, minimize). Write reply bodies to a\n  file and pass them with `-F body=@file` so Markdown survives the shell.\n\n## 1. Find the PR\n\nWith a PR number or URL from the user, use it. Otherwise ask `gh` for the PR of\nthe current branch:\n\n```bash\ngh pr view [\u003Cnumber>] --json number,url,state,headRefName,headRefOid,isCrossRepository,maintainerCanModify\n```\n\n`no pull requests found for branch` means there is none: ask the user for the\nPR number. Owner and repo come from the URL\n(`https:\u002F\u002Fgithub.com\u002F\u003Cowner>\u002F\u003Crepo>\u002Fpull\u002F\u003Cnumber>`); comments live on that\nrepository even when the head branch is in a fork. A PR that is not `OPEN`,\nor a fork PR with `maintainerCanModify: false` that you did not author, cannot\ntake pushes: stop and tell the user.\n\nDone when number, owner and repo are known and the PR accepts pushes.\n\n## 2. Check out the head\n\n`git status --porcelain` must be empty; uncommitted changes belong to the user,\nso stop and ask if it is not. Then:\n\n```bash\ngh pr checkout \u003Cnumber>\ngit pull --ff-only\n```\n\nDone when `git rev-parse HEAD` equals `headRefOid`.\n\n## 3. Build the inventory\n\nWho you are: `gh api user --jq .login` (the *viewer*).\n\n**Checks.** `gh pr checks \u003Cnumber> --json name,state,bucket,link,workflow`.\nThe command exits non-zero while checks fail (1) or are pending (8); read the\nJSON regardless. Every `bucket: \"fail\"` goes in the inventory. Pending checks\nare caught by step 8. `no checks reported on the '\u003Cbranch>' branch` (no JSON)\nmeans the repository runs no checks on this PR.\n\n**Review threads.** Unresolved threads, skipping threads where every comment is\nthe viewer's:\n\n```bash\ngh api graphql --paginate -F owner=\u003Cowner> -F repo=\u003Crepo> -F number=\u003Cnumber> -f query='\nquery($owner: String!, $repo: String!, $number: Int!, $endCursor: String) {\n  repository(owner: $owner, name: $repo) {\n    pullRequest(number: $number) {\n      reviewThreads(first: 50, after: $endCursor) {\n        pageInfo { hasNextPage endCursor }\n        nodes {\n          id isResolved isOutdated viewerCanReply viewerCanResolve path line\n          comments(first: 50) { nodes { author { login } body url } }\n        }\n      }\n    }\n  }\n}' --jq '.data.repository.pullRequest.reviewThreads.nodes[] | select(.isResolved | not)'\n```\n\n**Top-level comments and review summaries.** Not minimized, not the viewer's,\nnon-empty body:\n\n```bash\ngh api graphql -F owner=\u003Cowner> -F repo=\u003Crepo> -F number=\u003Cnumber> -f query='\nquery($owner: String!, $repo: String!, $number: Int!) {\n  repository(owner: $owner, name: $repo) {\n    pullRequest(number: $number) {\n      comments(first: 100) { nodes { id author { login } body url isMinimized } }\n      reviews(first: 100) { nodes { id author { login } state body url isMinimized } }\n    }\n  }\n}'\n```\n\nIf a PR has more than 100 of either, page that connection with `after:`.\n\nRead each thread in full: the ask is the latest unanswered request in it.\nComments that ask for nothing (approvals, praise, bot status reports, review\noverviews) need no reply; record them as *informational*.\n\nDone when every failing check and every comment has an inventory entry: id,\nkind (check, thread, top-level, review), author, location and the ask.\n\n## 4. Fix failing checks\n\nFor each failing check, get the failure from its `link`:\n\n- `...\u002Factions\u002Fruns\u002F\u003Crun>\u002Fjob\u002F\u003Cjob>`:\n  `gh run view --job \u003Cjob> --log-failed`.\n- `...\u002Fruns\u002F\u003Ccheck-run-id>` (a non-Actions app):\n  `gh api repos\u002F\u003Cowner>\u002F\u003Crepo>\u002Fcheck-runs\u002F\u003Ccheck-run-id> --jq .output`.\n\nFind the command the check runs (`.github\u002Fworkflows\u002F`, Makefile, package\nscripts), reproduce the failure locally, fix the cause and rerun the command\nuntil it passes. A failure whose cause lies outside the repository (runner\noutage, expired secret, flaky network) gets one `gh run rerun \u003Crun> --failed`;\nif it fails again, record it for the report. Commit each check's fix\nseparately.\n\nDone when every failing check either passes locally or is recorded as external.\n\n## 5. Triage each comment: fix or rebut\n\nRead the code the comment points at, at the current head (threads marked\n`isOutdated` may already be fixed: then the outcome is *fix*, citing the commit\nthat fixed it).\n\n- **Fix** when the comment is right: a bug, a missing case, a clearer name, a\n  repo convention, a cheap and correct nit. A ```` ```suggestion ```` block is\n  applied as written unless it is wrong.\n- **Rebut** when it is wrong or does not belong in this PR: the code already\n  handles it, it contradicts the repo's conventions or another reviewer, it is\n  out of scope (name the follow-up), or the trade-off was deliberate. Questions\n  get answered on this path too. Every rebuttal carries evidence: a permalink to\n  the line, a test, a doc or a measurement.\n\nDone when every non-informational comment is marked fix or rebut with a\none-line reason.\n\n## 6. Fix and push\n\nOne commit per comment fixed; comments asking for the same change share a\ncommit. For each: make the change, run the tests and linters that cover it,\nthen commit with a message in the repository's style (`git log --oneline -20`)\nthat says what changed, not \"address review\".\n\n```bash\ngit push\n```\n\nA rejected push means the branch moved: `git pull --rebase`, rerun the tests,\npush again. Rebasing rewrites SHAs, so read the final ones after the push\nsucceeds: `git log --format='%H %s' -n \u003Ccommits you made>`.\n\nDone when the push succeeded and every fixed comment maps to a pushed full SHA.\n\n## 7. Reply and resolve\n\nWrite each reply to a file, then post it.\n\n- **Fix:** `Fixed in \u003Cfull SHA>: \u003Cwhat changed>.` GitHub links the SHA.\n- **Rebut:** the position and its evidence, in one to four sentences.\n\n**Review thread:** reply in the thread, then resolve it.\n\n```bash\ngh api graphql -f threadId=\u003Cthread id> -F body=@reply.md -f query='\nmutation($threadId: ID!, $body: String!) {\n  addPullRequestReviewThreadReply(input: {pullRequestReviewThreadId: $threadId, body: $body}) {\n    comment { url }\n  }\n}'\ngh api graphql -f threadId=\u003Cthread id> -f query='\nmutation($threadId: ID!) {\n  resolveReviewThread(input: {threadId: $threadId}) { thread { isResolved } }\n}'\n```\n\n**Top-level comment or review summary:** post a quote-reply that starts with\nthe quoted ask, the author's handle and a link to the original, then minimize\nthe original as resolved.\n\n```markdown\n> \u003Cthe sentence being answered>\n\n@\u003Cauthor> ([comment](\u003Coriginal url>)): \u003Creply>\n```\n\n```bash\ngh pr comment \u003Cnumber> --body-file reply.md\ngh api graphql -f id=\u003Ccomment or review node id> -f query='\nmutation($id: ID!) {\n  minimizeComment(input: {subjectId: $id, classifier: RESOLVED}) {\n    minimizedComment { isMinimized }\n  }\n}'\n```\n\nA permission error on resolve or minimize (`viewerCanResolve: false`, or no\ntriage access) leaves the reply in place; record it for the report.\n\nDone when rerunning step 3's queries returns no unresolved thread and no\nunminimized comment other than informational ones and recorded permission\nfailures.\n\n## 8. Watch checks\n\n```bash\ngh pr checks \u003Cnumber> --watch --fail-fast\n```\n\nWith no checks reported in step 3, there is nothing to watch: skip this step.\nOtherwise, right after a push the new head may report no checks yet; wait ten\nseconds and retry. On a failure, run step 4 for it, push, and watch again. Stop\nafter three rounds of fixes.\n\nDone when every check passes, or three rounds are spent.\n\n## 9. Report\n\nTell the user, in chat, not on the PR:\n\n- each comment: author, location, outcome (fixed in `\u003Cshort SHA>`, or rebutted\n  with the one-line reason);\n- each check: final state, and the fix commit if it was red;\n- anything left open: external check failures, permission failures, checks\n  still red after three rounds, and informational comments that got no reply.\n","# Address PR comments\n\nWork through one pull request until every check is green and every comment is\nanswered and resolved. Run autonomously: triage, fix, push, reply and resolve\nwithout pausing for approval.\n\n## Rules\n\n- **Reply where the comment lives.** A review thread gets a reply in that\n  thread. A top-level comment or review summary gets its own quote-reply. Each\n  comment gets its own reply; the PR body and any all-in-one summary comment\n  stay untouched.\n- **Every comment ends answered and closed:** threads resolved, top-level\n  comments and review summaries minimized as `RESOLVED`.\n- **Fix the source.** A red check turns green because the code, test or config\n  is now correct. Skipping or deleting tests, `--no-verify`, `continue-on-error`,\n  loosened lint rules, lowered thresholds and blindly regenerated snapshots are\n  not fixes.\n- **Push fast-forward only** to the PR's head branch. Never force-push.\n- **Replies are short and specific:** what changed, or why not, with evidence.\n  No filler, no thanks-for-the-catch.\n- Prefer `gh` subcommands; use `gh api` \u002F `gh api graphql` where `gh` has no\n  subcommand (threads, replies, resolve, minimize). Write reply bodies to a\n  file and pass them with `-F body=@file` so Markdown survives the shell.\n\n## 1. Find the PR\n\nWith a PR number or URL from the user, use it. Otherwise ask `gh` for the PR of\nthe current branch:\n\n```bash\ngh pr view [\u003Cnumber>] --json number,url,state,headRefName,headRefOid,isCrossRepository,maintainerCanModify\n```\n\n`no pull requests found for branch` means there is none: ask the user for the\nPR number. Owner and repo come from the URL\n(`https:\u002F\u002Fgithub.com\u002F\u003Cowner>\u002F\u003Crepo>\u002Fpull\u002F\u003Cnumber>`); comments live on that\nrepository even when the head branch is in a fork. A PR that is not `OPEN`,\nor a fork PR with `maintainerCanModify: false` that you did not author, cannot\ntake pushes: stop and tell the user.\n\nDone when number, owner and repo are known and the PR accepts pushes.\n\n## 2. Check out the head\n\n`git status --porcelain` must be empty; uncommitted changes belong to the user,\nso stop and ask if it is not. Then:\n\n```bash\ngh pr checkout \u003Cnumber>\ngit pull --ff-only\n```\n\nDone when `git rev-parse HEAD` equals `headRefOid`.\n\n## 3. Build the inventory\n\nWho you are: `gh api user --jq .login` (the *viewer*).\n\n**Checks.** `gh pr checks \u003Cnumber> --json name,state,bucket,link,workflow`.\nThe command exits non-zero while checks fail (1) or are pending (8); read the\nJSON regardless. Every `bucket: \"fail\"` goes in the inventory. Pending checks\nare caught by step 8. `no checks reported on the '\u003Cbranch>' branch` (no JSON)\nmeans the repository runs no checks on this PR.\n\n**Review threads.** Unresolved threads, skipping threads where every comment is\nthe viewer's:\n\n```bash\ngh api graphql --paginate -F owner=\u003Cowner> -F repo=\u003Crepo> -F number=\u003Cnumber> -f query='\nquery($owner: String!, $repo: String!, $number: Int!, $endCursor: String) {\n  repository(owner: $owner, name: $repo) {\n    pullRequest(number: $number) {\n      reviewThreads(first: 50, after: $endCursor) {\n        pageInfo { hasNextPage endCursor }\n        nodes {\n          id isResolved isOutdated viewerCanReply viewerCanResolve path line\n          comments(first: 50) { nodes { author { login } body url } }\n        }\n      }\n    }\n  }\n}' --jq '.data.repository.pullRequest.reviewThreads.nodes[] | select(.isResolved | not)'\n```\n\n**Top-level comments and review summaries.** Not minimized, not the viewer's,\nnon-empty body:\n\n```bash\ngh api graphql -F owner=\u003Cowner> -F repo=\u003Crepo> -F number=\u003Cnumber> -f query='\nquery($owner: String!, $repo: String!, $number: Int!) {\n  repository(owner: $owner, name: $repo) {\n    pullRequest(number: $number) {\n      comments(first: 100) { nodes { id author { login } body url isMinimized } }\n      reviews(first: 100) { nodes { id author { login } state body url isMinimized } }\n    }\n  }\n}'\n```\n\nIf a PR has more than 100 of either, page that connection with `after:`.\n\nRead each thread in full: the ask is the latest unanswered request in it.\nComments that ask for nothing (approvals, praise, bot status reports, review\noverviews) need no reply; record them as *informational*.\n\nDone when every failing check and every comment has an inventory entry: id,\nkind (check, thread, top-level, review), author, location and the ask.\n\n## 4. Fix failing checks\n\nFor each failing check, get the failure from its `link`:\n\n- `...\u002Factions\u002Fruns\u002F\u003Crun>\u002Fjob\u002F\u003Cjob>`:\n  `gh run view --job \u003Cjob> --log-failed`.\n- `...\u002Fruns\u002F\u003Ccheck-run-id>` (a non-Actions app):\n  `gh api repos\u002F\u003Cowner>\u002F\u003Crepo>\u002Fcheck-runs\u002F\u003Ccheck-run-id> --jq .output`.\n\nFind the command the check runs (`.github\u002Fworkflows\u002F`, Makefile, package\nscripts), reproduce the failure locally, fix the cause and rerun the command\nuntil it passes. A failure whose cause lies outside the repository (runner\noutage, expired secret, flaky network) gets one `gh run rerun \u003Crun> --failed`;\nif it fails again, record it for the report. Commit each check's fix\nseparately.\n\nDone when every failing check either passes locally or is recorded as external.\n\n## 5. Triage each comment: fix or rebut\n\nRead the code the comment points at, at the current head (threads marked\n`isOutdated` may already be fixed: then the outcome is *fix*, citing the commit\nthat fixed it).\n\n- **Fix** when the comment is right: a bug, a missing case, a clearer name, a\n  repo convention, a cheap and correct nit. A ```` ```suggestion ```` block is\n  applied as written unless it is wrong.\n- **Rebut** when it is wrong or does not belong in this PR: the code already\n  handles it, it contradicts the repo's conventions or another reviewer, it is\n  out of scope (name the follow-up), or the trade-off was deliberate. Questions\n  get answered on this path too. Every rebuttal carries evidence: a permalink to\n  the line, a test, a doc or a measurement.\n\nDone when every non-informational comment is marked fix or rebut with a\none-line reason.\n\n## 6. Fix and push\n\nOne commit per comment fixed; comments asking for the same change share a\ncommit. For each: make the change, run the tests and linters that cover it,\nthen commit with a message in the repository's style (`git log --oneline -20`)\nthat says what changed, not \"address review\".\n\n```bash\ngit push\n```\n\nA rejected push means the branch moved: `git pull --rebase`, rerun the tests,\npush again. Rebasing rewrites SHAs, so read the final ones after the push\nsucceeds: `git log --format='%H %s' -n \u003Ccommits you made>`.\n\nDone when the push succeeded and every fixed comment maps to a pushed full SHA.\n\n## 7. Reply and resolve\n\nWrite each reply to a file, then post it.\n\n- **Fix:** `Fixed in \u003Cfull SHA>: \u003Cwhat changed>.` GitHub links the SHA.\n- **Rebut:** the position and its evidence, in one to four sentences.\n\n**Review thread:** reply in the thread, then resolve it.\n\n```bash\ngh api graphql -f threadId=\u003Cthread id> -F body=@reply.md -f query='\nmutation($threadId: ID!, $body: String!) {\n  addPullRequestReviewThreadReply(input: {pullRequestReviewThreadId: $threadId, body: $body}) {\n    comment { url }\n  }\n}'\ngh api graphql -f threadId=\u003Cthread id> -f query='\nmutation($threadId: ID!) {\n  resolveReviewThread(input: {threadId: $threadId}) { thread { isResolved } }\n}'\n```\n\n**Top-level comment or review summary:** post a quote-reply that starts with\nthe quoted ask, the author's handle and a link to the original, then minimize\nthe original as resolved.\n\n```markdown\n> \u003Cthe sentence being answered>\n\n@\u003Cauthor> ([comment](\u003Coriginal url>)): \u003Creply>\n```\n\n```bash\ngh pr comment \u003Cnumber> --body-file reply.md\ngh api graphql -f id=\u003Ccomment or review node id> -f query='\nmutation($id: ID!) {\n  minimizeComment(input: {subjectId: $id, classifier: RESOLVED}) {\n    minimizedComment { isMinimized }\n  }\n}'\n```\n\nA permission error on resolve or minimize (`viewerCanResolve: false`, or no\ntriage access) leaves the reply in place; record it for the report.\n\nDone when rerunning step 3's queries returns no unresolved thread and no\nunminimized comment other than informational ones and recorded permission\nfailures.\n\n## 8. Watch checks\n\n```bash\ngh pr checks \u003Cnumber> --watch --fail-fast\n```\n\nWith no checks reported in step 3, there is nothing to watch: skip this step.\nOtherwise, right after a push the new head may report no checks yet; wait ten\nseconds and retry. On a failure, run step 4 for it, push, and watch again. Stop\nafter three rounds of fixes.\n\nDone when every check passes, or three rounds are spent.\n\n## 9. Report\n\nTell the user, in chat, not on the PR:\n\n- each comment: author, location, outcome (fixed in `\u003Cshort SHA>`, or rebutted\n  with the one-line reason);\n- each check: final state, and the fix commit if it was red;\n- anything left open: external check failures, permission failures, checks\n  still red after three rounds, and informational comments that got no reply.\n",{"name":5,"description":7},"main","e4d0a0940fd53fc8a3a1e1dcb967c0a18ea8ba0f","omp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fskills-sh\u002F.agents\u002Fskills\u002Faddress-pr-comments","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow","https:\u002F\u002Fgithub.com\u002Fheynemann","http:\u002F\u002Fwww.thumbor.org","CTO @ Flutter Brazil | Former Meta & Coinbase","2026-10-29 20:46:15",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add heynemann\u002Fdotfiles-stow --skill address-pr-comments",{"tool":38,"command":39},"bunx","bunx skills add heynemann\u002Fdotfiles-stow --skill address-pr-comments",{"tool":41,"command":42},"pnpm","pnpm dlx skills add heynemann\u002Fdotfiles-stow --skill address-pr-comments","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fskills-sh\u002F.agents\u002Fskills\u002Faddress-pr-comments\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7FFA0PAN04C2DVK6A7CXK6K","unity-scriptableobjects","Architect Unity 6.3 LTS data and decoupling with ScriptableObjects: config\u002Fdata assets, shared runtime variables, event channels, and runtime sets\u002Fregistries. Use when designing data-driven systems, replacing singletons\u002Fmanagers, creating .asset data with CreateAssetMenu, or when the user mentions ScriptableObject, SO architecture, or data assets.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-scriptableobjects\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7FF9SPKA8BC4EGCHJGGJK5P","unity-package-management","Adds, removes, upgrades, and discovers Unity (UPM) packages from outside the Editor. Use for headless or CI package installs, verifying package IDs and versions, or choosing which packages a game needs. The Unity CLI doesn't manage packages.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-package-management\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"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},"01M7FF9KBCKR352R6ZSY2BB2J3","unity-input-system","Wire player input in Unity 6.3 LTS with the Input System package: Input Actions, action maps, the PlayerInput component, and reading values via callbacks or polling. Use when the project has a .inputactions asset or com.unity.inputsystem, or when the user mentions the Unity Input System, InputAction, action maps, PlayerInput, control schemes, or rebinding.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-input-system\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7FF9FREKNGB4PQP8ZHTN1D8","unity-ecs-patterns","Master Unity ECS (Entity Component System) with DOTS, Jobs, and Burst for high-performance game development. Use when building data-oriented games, optimizing performance, or working with large entity counts.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-ecs-patterns\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7FF99B1DV7RDAY98QVFFMA9","unity-csharp-scripting","Write Unity 6.3 LTS C# gameplay scripts: the MonoBehaviour lifecycle (Awake\u002FOnEnable\u002FStart\u002FUpdate\u002FFixedUpdate\u002FLateUpdate), GameObject and component access, coroutines, and Inspector serialization. Use when creating or editing .cs scripts in a Unity project, or when the user mentions MonoBehaviour, Start\u002FUpdate, GetComponent, SerializeField, coroutines, or \"Unity script\".","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-csharp-scripting\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7FF8ZK7PAPR4QZ44SY9ZDAJ","unity-cli","Controls the Unity Editor and projects from the command line, driving a running Editor to edit scenes and assets or run C#. Use when asked to install or manage Editors, licenses, or projects, set up version control, build, test, configure the Unity MCP server, or run any unity command.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-cli\u002FSKILL.md",[],[]]