[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EX5XV5V0SCNTAXESKCE6A2":3,"skill-same:01M7EX5XV5V0SCNTAXESKCE6A2":50},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7EX5XV5V0SCNTAXESKCE6A2","generate-a-commit-message",null,"Inspects staged\u002Funstaged changes and produces a short, clean Conventional Commit message that satisfies this repo's commitlint.config.js. Delegates phrasing to the `caveman` skill (full) so the subject is terse and free of filler. Auto-detects ticket IDs (e.g. APP-1234) from the current branch and appends a `Refs:` footer. Validates the final message with `pnpm exec commitlint --edit` before presenting. Use when user says \"generate commit message\", \"write commit\", \"commit msg\", \"what should the commit be\", or invokes \u002Fgenerate-a-commit-message — typically just before `git commit`.","Phenomenon-Studio\u002Fphenomenon-configs","Phenomenon-Studio","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F85674486?v=4","01M7EX2X2JF76C91JB202QMQHW","Phenomenon studio","01M7EX2X37T2C5FBHAH4B60YMX",1,"MIT","https:\u002F\u002Fgithub.com\u002FPhenomenon-Studio\u002Fphenomenon-configs\u002Fblob\u002Fmain\u002Fexamples\u002Fvite-css-modules\u002F.claude\u002Fskills\u002Fgenerate-a-commit-message\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: generate-a-commit-message\ndescription: >\n  Inspects staged\u002Funstaged changes and produces a short, clean Conventional Commit\n  message that satisfies this repo's commitlint.config.js. Delegates phrasing to the\n  `caveman` skill (full) so the subject is terse and free of filler. Auto-detects\n  ticket IDs (e.g. APP-1234) from the current branch and appends a `Refs:` footer.\n  Validates the final message with `pnpm exec commitlint --edit` before presenting.\n  Use when user says \"generate commit message\", \"write commit\", \"commit msg\",\n  \"what should the commit be\", or invokes \u002Fgenerate-a-commit-message — typically just\n  before `git commit`.\nallowed-tools: Read, Bash\nmodel: sonnet\n---\n\n# Generate Commit Message\n\n## Quick start\n\n1. Read changes: `git status` + `git diff --staged` (fall back to `git diff` if nothing staged).\n2. Read current branch: `git rev-parse --abbrev-ref HEAD`. Extract any `[A-Z]+-\\d+` ticket ID.\n3. Pick **one** type from the enum: `build | ci | docs | feat | fix | perf | refactor | revert | style | test`.\n4. Pick an optional lower-case scope from the touched area (e.g. `auth`, `e2e`, `deps`).\n5. Apply the [`caveman`](..\u002Fcaveman\u002FSKILL.md) skill at **full** level to draft the subject — drop articles, fragments OK, short synonyms.\n6. Append `Refs: \u003CTICKET-ID>` footer when a ticket ID was found on the branch.\n7. Validate by piping the message through `pnpm exec commitlint --edit` (see [Validation](#validation)).\n8. Output the final message; do not run `git commit` unless the user asks.\n\n## Commitlint rules to respect\n\nFrom [`commitlint.config.js`](..\u002F..\u002F..\u002Fcommitlint.config.js):\n\n- `type-enum`: only the 10 types above. No others.\n- `type-case` \u002F `scope-case`: **lower-case** only.\n- `subject-case`: NEVER sentence-case, start-case, pascal-case, or upper-case → write subject in lower-case (or imperative mood with lowercase first word).\n- `subject-empty`: required.\n- `subject-full-stop`: no trailing `.`.\n- `header-max-length`: **≤ 100 chars** total (`type(scope): subject`).\n- `body-leading-blank` + `footer-leading-blank`: blank line before each.\n- `body-max-line-length`: 200. `footer-max-line-length`: 100.\n\n## Workflow\n\n- [ ] `git status` + `git diff --staged` (or `git diff` if nothing staged).\n- [ ] `git rev-parse --abbrev-ref HEAD` → extract `[A-Z]+-\\d+` ticket ID if present.\n- [ ] Group changes by intent. Pick the **dominant** one for the type. Mixed concerns → suggest splitting, do not invent a multi-type header.\n- [ ] Choose scope from the most-touched directory\u002Ffeature. Skip scope if changes span unrelated areas.\n- [ ] Draft subject in **caveman full**: imperative verb, drop articles, fragments OK, short synonyms (`fix` not `implement a solution for`), no period, lowercase.\n- [ ] Add a body **only** if the *why* is non-obvious from the diff. Otherwise omit.\n- [ ] Append `Refs: \u003CTICKET-ID>` footer when ticket ID found.\n- [ ] Validate with `commitlint --edit` (see below). If it fails, fix and revalidate.\n- [ ] Present the message; do not run `git commit` unless the user asks.\n\n## Validation\n\nThe repo already gates commits via [`.husky\u002Fcommit-msg`](..\u002F..\u002F..\u002F.husky\u002Fcommit-msg) running `pnpm exec commitlint --edit $1`. Reuse that exact tool for pre-flight validation:\n\n```bash\n# Write candidate message to a temp file, then validate.\nprintf '%s\\n' \"$MESSAGE\" > \u002Ftmp\u002Fcommit-msg-candidate\npnpm exec commitlint --edit \u002Ftmp\u002Fcommit-msg-candidate\n```\n\nExit code `0` = valid. Non-zero = read the violations and rewrite. Do not bypass with `--no-verify`.\n\n## Type cheatsheet\n\n| Type | Use when |\n|------|----------|\n| `feat` | new user-visible capability |\n| `fix` | bug fix |\n| `refactor` | code change, no behavior change |\n| `perf` | performance improvement |\n| `style` | whitespace\u002Fformatting only |\n| `test` | add\u002Fadjust tests only |\n| `docs` | docs\u002Fcomments only |\n| `build` | build system, deps, bundler, scripts |\n| `ci` | CI config and pipelines |\n| `revert` | revert a previous commit |\n\n## Examples\n\nSubject only (caveman **full**):\n\n```\nfeat(assessments): add bulk archive\n```\n```\nfix(auth): handle expired refresh token on boot\n```\n```\nrefactor(auth): replace getLocalStorageValueWithoutQuetes with parse\u002Fstringify\n```\n```\ntest: add unit tests for storage utils\n```\n\nWith auto-detected ticket footer (branch `feat\u002FAPP-1234-bulk-archive`):\n\n```\nfeat(assessments): add bulk archive\n\nRefs: APP-1234\n```\n\nBody + footer (only when *why* is non-obvious):\n\n```\nfix(api): retry survey submission on 502\n\nBackend behind CDN occasionally returns 502 during deploys. One retry hides transient blip from user.\n\nRefs: APP-1234\n```\n\n## Don'ts\n\n- No emojis. No trailing period. No upper-case first letter in subject.\n- No vague subjects like `update code`, `fix stuff`, `misc changes`.\n- Do not invent a ticket ID — only use one if it actually appears on the branch name.\n- Do not stage files or run `git commit` unless explicitly asked.\n- Do not bypass commitlint with `--no-verify`.\n","# Generate Commit Message\n\n## Quick start\n\n1. Read changes: `git status` + `git diff --staged` (fall back to `git diff` if nothing staged).\n2. Read current branch: `git rev-parse --abbrev-ref HEAD`. Extract any `[A-Z]+-\\d+` ticket ID.\n3. Pick **one** type from the enum: `build | ci | docs | feat | fix | perf | refactor | revert | style | test`.\n4. Pick an optional lower-case scope from the touched area (e.g. `auth`, `e2e`, `deps`).\n5. Apply the [`caveman`](..\u002Fcaveman\u002FSKILL.md) skill at **full** level to draft the subject — drop articles, fragments OK, short synonyms.\n6. Append `Refs: \u003CTICKET-ID>` footer when a ticket ID was found on the branch.\n7. Validate by piping the message through `pnpm exec commitlint --edit` (see [Validation](#validation)).\n8. Output the final message; do not run `git commit` unless the user asks.\n\n## Commitlint rules to respect\n\nFrom [`commitlint.config.js`](..\u002F..\u002F..\u002Fcommitlint.config.js):\n\n- `type-enum`: only the 10 types above. No others.\n- `type-case` \u002F `scope-case`: **lower-case** only.\n- `subject-case`: NEVER sentence-case, start-case, pascal-case, or upper-case → write subject in lower-case (or imperative mood with lowercase first word).\n- `subject-empty`: required.\n- `subject-full-stop`: no trailing `.`.\n- `header-max-length`: **≤ 100 chars** total (`type(scope): subject`).\n- `body-leading-blank` + `footer-leading-blank`: blank line before each.\n- `body-max-line-length`: 200. `footer-max-line-length`: 100.\n\n## Workflow\n\n- [ ] `git status` + `git diff --staged` (or `git diff` if nothing staged).\n- [ ] `git rev-parse --abbrev-ref HEAD` → extract `[A-Z]+-\\d+` ticket ID if present.\n- [ ] Group changes by intent. Pick the **dominant** one for the type. Mixed concerns → suggest splitting, do not invent a multi-type header.\n- [ ] Choose scope from the most-touched directory\u002Ffeature. Skip scope if changes span unrelated areas.\n- [ ] Draft subject in **caveman full**: imperative verb, drop articles, fragments OK, short synonyms (`fix` not `implement a solution for`), no period, lowercase.\n- [ ] Add a body **only** if the *why* is non-obvious from the diff. Otherwise omit.\n- [ ] Append `Refs: \u003CTICKET-ID>` footer when ticket ID found.\n- [ ] Validate with `commitlint --edit` (see below). If it fails, fix and revalidate.\n- [ ] Present the message; do not run `git commit` unless the user asks.\n\n## Validation\n\nThe repo already gates commits via [`.husky\u002Fcommit-msg`](..\u002F..\u002F..\u002F.husky\u002Fcommit-msg) running `pnpm exec commitlint --edit $1`. Reuse that exact tool for pre-flight validation:\n\n```bash\n# Write candidate message to a temp file, then validate.\nprintf '%s\\n' \"$MESSAGE\" > \u002Ftmp\u002Fcommit-msg-candidate\npnpm exec commitlint --edit \u002Ftmp\u002Fcommit-msg-candidate\n```\n\nExit code `0` = valid. Non-zero = read the violations and rewrite. Do not bypass with `--no-verify`.\n\n## Type cheatsheet\n\n| Type | Use when |\n|------|----------|\n| `feat` | new user-visible capability |\n| `fix` | bug fix |\n| `refactor` | code change, no behavior change |\n| `perf` | performance improvement |\n| `style` | whitespace\u002Fformatting only |\n| `test` | add\u002Fadjust tests only |\n| `docs` | docs\u002Fcomments only |\n| `build` | build system, deps, bundler, scripts |\n| `ci` | CI config and pipelines |\n| `revert` | revert a previous commit |\n\n## Examples\n\nSubject only (caveman **full**):\n\n```\nfeat(assessments): add bulk archive\n```\n```\nfix(auth): handle expired refresh token on boot\n```\n```\nrefactor(auth): replace getLocalStorageValueWithoutQuetes with parse\u002Fstringify\n```\n```\ntest: add unit tests for storage utils\n```\n\nWith auto-detected ticket footer (branch `feat\u002FAPP-1234-bulk-archive`):\n\n```\nfeat(assessments): add bulk archive\n\nRefs: APP-1234\n```\n\nBody + footer (only when *why* is non-obvious):\n\n```\nfix(api): retry survey submission on 502\n\nBackend behind CDN occasionally returns 502 during deploys. One retry hides transient blip from user.\n\nRefs: APP-1234\n```\n\n## Don'ts\n\n- No emojis. No trailing period. No upper-case first letter in subject.\n- No vague subjects like `update code`, `fix stuff`, `misc changes`.\n- Do not invent a ticket ID — only use one if it actually appears on the branch name.\n- Do not stage files or run `git commit` unless explicitly asked.\n- Do not bypass commitlint with `--no-verify`.\n",{"name":5,"model":24,"description":25,"allowed-tools":26},"sonnet","Inspects staged\u002Funstaged changes and produces a short, clean Conventional Commit message that satisfies this repo's commitlint.config.js. Delegates phrasing to the `caveman` skill (full) so the subject is terse and free of filler. Auto-detects ticket IDs (e.g. APP-1234) from the current branch and appends a `Refs:` footer. Validates the final message with `pnpm exec commitlint --edit` before presenting. Use when user says \"generate commit message\", \"write commit\", \"commit msg\", \"what should the commit be\", or invokes \u002Fgenerate-a-commit-message — typically just before `git commit`.\n","Read, Bash","main","a5c9ac2f39c1611831e417faea2e6d635699d9b5","examples\u002Fvite-css-modules\u002F.claude\u002Fskills\u002Fgenerate-a-commit-message",0,"https:\u002F\u002Fgithub.com\u002FPhenomenon-Studio\u002Fphenomenon-configs","https:\u002F\u002Fgithub.com\u002FPhenomenon-Studio","https:\u002F\u002Fphenomenonstudio.com\u002F","Phenomenon is a digital product studio bolstering a core team of world-class developers, designers, and a flexible network of multi-specialized talent. ","2026-10-23 17:20:31",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add Phenomenon-Studio\u002Fphenomenon-configs --skill generate-a-commit-message",{"tool":42,"command":43},"bunx","bunx skills add Phenomenon-Studio\u002Fphenomenon-configs --skill generate-a-commit-message",{"tool":45,"command":46},"pnpm","pnpm dlx skills add Phenomenon-Studio\u002Fphenomenon-configs --skill generate-a-commit-message","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPhenomenon-Studio\u002Fphenomenon-configs\u002Fblob\u002Fmain\u002Fexamples\u002Fvite-css-modules\u002F.claude\u002Fskills\u002Fgenerate-a-commit-message\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7EXBNNR8YZB8PD7J8ZAB5FP","web-security","Enforce web security and avoid security vulnerabilities.","https:\u002F\u002Fgithub.com\u002FPhenomenon-Studio\u002Fphenomenon-configs\u002Fblob\u002Fmain\u002Ftemplate\u002Fproject\u002F{{ '.' if scope == 'app' and stack == 'vite' else '' }}\u002F.claude\u002Fskills\u002Fweb-security\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7EXBJGWKB32NY4R2V141G0S","typescript","Write clean, efficient TypeScript code that follows project conventions and advanced type patterns. Use when writing or reviewing TypeScript code, defining types, creating generics, handling errors, or working with React components, Zod schemas, and TanStack libraries.","https:\u002F\u002Fgithub.com\u002FPhenomenon-Studio\u002Fphenomenon-configs\u002Fblob\u002Fmain\u002Ftemplate\u002Fproject\u002F{{ '.' if scope == 'app' and stack == 'vite' else '' }}\u002F.claude\u002Fskills\u002Ftypescript\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7EXBESDHFPHAZKN292SDB6E","tanstack-router","TanStack Router patterns for this repo — file-based routing, auth guards, search params, data loading, TanStack Query integration, navigation, and code splitting. Use when creating routes, adding pages, implementing auth flows, working with search\u002Fpath params, or integrating loaders with TanStack Query.","https:\u002F\u002Fgithub.com\u002FPhenomenon-Studio\u002Fphenomenon-configs\u002Fblob\u002Fmain\u002Ftemplate\u002Fproject\u002F{{ '.' if scope == 'app' and stack == 'vite' else '' }}\u002F.claude\u002Fskills\u002Ftanstack-router\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7EXBAZW0KSMGVDB9DW157SD","tanstack-query","TanStack Query patterns for this repo — queryOptions\u002FmutationOptions factories, query key hierarchies, service layer integration, optimistic updates, Suspense usage, error handling, and TanStack Router data loading. Use when creating queries, mutations, API services, query keys, cache invalidation, optimistic updates, or integrating data fetching with routes.","https:\u002F\u002Fgithub.com\u002FPhenomenon-Studio\u002Fphenomenon-configs\u002Fblob\u002Fmain\u002Ftemplate\u002Fproject\u002F{{ '.' if scope == 'app' and stack == 'vite' else '' }}\u002F.claude\u002Fskills\u002Ftanstack-query\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7EXB6X2TG4HYWCYB293581T","tanstack-form","Build forms using TanStack Form with the project's useAppForm composition, composable field components, Zod validation schemas, FormFieldWrapper error tracking, and form.AppField vs form.Field patterns. Use when creating new forms, adding form fields, writing form validation, or working with TanStack Form in this project.","https:\u002F\u002Fgithub.com\u002FPhenomenon-Studio\u002Fphenomenon-configs\u002Fblob\u002Fmain\u002Ftemplate\u002Fproject\u002F{{ '.' if scope == 'app' and stack == 'vite' else '' }}\u002F.claude\u002Fskills\u002Ftanstack-form\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7EXB4EXHFSSVY64QQAE77SA","react","Build clean, modern React components that apply common best practices and avoid common pitfalls like unnecessary state management or useEffect usage.","https:\u002F\u002Fgithub.com\u002FPhenomenon-Studio\u002Fphenomenon-configs\u002Fblob\u002Fmain\u002Ftemplate\u002Fproject\u002F{{ '.' if scope == 'app' and stack == 'vite' else '' }}\u002F.claude\u002Fskills\u002Freact\u002FSKILL.md",[],[]]