[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74C78GSX3Y8M2BZ1Z79M26P":3,"skill-same:01M74C78GSX3Y8M2BZ1Z79M26P":51},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M74C78GSX3Y8M2BZ1Z79M26P","review-and-merge-pr",null,"Review an open GitHub pull request, inspect feedback from Cursor Bugbot, CodeRabbit, CI, and human reviewers, decide which findings are valid, implement fixes on the PR branch, merge the PR into master when it is ready, and finalize any linked GitHub issue so it matches the make-closed-issue workflow after merge. Use when the user says \"check the PR\", \"address bugbot comments\", \"handle CodeRabbit feedback\", \"review PR feedback\", or \"merge this PR\".","tamarillo-ai\u002Ftheta","tamarillo-ai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F264659913?v=4","01M732W8TW61PS979NJ2W4Z6XZ","tamarillo.ai","01M732W8VRBBGT4F0Q3B2HNGTQ",15,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Ftamarillo-ai\u002Ftheta\u002Fblob\u002Fmain\u002Ftest\u002Fcast-fixtures\u002Fcodex-cli\u002Fregression\u002F5chan\u002F.codex\u002Fskills\u002Freview-and-merge-pr\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: review-and-merge-pr\ndescription: Review an open GitHub pull request, inspect feedback from Cursor Bugbot, CodeRabbit, CI, and human reviewers, decide which findings are valid, implement fixes on the PR branch, merge the PR into master when it is ready, and finalize any linked GitHub issue so it matches the make-closed-issue workflow after merge. Use when the user says \"check the PR\", \"address bugbot comments\", \"handle CodeRabbit feedback\", \"review PR feedback\", or \"merge this PR\".\n---\n\n# Review And Merge Pr\n\n## Overview\n\nUse this skill after a feature branch already has an open PR into `master`.\nStay on the PR branch, treat review bots as input rather than authority, and only merge once the branch is verified and the remaining comments are either fixed, explicitly deferred, or explicitly declined with a reason.\nDo not let repeated nitpicks, speculative future-work comments, or low-value bot suggestions keep the PR open once they have been triaged as non-blocking.\nFinish the workflow by cleaning up local git state yourself; do not assume GitHub, `gh pr merge --delete-branch`, or GitHub Desktop removed the local feature branch or any local `pr\u002F\u003Cnumber>` alias.\n\n## Workflow\n\n### 1. Identify the target PR\n\nPrefer the PR for the current branch when the branch is not `master`.\nIf the current branch is `master`, inspect open PRs and choose the one that matches the user request.\nIf there is no open PR yet, stop and use `make-closed-issue` first.\n\nUseful commands:\n\n```bash\ngh pr status\ngh pr list --repo bitsocialnet\u002F5chan --state open\ngh pr view \u003Cpr-number> --repo bitsocialnet\u002F5chan --json number,title,url,headRefName,baseRefName,isDraft,reviewDecision,mergeStateStatus\n```\n\n### 2. Gather all review signals before changing code\n\nRead the PR state, checks, issue comments, review summaries, and inline review comments before deciding what to change.\nDo not merge based only on the top-level review verdict.\n\nUseful commands:\n\n```bash\ngh pr view \u003Cpr-number> --repo bitsocialnet\u002F5chan --json number,title,url,headRefName,baseRefName,isDraft,reviewDecision,mergeStateStatus\ngh pr checks \u003Cpr-number>\ngh api \"repos\u002Fbitsocialnet\u002F5chan\u002Fissues\u002F\u003Cpr-number>\u002Fcomments?per_page=100\"\ngh api \"repos\u002Fbitsocialnet\u002F5chan\u002Fpulls\u002F\u003Cpr-number>\u002Freviews?per_page=100\"\ngh api \"repos\u002Fbitsocialnet\u002F5chan\u002Fpulls\u002F\u003Cpr-number>\u002Fcomments?per_page=100\"\n```\n\nFocus on comments from:\n\n- Cursor Bugbot\n- CodeRabbit\n- human reviewers\n- failing CI checks\n\n### 3. Triage findings instead of blindly applying them\n\nSort feedback into these buckets:\n\n- `must-fix`: correctness bugs, broken behavior, crashes, security issues, test failures, reproducible regressions\n- `should-fix`: clear maintainability or edge-case issues with concrete evidence\n- `defer`: real but non-blocking follow-up work that can land later without making this PR unsafe to merge\n- `decline`: false positives, stale comments, duplicate findings, speculative style-only suggestions, feedback already addressed in newer commits, or nitpicks that are not worth blocking merge\n\nRules:\n\n- Never merge with unresolved `must-fix` findings.\n- Do not accept a bot finding without reading the relevant code and diff.\n- `should-fix` and `defer` findings are not merge blockers by default; use judgment and prefer merging once the branch is safe, verified, and the remaining comments are low-value or future work.\n- If a finding is ambiguous but high-risk, ask the user before merging.\n- If a comment is wrong, stale, or intentionally deferred, explain that briefly in the PR or merge summary rather than silently ignoring it.\n- After triaging a comment as `defer` or `decline`, do not keep reopening the same discussion unless new evidence appears or the user explicitly asks for a follow-up pass.\n\n### 4. Work on the PR branch and keep the PR updated\n\nSwitch to the PR branch if needed, apply the valid fixes, and push new commits to the same branch.\nDo not open a replacement PR unless the user explicitly asks for that.\n\nUseful commands:\n\n```bash\ngit switch \u003Chead-branch>\ngit fetch origin \u003Chead-branch>\ngit status --short --branch\ngit add \u003Cfiles>\ngit commit -m \"fix(scope): address review feedback\"\ngit push\n```\n\nAfter code changes, follow repo verification rules from `AGENTS.md`:\n\n- run `yarn build`, `yarn lint`, and `yarn type-check`\n- run `yarn test` after adding or changing tests\n- run `yarn doctor` after React UI logic changes\n- use `playwright-cli` for UI\u002Fvisual changes across `chrome`, `firefox`, and `webkit`, plus a mobile viewport flow in each engine when relevant\n\n### 5. Report back on the PR before merging\n\nSummarize what was fixed, what was deferred, and what was declined.\nUse `gh pr comment` for a concise PR update when the branch changed because of review feedback.\n\nExample:\n\n```bash\ngh pr comment \u003Cpr-number> --repo bitsocialnet\u002F5chan --body \"Addressed the valid review findings in the latest commit. Remaining bot comments were triaged as stale, low-value, or follow-up work that does not block this merge.\"\n```\n\n### 6. Merge only when the PR is actually ready\n\nMerge only if all of these are true:\n\n- the PR is not draft\n- required checks are passing\n- the branch is mergeable into `master`\n- no unresolved `must-fix` reviewer findings remain\n- any remaining `should-fix`, `defer`, or `decline` items were consciously triaged and are not worth blocking merge\n- the latest code was verified locally after the last review-driven change\n\nPreferred merge command:\n\n```bash\ngh pr merge \u003Cpr-number> --repo bitsocialnet\u002F5chan --squash --delete-branch\n```\n\n### 7. Finalize linked issues to match `make-closed-issue`\n\nAfter merge, inspect the PR's linked closing issues.\nFor every linked issue, bring it into the same final state expected from `make-closed-issue`:\n\n- closed\n- assigned to the current GitHub user\n- added to the `5chan` project if missing\n- project status `Done`\n\nBefore editing issue assignees, determine the current contributor's GitHub username from the authenticated `gh` session.\nIf `gh` is not signed in or cannot resolve the login, stop and ask the contributor for their GitHub username before proceeding.\nIf the PR has no linked issue, explicitly tell the user that there was no associated issue to finalize.\n\nUseful commands:\n\n```bash\nGH_LOGIN=$(gh api user --jq '.login' 2>\u002Fdev\u002Fnull || true)\n\nif [ -z \"$GH_LOGIN\" ]; then\n  echo \"GitHub username could not be determined from gh auth. Ask the contributor for their GitHub username before proceeding.\"\n  exit 1\nfi\n\nISSUE_NUMBERS=$(gh pr view \u003Cpr-number> --repo bitsocialnet\u002F5chan --json closingIssuesReferences --jq '.closingIssuesReferences[].number')\n\nif [ -n \"$ISSUE_NUMBERS\" ]; then\n  FIELD_JSON=$(gh project field-list 1 --owner bitsocialnet --format json)\n  STATUS_FIELD_ID=$(echo \"$FIELD_JSON\" | jq -r '.fields[] | select(.name==\"Status\") | .id')\n  DONE_OPTION_ID=$(echo \"$FIELD_JSON\" | jq -r '.fields[] | select(.name==\"Status\") | .options[] | select(.name==\"Done\") | .id')\n\n  for ISSUE_NUMBER in $ISSUE_NUMBERS; do\n    ISSUE_STATE=$(gh issue view \"$ISSUE_NUMBER\" --repo bitsocialnet\u002F5chan --json state --jq '.state')\n    if [ \"$ISSUE_STATE\" != \"CLOSED\" ]; then\n      gh issue close \"$ISSUE_NUMBER\" --repo bitsocialnet\u002F5chan\n    fi\n\n    if ! gh issue view \"$ISSUE_NUMBER\" --repo bitsocialnet\u002F5chan --json assignees --jq '.assignees[].login' | grep -qx \"$GH_LOGIN\"; then\n      gh issue edit \"$ISSUE_NUMBER\" --repo bitsocialnet\u002F5chan --add-assignee \"$GH_LOGIN\"\n    fi\n\n    ITEM_ID=$(gh project item-list 1 --owner bitsocialnet --limit 1000 --format json --jq \".items[] | select(.content.number == $ISSUE_NUMBER) | .id\" | head -n1)\n    if [ -z \"$ITEM_ID\" ]; then\n      ITEM_JSON=$(gh project item-add 1 --owner bitsocialnet --url \"https:\u002F\u002Fgithub.com\u002Fbitsocialnet\u002F5chan\u002Fissues\u002F$ISSUE_NUMBER\" --format json)\n      ITEM_ID=$(echo \"$ITEM_JSON\" | jq -r '.id')\n    fi\n\n    gh project item-edit --id \"$ITEM_ID\" --project-id PVT_kwDODohK7M4BM4wg --field-id \"$STATUS_FIELD_ID\" --single-select-option-id \"$DONE_OPTION_ID\"\n  done\nfi\n```\n\n### 8. Clean up local state after merge\n\nAfter the PR is merged:\n\n```bash\ngit switch master\ngit fetch origin --prune\ngit pull --ff-only\ngit branch -D \u003Chead-branch> 2>\u002Fdev\u002Fnull || true\ngit branch -D \"pr\u002F\u003Cpr-number>\" 2>\u002Fdev\u002Fnull || true\n```\n\nThis cleanup is required even when the remote branch was deleted automatically or the merge happened in GitHub Desktop or the GitHub web UI.\nRemote deletion only removes the remote branch; it does not remove the local feature branch, the local `pr\u002F\u003Cnumber>` checkout alias, or stale remote-tracking refs in your clone.\nUse `-D` rather than `-d` here because squash merges usually leave the local branch looking unmerged by ancestry even when the PR is already merged and safe to remove.\n\nIf the PR branch lived in a dedicated worktree, remove that worktree after leaving it:\n\n```bash\ngit worktree list\ngit worktree remove \u002Fpath\u002Fto\u002Fworktree\n```\n\n### 9. Report the outcome\n\nTell the user:\n\n- which findings were fixed\n- which findings were deferred and why they did not block merge\n- which findings were declined and why\n- which verification commands ran\n- whether the PR was merged\n- whether linked issues were confirmed closed\n- whether linked issues were assigned to the current GitHub user\n- whether linked project items were confirmed `Done`\n- whether stale remote-tracking refs were pruned\n- whether the feature branch, local `pr\u002F\u003Cnumber>` alias, and any worktree were cleaned up\n","# Review And Merge Pr\n\n## Overview\n\nUse this skill after a feature branch already has an open PR into `master`.\nStay on the PR branch, treat review bots as input rather than authority, and only merge once the branch is verified and the remaining comments are either fixed, explicitly deferred, or explicitly declined with a reason.\nDo not let repeated nitpicks, speculative future-work comments, or low-value bot suggestions keep the PR open once they have been triaged as non-blocking.\nFinish the workflow by cleaning up local git state yourself; do not assume GitHub, `gh pr merge --delete-branch`, or GitHub Desktop removed the local feature branch or any local `pr\u002F\u003Cnumber>` alias.\n\n## Workflow\n\n### 1. Identify the target PR\n\nPrefer the PR for the current branch when the branch is not `master`.\nIf the current branch is `master`, inspect open PRs and choose the one that matches the user request.\nIf there is no open PR yet, stop and use `make-closed-issue` first.\n\nUseful commands:\n\n```bash\ngh pr status\ngh pr list --repo bitsocialnet\u002F5chan --state open\ngh pr view \u003Cpr-number> --repo bitsocialnet\u002F5chan --json number,title,url,headRefName,baseRefName,isDraft,reviewDecision,mergeStateStatus\n```\n\n### 2. Gather all review signals before changing code\n\nRead the PR state, checks, issue comments, review summaries, and inline review comments before deciding what to change.\nDo not merge based only on the top-level review verdict.\n\nUseful commands:\n\n```bash\ngh pr view \u003Cpr-number> --repo bitsocialnet\u002F5chan --json number,title,url,headRefName,baseRefName,isDraft,reviewDecision,mergeStateStatus\ngh pr checks \u003Cpr-number>\ngh api \"repos\u002Fbitsocialnet\u002F5chan\u002Fissues\u002F\u003Cpr-number>\u002Fcomments?per_page=100\"\ngh api \"repos\u002Fbitsocialnet\u002F5chan\u002Fpulls\u002F\u003Cpr-number>\u002Freviews?per_page=100\"\ngh api \"repos\u002Fbitsocialnet\u002F5chan\u002Fpulls\u002F\u003Cpr-number>\u002Fcomments?per_page=100\"\n```\n\nFocus on comments from:\n\n- Cursor Bugbot\n- CodeRabbit\n- human reviewers\n- failing CI checks\n\n### 3. Triage findings instead of blindly applying them\n\nSort feedback into these buckets:\n\n- `must-fix`: correctness bugs, broken behavior, crashes, security issues, test failures, reproducible regressions\n- `should-fix`: clear maintainability or edge-case issues with concrete evidence\n- `defer`: real but non-blocking follow-up work that can land later without making this PR unsafe to merge\n- `decline`: false positives, stale comments, duplicate findings, speculative style-only suggestions, feedback already addressed in newer commits, or nitpicks that are not worth blocking merge\n\nRules:\n\n- Never merge with unresolved `must-fix` findings.\n- Do not accept a bot finding without reading the relevant code and diff.\n- `should-fix` and `defer` findings are not merge blockers by default; use judgment and prefer merging once the branch is safe, verified, and the remaining comments are low-value or future work.\n- If a finding is ambiguous but high-risk, ask the user before merging.\n- If a comment is wrong, stale, or intentionally deferred, explain that briefly in the PR or merge summary rather than silently ignoring it.\n- After triaging a comment as `defer` or `decline`, do not keep reopening the same discussion unless new evidence appears or the user explicitly asks for a follow-up pass.\n\n### 4. Work on the PR branch and keep the PR updated\n\nSwitch to the PR branch if needed, apply the valid fixes, and push new commits to the same branch.\nDo not open a replacement PR unless the user explicitly asks for that.\n\nUseful commands:\n\n```bash\ngit switch \u003Chead-branch>\ngit fetch origin \u003Chead-branch>\ngit status --short --branch\ngit add \u003Cfiles>\ngit commit -m \"fix(scope): address review feedback\"\ngit push\n```\n\nAfter code changes, follow repo verification rules from `AGENTS.md`:\n\n- run `yarn build`, `yarn lint`, and `yarn type-check`\n- run `yarn test` after adding or changing tests\n- run `yarn doctor` after React UI logic changes\n- use `playwright-cli` for UI\u002Fvisual changes across `chrome`, `firefox`, and `webkit`, plus a mobile viewport flow in each engine when relevant\n\n### 5. Report back on the PR before merging\n\nSummarize what was fixed, what was deferred, and what was declined.\nUse `gh pr comment` for a concise PR update when the branch changed because of review feedback.\n\nExample:\n\n```bash\ngh pr comment \u003Cpr-number> --repo bitsocialnet\u002F5chan --body \"Addressed the valid review findings in the latest commit. Remaining bot comments were triaged as stale, low-value, or follow-up work that does not block this merge.\"\n```\n\n### 6. Merge only when the PR is actually ready\n\nMerge only if all of these are true:\n\n- the PR is not draft\n- required checks are passing\n- the branch is mergeable into `master`\n- no unresolved `must-fix` reviewer findings remain\n- any remaining `should-fix`, `defer`, or `decline` items were consciously triaged and are not worth blocking merge\n- the latest code was verified locally after the last review-driven change\n\nPreferred merge command:\n\n```bash\ngh pr merge \u003Cpr-number> --repo bitsocialnet\u002F5chan --squash --delete-branch\n```\n\n### 7. Finalize linked issues to match `make-closed-issue`\n\nAfter merge, inspect the PR's linked closing issues.\nFor every linked issue, bring it into the same final state expected from `make-closed-issue`:\n\n- closed\n- assigned to the current GitHub user\n- added to the `5chan` project if missing\n- project status `Done`\n\nBefore editing issue assignees, determine the current contributor's GitHub username from the authenticated `gh` session.\nIf `gh` is not signed in or cannot resolve the login, stop and ask the contributor for their GitHub username before proceeding.\nIf the PR has no linked issue, explicitly tell the user that there was no associated issue to finalize.\n\nUseful commands:\n\n```bash\nGH_LOGIN=$(gh api user --jq '.login' 2>\u002Fdev\u002Fnull || true)\n\nif [ -z \"$GH_LOGIN\" ]; then\n  echo \"GitHub username could not be determined from gh auth. Ask the contributor for their GitHub username before proceeding.\"\n  exit 1\nfi\n\nISSUE_NUMBERS=$(gh pr view \u003Cpr-number> --repo bitsocialnet\u002F5chan --json closingIssuesReferences --jq '.closingIssuesReferences[].number')\n\nif [ -n \"$ISSUE_NUMBERS\" ]; then\n  FIELD_JSON=$(gh project field-list 1 --owner bitsocialnet --format json)\n  STATUS_FIELD_ID=$(echo \"$FIELD_JSON\" | jq -r '.fields[] | select(.name==\"Status\") | .id')\n  DONE_OPTION_ID=$(echo \"$FIELD_JSON\" | jq -r '.fields[] | select(.name==\"Status\") | .options[] | select(.name==\"Done\") | .id')\n\n  for ISSUE_NUMBER in $ISSUE_NUMBERS; do\n    ISSUE_STATE=$(gh issue view \"$ISSUE_NUMBER\" --repo bitsocialnet\u002F5chan --json state --jq '.state')\n    if [ \"$ISSUE_STATE\" != \"CLOSED\" ]; then\n      gh issue close \"$ISSUE_NUMBER\" --repo bitsocialnet\u002F5chan\n    fi\n\n    if ! gh issue view \"$ISSUE_NUMBER\" --repo bitsocialnet\u002F5chan --json assignees --jq '.assignees[].login' | grep -qx \"$GH_LOGIN\"; then\n      gh issue edit \"$ISSUE_NUMBER\" --repo bitsocialnet\u002F5chan --add-assignee \"$GH_LOGIN\"\n    fi\n\n    ITEM_ID=$(gh project item-list 1 --owner bitsocialnet --limit 1000 --format json --jq \".items[] | select(.content.number == $ISSUE_NUMBER) | .id\" | head -n1)\n    if [ -z \"$ITEM_ID\" ]; then\n      ITEM_JSON=$(gh project item-add 1 --owner bitsocialnet --url \"https:\u002F\u002Fgithub.com\u002Fbitsocialnet\u002F5chan\u002Fissues\u002F$ISSUE_NUMBER\" --format json)\n      ITEM_ID=$(echo \"$ITEM_JSON\" | jq -r '.id')\n    fi\n\n    gh project item-edit --id \"$ITEM_ID\" --project-id PVT_kwDODohK7M4BM4wg --field-id \"$STATUS_FIELD_ID\" --single-select-option-id \"$DONE_OPTION_ID\"\n  done\nfi\n```\n\n### 8. Clean up local state after merge\n\nAfter the PR is merged:\n\n```bash\ngit switch master\ngit fetch origin --prune\ngit pull --ff-only\ngit branch -D \u003Chead-branch> 2>\u002Fdev\u002Fnull || true\ngit branch -D \"pr\u002F\u003Cpr-number>\" 2>\u002Fdev\u002Fnull || true\n```\n\nThis cleanup is required even when the remote branch was deleted automatically or the merge happened in GitHub Desktop or the GitHub web UI.\nRemote deletion only removes the remote branch; it does not remove the local feature branch, the local `pr\u002F\u003Cnumber>` checkout alias, or stale remote-tracking refs in your clone.\nUse `-D` rather than `-d` here because squash merges usually leave the local branch looking unmerged by ancestry even when the PR is already merged and safe to remove.\n\nIf the PR branch lived in a dedicated worktree, remove that worktree after leaving it:\n\n```bash\ngit worktree list\ngit worktree remove \u002Fpath\u002Fto\u002Fworktree\n```\n\n### 9. Report the outcome\n\nTell the user:\n\n- which findings were fixed\n- which findings were deferred and why they did not block merge\n- which findings were declined and why\n- which verification commands ran\n- whether the PR was merged\n- whether linked issues were confirmed closed\n- whether linked issues were assigned to the current GitHub user\n- whether linked project items were confirmed `Done`\n- whether stale remote-tracking refs were pruned\n- whether the feature branch, local `pr\u002F\u003Cnumber>` alias, and any worktree were cleaned up\n",{"name":5,"description":7},"main","08c084f718b2b842cd53622ce0b1a1fb2888ccef","test\u002Fcast-fixtures\u002Fcodex-cli\u002Fregression\u002F5chan\u002F.codex\u002Fskills\u002Freview-and-merge-pr",1,"https:\u002F\u002Fgithub.com\u002Ftamarillo-ai\u002Ftheta","https:\u002F\u002Fgithub.com\u002Ftamarillo-ai","2026-07-15 23:48:12",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add tamarillo-ai\u002Ftheta --skill review-and-merge-pr",{"tool":37,"command":38},"bunx","bunx skills add tamarillo-ai\u002Ftheta --skill review-and-merge-pr",{"tool":40,"command":41},"pnpm","pnpm dlx skills add tamarillo-ai\u002Ftheta --skill review-and-merge-pr","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftamarillo-ai\u002Ftheta\u002Fblob\u002Fmain\u002Ftest\u002Fcast-fixtures\u002Fcodex-cli\u002Fregression\u002F5chan\u002F.codex\u002Fskills\u002Freview-and-merge-pr\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",237,"https:\u002F\u002Fgithub.com\u002Ftamarillo-ai\u002Ftheta\u002Fblob\u002Fmain\u002Ftest\u002Fcast-fixtures\u002Fcodex-cli\u002Fregression\u002F5chan\u002F.codex\u002Fskills\u002Freview-and-merge-pr\u002Fagents\u002Fopenai.yaml",[52,59,66,74,81,88],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M74FCAJ0RRFRJRQES26329E7","deploy-app","Deploy the application to staging or production environments.","https:\u002F\u002Fgithub.com\u002Ftamarillo-ai\u002Ftheta\u002Fblob\u002Fmain\u002Ftest\u002Fcast-fixtures\u002Fcursor\u002Fskills\u002Fbasic\u002F.cursor\u002Fskills\u002Fdeploy-app\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M74FC8GPJGCS0KTGKS1CJZZS","deploy","Deploy the application to environments.","https:\u002F\u002Fgithub.com\u002Ftamarillo-ai\u002Ftheta\u002Fblob\u002Fmain\u002Ftest\u002Fcast-fixtures\u002Fcursor\u002Fcombined\u002Ffull-config\u002F.cursor\u002Fskills\u002Fdeploy\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M74FC5RT3VTNZEK1F7NX5380","building-native-ui","Complete guide for building beautiful apps with Expo Router. Covers fundamentals, styling, components, navigation, animations, patterns, and native tabs.","MIT","https:\u002F\u002Fgithub.com\u002Ftamarillo-ai\u002Ftheta\u002Fblob\u002Fmain\u002Ftest\u002Fcast-fixtures\u002Fcopilot\u002Fskills\u002Fwith-references\u002F.github\u002Fskills\u002Fbuilding-native-ui\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},"01M74FC1ZGP5R44HPGWWSW6P3B","create-section","Use when creating a new section for the AI Workshop presentation. Guides through title slide setup, layout choices, and content gathering. Activates when user wants to add a new topic section to the slideshow.","https:\u002F\u002Fgithub.com\u002Ftamarillo-ai\u002Ftheta\u002Fblob\u002Fmain\u002Ftest\u002Fcast-fixtures\u002Fcopilot\u002Fskills\u002Fbasic\u002F.github\u002Fskills\u002Fcreate-section\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},"01M74FBZXSZ7GVP0HCGNR1BVNH","ship-checker","Run a full pre-ship review for this repo. Use when asked if a change is ready to deploy, publish, or ship.","https:\u002F\u002Fgithub.com\u002Ftamarillo-ai\u002Ftheta\u002Fblob\u002Fmain\u002Ftest\u002Fcast-fixtures\u002Fcopilot\u002Fcombined\u002Feverything\u002F.github\u002Fskills\u002Fship-checker\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M74FBY4N2E3ZERWBRM4S3DE6","lint-check","Run repository linters and report failures.","https:\u002F\u002Fgithub.com\u002Ftamarillo-ai\u002Ftheta\u002Fblob\u002Fmain\u002Ftest\u002Fcast-fixtures\u002Fcodex-cli\u002Fskills\u002Fagents-path\u002F.agents\u002Fskills\u002Flint-check\u002FSKILL.md",[],[]]