[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75MR7QA2C9F3M4QM6WJSHS7":3,"skill-same:01M75MR7QA2C9F3M4QM6WJSHS7":47},{"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":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M75MR7QA2C9F3M4QM6WJSHS7","gh-cli",null,"Use gh (GitHub CLI) for all GitHub operations — creating PRs, checking status, commenting, and capturing URLs. Prefer gh over GitHub MCP tools to minimize token usage.","whimzyLive\u002Fnightshift-ai","whimzyLive","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F22066605?v=4","01M75MMH22XX6R3NTAFHD7HEN7","Rushi Patel","01M75MMH32DHVVC61XRSHWVEV2",3,"MIT","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fplugins\u002Fsdlc\u002Fskills\u002Fgh-cli\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: gh-cli\ndescription: Use gh (GitHub CLI) for all GitHub operations — creating PRs, checking status, commenting, and capturing URLs. Prefer gh over GitHub MCP tools to minimize token usage.\n---\n\n# gh-cli — GitHub CLI\n\nUse `gh` for all GitHub operations. Never use GitHub MCP tools when gh can do the same job.\n\n## Why gh over MCP\n\nMCP tool calls return full JSON payloads into context. gh runs in Bash, outputs only what you request, and exits. Token cost per operation: gh ≈ 10–50 tokens vs MCP ≈ 500–2000 tokens.\n\n## Authentication\n\ngh reads credentials from `~\u002F.config\u002Fgh\u002F`. Assume it is authenticated. If a command returns an auth error, stop and tell the user to run `gh auth login`.\n\n## Full PR creation workflow\n\nAlways follow this order — never skip steps:\n\n```bash\n# 1. Push branch to remote\ngit push -u origin \"$(git branch --show-current)\"\n\n# 2. Check for existing PR — never create duplicates\nexisting=$(gh pr list --head \"$(git branch --show-current)\" --json url --jq '.[0].url \u002F\u002F empty' 2>&1)\nif [ -n \"$existing\" ]; then\n  echo \"PR already exists: $existing\"\n  exit 0\nfi\n\n# 3. Create PR — always use heredoc for body to avoid shell escaping issues\npr_url=$(gh pr create \\\n  --title \"feat(scope): description\" \\\n  --base develop \\\n  --body \"$(cat \u003C\u003C'EOF'\n## Summary\n- What this PR does (bullet points)\n\n## Test plan\n- [ ] Verification step\nEOF\n)\" 2>&1)\n\necho \"Created PR: $pr_url\"\n```\n\n## Create a PR (minimal form)\n\n```bash\ngh pr create \\\n  --title \"feat(scope): description\" \\\n  --base develop \\\n  --body \"$(cat \u003C\u003C'EOF'\n## Summary\n- \u003Cwhat changed and why>\n\n## Test plan\n- [ ] \u003Chow to verify>\nEOF\n)\"\n```\n\n## Shell escaping rule\n\n**Always use single-quoted `\u003C\u003C'EOF'`** for PR bodies — prevents variable expansion inside the body:\n\n```bash\n# CORRECT — $ENTITY is treated as literal text\n--body \"$(cat \u003C\u003C'EOF'\n## Summary\n- Added $ENTITY support\nEOF\n)\"\n\n# WRONG — shell expands $ENTITY, breaks the body\n--body \"$(cat \u003C\u003CEOF\n## Summary\n- Added $ENTITY support\nEOF\n)\"\n```\n\n## Core commands\n\n### View PR (minimal output — never dump full view)\n\n```bash\n# State + title + URL\ngh pr view --json url,state,title --jq '\"\\(.state) — \\(.title) — \\(.url)\"'\n\n# Review status\ngh pr view --json reviewDecision,mergeable --jq '\"\\(.reviewDecision) \u002F \\(.mergeable)\"'\n```\n\n### List PRs for current branch\n\n```bash\ngh pr list \\\n  --head \"$(git branch --show-current)\" \\\n  --json number,title,url,state \\\n  --jq '.[] | \"\\(.number) [\\(.state)] \\(.title) — \\(.url)\"'\n```\n\n### Add comment to PR or issue\n\n```bash\ngh pr comment \u003Cnumber-or-url> --body \"Spec ready: docs\u002Fsuperpowers\u002Fspecs\u002FCER-123-design.md\"\ngh issue comment \u003Cnumber> --body \"Comment text\"\n```\n\n### Check CI status\n\n```bash\ngh pr checks --json name,state,conclusion \\\n  --jq '.[] | \"\\(.name): \\(.conclusion \u002F\u002F .state)\"'\n```\n\n### Merge a PR (when authorized)\n\n```bash\ngh pr merge \u003Cnumber-or-url> --squash --delete-branch\n```\n\n## Branch conventions\n\n| Artifact | Branch pattern |\n| --- | --- |\n| Idea doc | `ideas\u002F\u003Cslug>` |\n| PRD | `feature\u002Fprd-\u003Cslug>` |\n| Spec, plan | committed to `feat\u002F\u003CJIRA-KEY>`; they ship in the implementation PR (no PR of their own) |\n| DB changes | `feat\u002Fdb\u002F\u003Cfeature>` |\n| Backend | `feat\u002Fbackend\u002F\u003Cfeature>` |\n| Sync | `feat\u002Fsync\u002F\u003Cfeature>` |\n| Web | `feat\u002Fweb\u002F\u003Cfeature>` |\n| Mobile | `feat\u002Fmobile\u002F\u003Cfeature>` |\n\n## PR title conventions\n\n| Phase | Title format |\n| --- | --- |\n| Idea doc | `docs(idea): \u003Cconcept title>` |\n| PRD | `docs(prd): \u003Cfeature title>` |\n| Spec | `docs(spec): \u003CJIRA-KEY> \u003Cstory summary>` |\n| Plan | `docs(plan): \u003CJIRA-KEY> \u003Cfeature title>` |\n| DB | `feat(db): \u003Cdescription>` |\n| Backend | `feat(backend): \u003Cdescription>` |\n| Sync | `feat(sync): \u003Cdescription>` |\n| Web | `feat(web): \u003Cdescription>` |\n| Mobile | `feat(mobile): \u003Cdescription>` |\n\n## PR body template per phase\n\n### Doc artifact PR (idea \u002F PRD)\n\n```\n## Summary\n- Adds \u003Cartifact type> for \u003Cfeature\u002Fstory name>\n- Covers: \u003Ckey decisions made>\n\n## Review checklist\n- [ ] Acceptance criteria are binary (done\u002Fnot done)\n- [ ] No open TBDs without a suggested default\n- [ ] Scope boundaries are explicit\n```\n\n### Implementation PR (DB \u002F backend \u002F sync \u002F web \u002F mobile)\n\n```\n## Summary\n- Implements \u003Cstory key>: \u003Cstory summary>\n- Changes: \u003Clist of key changes>\n\n## Test plan\n- [ ] Project typecheck passes (command from project-context)\n- [ ] Project lint passes (command from project-context)\n- [ ] \u003Cmanual verification step>\n\n## Jira\n\u003CJIRA-KEY>\n```\n\n## Capturing PR URL\n\n```bash\npr_url=$(gh pr create --title \"...\" --base develop --body \"...\" 2>&1)\necho \"PR: $pr_url\"\n# Use $pr_url in follow-up acli comments or return value\n```\n\n## Error handling\n\n| Error | Fix |\n| --- | --- |\n| Auth error | Tell user: `gh auth login` |\n| Branch not pushed | `git push -u origin $(git branch --show-current)` first |\n| PR already exists | Report existing URL, do NOT create duplicate |\n| No commits ahead of base | Nothing to PR — stop and report |\n| `--base` branch not found | Confirm base branch: `git branch -r \\| grep \u003Cconfigured-base-branch>` |\n","# gh-cli — GitHub CLI\n\nUse `gh` for all GitHub operations. Never use GitHub MCP tools when gh can do the same job.\n\n## Why gh over MCP\n\nMCP tool calls return full JSON payloads into context. gh runs in Bash, outputs only what you request, and exits. Token cost per operation: gh ≈ 10–50 tokens vs MCP ≈ 500–2000 tokens.\n\n## Authentication\n\ngh reads credentials from `~\u002F.config\u002Fgh\u002F`. Assume it is authenticated. If a command returns an auth error, stop and tell the user to run `gh auth login`.\n\n## Full PR creation workflow\n\nAlways follow this order — never skip steps:\n\n```bash\n# 1. Push branch to remote\ngit push -u origin \"$(git branch --show-current)\"\n\n# 2. Check for existing PR — never create duplicates\nexisting=$(gh pr list --head \"$(git branch --show-current)\" --json url --jq '.[0].url \u002F\u002F empty' 2>&1)\nif [ -n \"$existing\" ]; then\n  echo \"PR already exists: $existing\"\n  exit 0\nfi\n\n# 3. Create PR — always use heredoc for body to avoid shell escaping issues\npr_url=$(gh pr create \\\n  --title \"feat(scope): description\" \\\n  --base develop \\\n  --body \"$(cat \u003C\u003C'EOF'\n## Summary\n- What this PR does (bullet points)\n\n## Test plan\n- [ ] Verification step\nEOF\n)\" 2>&1)\n\necho \"Created PR: $pr_url\"\n```\n\n## Create a PR (minimal form)\n\n```bash\ngh pr create \\\n  --title \"feat(scope): description\" \\\n  --base develop \\\n  --body \"$(cat \u003C\u003C'EOF'\n## Summary\n- \u003Cwhat changed and why>\n\n## Test plan\n- [ ] \u003Chow to verify>\nEOF\n)\"\n```\n\n## Shell escaping rule\n\n**Always use single-quoted `\u003C\u003C'EOF'`** for PR bodies — prevents variable expansion inside the body:\n\n```bash\n# CORRECT — $ENTITY is treated as literal text\n--body \"$(cat \u003C\u003C'EOF'\n## Summary\n- Added $ENTITY support\nEOF\n)\"\n\n# WRONG — shell expands $ENTITY, breaks the body\n--body \"$(cat \u003C\u003CEOF\n## Summary\n- Added $ENTITY support\nEOF\n)\"\n```\n\n## Core commands\n\n### View PR (minimal output — never dump full view)\n\n```bash\n# State + title + URL\ngh pr view --json url,state,title --jq '\"\\(.state) — \\(.title) — \\(.url)\"'\n\n# Review status\ngh pr view --json reviewDecision,mergeable --jq '\"\\(.reviewDecision) \u002F \\(.mergeable)\"'\n```\n\n### List PRs for current branch\n\n```bash\ngh pr list \\\n  --head \"$(git branch --show-current)\" \\\n  --json number,title,url,state \\\n  --jq '.[] | \"\\(.number) [\\(.state)] \\(.title) — \\(.url)\"'\n```\n\n### Add comment to PR or issue\n\n```bash\ngh pr comment \u003Cnumber-or-url> --body \"Spec ready: docs\u002Fsuperpowers\u002Fspecs\u002FCER-123-design.md\"\ngh issue comment \u003Cnumber> --body \"Comment text\"\n```\n\n### Check CI status\n\n```bash\ngh pr checks --json name,state,conclusion \\\n  --jq '.[] | \"\\(.name): \\(.conclusion \u002F\u002F .state)\"'\n```\n\n### Merge a PR (when authorized)\n\n```bash\ngh pr merge \u003Cnumber-or-url> --squash --delete-branch\n```\n\n## Branch conventions\n\n| Artifact | Branch pattern |\n| --- | --- |\n| Idea doc | `ideas\u002F\u003Cslug>` |\n| PRD | `feature\u002Fprd-\u003Cslug>` |\n| Spec, plan | committed to `feat\u002F\u003CJIRA-KEY>`; they ship in the implementation PR (no PR of their own) |\n| DB changes | `feat\u002Fdb\u002F\u003Cfeature>` |\n| Backend | `feat\u002Fbackend\u002F\u003Cfeature>` |\n| Sync | `feat\u002Fsync\u002F\u003Cfeature>` |\n| Web | `feat\u002Fweb\u002F\u003Cfeature>` |\n| Mobile | `feat\u002Fmobile\u002F\u003Cfeature>` |\n\n## PR title conventions\n\n| Phase | Title format |\n| --- | --- |\n| Idea doc | `docs(idea): \u003Cconcept title>` |\n| PRD | `docs(prd): \u003Cfeature title>` |\n| Spec | `docs(spec): \u003CJIRA-KEY> \u003Cstory summary>` |\n| Plan | `docs(plan): \u003CJIRA-KEY> \u003Cfeature title>` |\n| DB | `feat(db): \u003Cdescription>` |\n| Backend | `feat(backend): \u003Cdescription>` |\n| Sync | `feat(sync): \u003Cdescription>` |\n| Web | `feat(web): \u003Cdescription>` |\n| Mobile | `feat(mobile): \u003Cdescription>` |\n\n## PR body template per phase\n\n### Doc artifact PR (idea \u002F PRD)\n\n```\n## Summary\n- Adds \u003Cartifact type> for \u003Cfeature\u002Fstory name>\n- Covers: \u003Ckey decisions made>\n\n## Review checklist\n- [ ] Acceptance criteria are binary (done\u002Fnot done)\n- [ ] No open TBDs without a suggested default\n- [ ] Scope boundaries are explicit\n```\n\n### Implementation PR (DB \u002F backend \u002F sync \u002F web \u002F mobile)\n\n```\n## Summary\n- Implements \u003Cstory key>: \u003Cstory summary>\n- Changes: \u003Clist of key changes>\n\n## Test plan\n- [ ] Project typecheck passes (command from project-context)\n- [ ] Project lint passes (command from project-context)\n- [ ] \u003Cmanual verification step>\n\n## Jira\n\u003CJIRA-KEY>\n```\n\n## Capturing PR URL\n\n```bash\npr_url=$(gh pr create --title \"...\" --base develop --body \"...\" 2>&1)\necho \"PR: $pr_url\"\n# Use $pr_url in follow-up acli comments or return value\n```\n\n## Error handling\n\n| Error | Fix |\n| --- | --- |\n| Auth error | Tell user: `gh auth login` |\n| Branch not pushed | `git push -u origin $(git branch --show-current)` first |\n| PR already exists | Report existing URL, do NOT create duplicate |\n| No commits ahead of base | Nothing to PR — stop and report |\n| `--base` branch not found | Confirm base branch: `git branch -r \\| grep \u003Cconfigured-base-branch>` |\n",{"name":5,"description":7},"main","7d4ebd573a4218d5e92eced411b259f34e9203fe","plugins\u002Fsdlc\u002Fskills\u002Fgh-cli",0,"https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai","https:\u002F\u002Fwithnightshift.com\u002F","https:\u002F\u002Fgithub.com\u002FwhimzyLive","Creator of @typedorm","2026-11-14 22:45:42",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add whimzyLive\u002Fnightshift-ai --skill gh-cli",{"tool":39,"command":40},"bunx","bunx skills add whimzyLive\u002Fnightshift-ai --skill gh-cli",{"tool":42,"command":43},"pnpm","pnpm dlx skills add whimzyLive\u002Fnightshift-ai --skill gh-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fplugins\u002Fsdlc\u002Fskills\u002Fgh-cli\u002FSKILL.md",true,[],[48,56,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":55},"01M7BCEWYHDS1FWAJ6G4CD9P54","designing-in-patterns","Use when designing, planning or auditing UI against a component library — naming surfaces with the repo's pattern vocabulary, deciding reuse versus extend versus new, exploring compositions, or writing the reuse table (component-plan.md, a spec's `## Reuse`, a UI audit). Carries the design method; the repo's own vocabulary, bundle and board rules come from project-context and the designer override.","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fplugins\u002Fsdlc\u002Fskills\u002Fdesigning-in-patterns\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":57,"name":58,"nameZh":6,"description":59,"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},"01M75MVN6GACAC87SV9RBPBMKH","typeorm","Use when defining TypeORM entities, writing migrations, or building repository\u002Fquery-builder code in TypeScript. Covers entity and relation decorators, the Data Mapper pattern, migrations, the query builder, transactions, and multi-database configuration.","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fskills\u002Ftypeorm\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M75MTEZV8SAZNS20YDSB7KG2","hono-api","Use when building or extending REST APIs with Hono + @hono\u002Fzod-openapi. Covers schema-first route declaration with createRoute, feature-grouped composable routers, a class-based service layer behind interfaces, the strategy pattern for multi-event webhooks, typed request validation, and auto-generated OpenAPI docs.","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fskills\u002Fhono-api\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M75MTB91SB6HPB3ZRT20F950","electrodb","Use when defining DynamoDB entities, modeling indexes, or writing queries\u002Fmutations with the ElectroDB ORM. Covers entity schema, access patterns, CRUD operations, update expressions, and single-table design patterns.","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fskills\u002Felectrodb\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M75MT7KT9A3XYX38TX5MY6MA","atomic-design","Use when structuring or decomposing any frontend UI into reusable components, regardless of framework. Applies Brad Frost's atomic design methodology — atoms, molecules, organisms, templates, and pages — to guide consistent component hierarchy, naming, and composition decisions.","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fskills\u002Fatomic-design\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M75MSTQ54EY0K29PKBF212K1","writing-docs","Use when writing, restructuring, or reviewing any prose documentation — a tutorial, how-to guide, reference page, or explanation\u002Fconceptual doc — for a public docs site (e.g. Mintlify MDX, docs\u002F, README material), a getting-started guide, an API\u002FCLI reference page, or a \"why we built it this way\" conceptual page. Applies the Diátaxis framework (see https:\u002F\u002Fdiataxis.fr\u002F) — every document belongs to exactly one of the four quadrants (tutorial \u002F how-to guide \u002F reference \u002F explanation), and mixing quadrants inside one document is the single most common documentation failure. Covers the four-quadrant compass for picking the right form, per-quadrant structure templates, an anti-pattern list for quadrant drift, and generic voice\u002Fcraft rules — repo-specific voice and target output format (e.g. Mintlify MDX) are resolved from the repo's docs-manifest (falling back to project-context), never hardcoded here.","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fplugins\u002Fsdlc\u002Fskills\u002Fwriting-docs\u002FSKILL.md",[],[]]