[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74F6143FFECCT9XPCPHHYXC":3,"skill-same:01M74F6143FFECCT9XPCPHHYXC":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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M74F6143FFECCT9XPCPHHYXC","make-closed-issue",null,"Create a GitHub issue from recent changes, commit only relevant diffs on a short-lived task branch, push that branch, and open a PR into master that will close the issue on merge. Use when the user says \"make closed issue\", \"close issue\", or wants to create a tracked, already-resolved GitHub issue for completed work.","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\u002Fseedit\u002F.codex\u002Fskills\u002Fmake-closed-issue\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: make-closed-issue\ndescription: Create a GitHub issue from recent changes, commit only relevant diffs on a short-lived task branch, push that branch, and open a PR into master that will close the issue on merge. Use when the user says \"make closed issue\", \"close issue\", or wants to create a tracked, already-resolved GitHub issue for completed work.\n---\n\n# Make Closed Issue\n\nCreates a GitHub issue, commits relevant changes on a review branch, pushes the branch, and opens a PR into `master` that closes the issue when merged.\n\n## Inputs\n\n- What changed and why (from prior conversation context)\n- Uncommitted or staged git changes in the working tree\n\n## Workflow\n\n### 1. Determine label(s)\n\nThe agent should choose the issue label(s) itself from the conversation context and diff. Do **not** ask the user to pick labels unless the work is genuinely ambiguous after reviewing both.\n\nDefault mapping:\n\n| Option | When |\n|--------|------|\n| `bug` | Bug fix |\n| `enhancement` | New feature |\n| `bug` + `enhancement` | New feature that also fixes a bug |\n| `documentation` | README, AGENTS.md, docs-only changes |\n\nWhen the classification is ambiguous, make the best reasonable choice and note the reasoning in the final summary. Only ask the user if the ambiguity would materially affect tracking or triage.\n\n### 2. Resolve the current GitHub assignee\n\nBefore creating or editing any issue assignee, 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.\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```\n\n### 3. Ensure branch workflow is reviewable\n\n- If already on a short-lived task branch such as `codex\u002Ffeature\u002F*`, `codex\u002Ffix\u002F*`, `codex\u002Fdocs\u002F*`, or `codex\u002Fchore\u002F*`, stay on it.\n- If on `master`, create a task branch before staging or committing.\n- Do **not** commit the work directly on `master` when PR review bots are expected.\n\nSuggested naming:\n\n- `codex\u002Ffeature\u002Fshort-slug`\n- `codex\u002Ffix\u002Fshort-slug`\n- `codex\u002Fdocs\u002Fshort-slug`\n- `codex\u002Fchore\u002Fshort-slug`\n\nExample:\n\n```bash\ngit switch -c codex\u002Ffix\u002Freply-editor-stuck\n```\n\n### 4. Review diffs for relevance\n\n```bash\ngit status\ngit diff\ngit diff --cached\n```\n\nIdentify which files relate to the work done in this conversation. Only relevant changes get committed. Unrelated files must be excluded from staging.\n\n**Important**: `git add -p` and `git add -i` are not available (interactive mode unsupported). If a file has mixed relevant\u002Firrelevant changes, include the entire file and note the caveat to the user.\n\n### 5. Generate issue title and description\n\nFrom the conversation context:\n\n- **Title**: Short, present-tense, describes the **problem** (not the solution). Use backticks for UI elements, code, or literal strings (e.g. Post page `` `Update` `` button disabled and `` `Auto` `` alert unclear).\n- **Description**: 2-3 sentences about the problem. Use backticks for UI element names (`Update`, `Auto`), function\u002Fcode references (`useReplies().reset()`), and literal text strings. Write as if the issue hasn't been fixed yet.\n\n### 6. Create the issue\n\n```bash\ngh issue create \\\n  --repo bitsocialnet\u002Fseedit \\\n  --title \"ISSUE_TITLE\" \\\n  --body \"ISSUE_DESCRIPTION\" \\\n  --label \"LABEL1,LABEL2\" \\\n  --assignee \"$GH_LOGIN\"\n```\n\nCapture the issue number from the output.\n\n### 7. Commit relevant changes\n\nStage only the relevant files:\n\n```bash\ngit add file1.ts file2.tsx ...\n```\n\nCommit using Conventional Commits with scope:\n\n```bash\ngit commit -m \"$(cat \u003C\u003C'EOF'\ntype(scope): concise title\n\nOptional 1-sentence description only if the title isn't self-explanatory.\nEOF\n)\"\n```\n\n- **Types**: `fix`, `feat`, `perf`, `refactor`, `docs`, `chore`\n- **Scope**: area of the codebase (e.g., `reply-modal`, `markdown`, `routing`)\n- Prefer title-only commits — skip description when the title is exhaustive\n\n### 8. Push branch and open PR\n\nPush the current task branch to origin and open a PR into `master`.\n\nUse `Closes #ISSUE_NUMBER` in the PR body so the issue closes automatically when the PR is merged.\n\n```bash\nCOMMIT_HASH=$(git rev-parse HEAD)\nBRANCH_NAME=$(git branch --show-current)\ngit push -u origin \"$BRANCH_NAME\"\n\ngh pr create \\\n  --repo bitsocialnet\u002Fseedit \\\n  --base master \\\n  --head \"$BRANCH_NAME\" \\\n  --title \"PR_TITLE\" \\\n  --body \"$(cat \u003C\u003CEOF\nSUMMARY\n\nCloses #ISSUE_NUMBER\nEOF\n)\"\n```\n\nDo **not** merge the PR locally as part of this skill. Review bots must be allowed to inspect the PR first.\n\nIf the user later explicitly asks to merge after reviews pass, a separate merge step can be run, for example:\n\n```bash\ngh pr merge --squash --delete-branch\n```\n\n### 9. Add to project board\n\nUse **gh CLI** for project operations (never GitHub MCP).\n\nAdd the issue to the project when the PR is opened, but do **not** force it to `Done` yet.\n\n```bash\nITEM_JSON=$(gh project item-add 1 --owner bitsocialnet --url \"https:\u002F\u002Fgithub.com\u002Fbitsocialnet\u002Fseedit\u002Fissues\u002FISSUE_NUMBER\" --format json)\nITEM_ID=$(echo \"$ITEM_JSON\" | jq -r '.id')\n```\n\nIf the user later explicitly asks to merge the reviewed PR in the same run, reuse `ITEM_ID` and then set the project item to `Done`:\n\n```bash\n# Get Status field ID and Done option ID from project\nFIELD_JSON=$(gh project field-list 1 --owner bitsocialnet --format json)\nSTATUS_FIELD_ID=$(echo \"$FIELD_JSON\" | jq -r '.fields[] | select(.name==\"Status\") | .id')\nDONE_OPTION_ID=$(echo \"$FIELD_JSON\" | jq -r '.fields[] | select(.name==\"Status\") | .options[] | select(.name==\"Done\") | .id')\n\n# Set status to Done\ngh project item-edit --id \"$ITEM_ID\" --project-id PVT_kwDODohK7M4BM4wg --field-id \"$STATUS_FIELD_ID\" --single-select-option-id \"$DONE_OPTION_ID\"\n```\n\nAssignees and labels are inherited from the issue (set in step 6) — no separate project update needed.\n\n### 10. Report summary\n\nPrint a summary to the user:\n\n```\nIssue #NUMBER created, committed, pushed, and linked to a PR into master.\n  Branch: BRANCH_NAME\n  Commit: HASH\n  Labels: label1, label2\n  PR: PR_URL\n  Project: seedit\n  URL: https:\u002F\u002Fgithub.com\u002Fbitsocialnet\u002Fseedit\u002Fissues\u002FNUMBER\n```\n\nIf the PR has not been merged yet, explicitly tell the user that the issue will close on PR merge and that the branch should not be deleted yet.\n\nAfter the PR is open, use `review-and-merge-pr` to inspect Bugbot, CodeRabbit, CI, and human feedback before merging.\n","# Make Closed Issue\n\nCreates a GitHub issue, commits relevant changes on a review branch, pushes the branch, and opens a PR into `master` that closes the issue when merged.\n\n## Inputs\n\n- What changed and why (from prior conversation context)\n- Uncommitted or staged git changes in the working tree\n\n## Workflow\n\n### 1. Determine label(s)\n\nThe agent should choose the issue label(s) itself from the conversation context and diff. Do **not** ask the user to pick labels unless the work is genuinely ambiguous after reviewing both.\n\nDefault mapping:\n\n| Option | When |\n|--------|------|\n| `bug` | Bug fix |\n| `enhancement` | New feature |\n| `bug` + `enhancement` | New feature that also fixes a bug |\n| `documentation` | README, AGENTS.md, docs-only changes |\n\nWhen the classification is ambiguous, make the best reasonable choice and note the reasoning in the final summary. Only ask the user if the ambiguity would materially affect tracking or triage.\n\n### 2. Resolve the current GitHub assignee\n\nBefore creating or editing any issue assignee, 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.\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```\n\n### 3. Ensure branch workflow is reviewable\n\n- If already on a short-lived task branch such as `codex\u002Ffeature\u002F*`, `codex\u002Ffix\u002F*`, `codex\u002Fdocs\u002F*`, or `codex\u002Fchore\u002F*`, stay on it.\n- If on `master`, create a task branch before staging or committing.\n- Do **not** commit the work directly on `master` when PR review bots are expected.\n\nSuggested naming:\n\n- `codex\u002Ffeature\u002Fshort-slug`\n- `codex\u002Ffix\u002Fshort-slug`\n- `codex\u002Fdocs\u002Fshort-slug`\n- `codex\u002Fchore\u002Fshort-slug`\n\nExample:\n\n```bash\ngit switch -c codex\u002Ffix\u002Freply-editor-stuck\n```\n\n### 4. Review diffs for relevance\n\n```bash\ngit status\ngit diff\ngit diff --cached\n```\n\nIdentify which files relate to the work done in this conversation. Only relevant changes get committed. Unrelated files must be excluded from staging.\n\n**Important**: `git add -p` and `git add -i` are not available (interactive mode unsupported). If a file has mixed relevant\u002Firrelevant changes, include the entire file and note the caveat to the user.\n\n### 5. Generate issue title and description\n\nFrom the conversation context:\n\n- **Title**: Short, present-tense, describes the **problem** (not the solution). Use backticks for UI elements, code, or literal strings (e.g. Post page `` `Update` `` button disabled and `` `Auto` `` alert unclear).\n- **Description**: 2-3 sentences about the problem. Use backticks for UI element names (`Update`, `Auto`), function\u002Fcode references (`useReplies().reset()`), and literal text strings. Write as if the issue hasn't been fixed yet.\n\n### 6. Create the issue\n\n```bash\ngh issue create \\\n  --repo bitsocialnet\u002Fseedit \\\n  --title \"ISSUE_TITLE\" \\\n  --body \"ISSUE_DESCRIPTION\" \\\n  --label \"LABEL1,LABEL2\" \\\n  --assignee \"$GH_LOGIN\"\n```\n\nCapture the issue number from the output.\n\n### 7. Commit relevant changes\n\nStage only the relevant files:\n\n```bash\ngit add file1.ts file2.tsx ...\n```\n\nCommit using Conventional Commits with scope:\n\n```bash\ngit commit -m \"$(cat \u003C\u003C'EOF'\ntype(scope): concise title\n\nOptional 1-sentence description only if the title isn't self-explanatory.\nEOF\n)\"\n```\n\n- **Types**: `fix`, `feat`, `perf`, `refactor`, `docs`, `chore`\n- **Scope**: area of the codebase (e.g., `reply-modal`, `markdown`, `routing`)\n- Prefer title-only commits — skip description when the title is exhaustive\n\n### 8. Push branch and open PR\n\nPush the current task branch to origin and open a PR into `master`.\n\nUse `Closes #ISSUE_NUMBER` in the PR body so the issue closes automatically when the PR is merged.\n\n```bash\nCOMMIT_HASH=$(git rev-parse HEAD)\nBRANCH_NAME=$(git branch --show-current)\ngit push -u origin \"$BRANCH_NAME\"\n\ngh pr create \\\n  --repo bitsocialnet\u002Fseedit \\\n  --base master \\\n  --head \"$BRANCH_NAME\" \\\n  --title \"PR_TITLE\" \\\n  --body \"$(cat \u003C\u003CEOF\nSUMMARY\n\nCloses #ISSUE_NUMBER\nEOF\n)\"\n```\n\nDo **not** merge the PR locally as part of this skill. Review bots must be allowed to inspect the PR first.\n\nIf the user later explicitly asks to merge after reviews pass, a separate merge step can be run, for example:\n\n```bash\ngh pr merge --squash --delete-branch\n```\n\n### 9. Add to project board\n\nUse **gh CLI** for project operations (never GitHub MCP).\n\nAdd the issue to the project when the PR is opened, but do **not** force it to `Done` yet.\n\n```bash\nITEM_JSON=$(gh project item-add 1 --owner bitsocialnet --url \"https:\u002F\u002Fgithub.com\u002Fbitsocialnet\u002Fseedit\u002Fissues\u002FISSUE_NUMBER\" --format json)\nITEM_ID=$(echo \"$ITEM_JSON\" | jq -r '.id')\n```\n\nIf the user later explicitly asks to merge the reviewed PR in the same run, reuse `ITEM_ID` and then set the project item to `Done`:\n\n```bash\n# Get Status field ID and Done option ID from project\nFIELD_JSON=$(gh project field-list 1 --owner bitsocialnet --format json)\nSTATUS_FIELD_ID=$(echo \"$FIELD_JSON\" | jq -r '.fields[] | select(.name==\"Status\") | .id')\nDONE_OPTION_ID=$(echo \"$FIELD_JSON\" | jq -r '.fields[] | select(.name==\"Status\") | .options[] | select(.name==\"Done\") | .id')\n\n# Set status to Done\ngh project item-edit --id \"$ITEM_ID\" --project-id PVT_kwDODohK7M4BM4wg --field-id \"$STATUS_FIELD_ID\" --single-select-option-id \"$DONE_OPTION_ID\"\n```\n\nAssignees and labels are inherited from the issue (set in step 6) — no separate project update needed.\n\n### 10. Report summary\n\nPrint a summary to the user:\n\n```\nIssue #NUMBER created, committed, pushed, and linked to a PR into master.\n  Branch: BRANCH_NAME\n  Commit: HASH\n  Labels: label1, label2\n  PR: PR_URL\n  Project: seedit\n  URL: https:\u002F\u002Fgithub.com\u002Fbitsocialnet\u002Fseedit\u002Fissues\u002FNUMBER\n```\n\nIf the PR has not been merged yet, explicitly tell the user that the issue will close on PR merge and that the branch should not be deleted yet.\n\nAfter the PR is open, use `review-and-merge-pr` to inspect Bugbot, CodeRabbit, CI, and human feedback before merging.\n",{"name":5,"description":7},"main","08c084f718b2b842cd53622ce0b1a1fb2888ccef","test\u002Fcast-fixtures\u002Fcodex-cli\u002Fregression\u002Fseedit\u002F.codex\u002Fskills\u002Fmake-closed-issue",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 make-closed-issue",{"tool":37,"command":38},"bunx","bunx skills add tamarillo-ai\u002Ftheta --skill make-closed-issue",{"tool":40,"command":41},"pnpm","pnpm dlx skills add tamarillo-ai\u002Ftheta --skill make-closed-issue","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftamarillo-ai\u002Ftheta\u002Fblob\u002Fmain\u002Ftest\u002Fcast-fixtures\u002Fcodex-cli\u002Fregression\u002Fseedit\u002F.codex\u002Fskills\u002Fmake-closed-issue\u002FSKILL.md",true,[],[46,53,60,68,75,82],{"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},"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":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},"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":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"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":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},"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":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},"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":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},"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",[],[]]