[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C5PRVTER1N67VRB7G04T8A":3,"skill-same:01M6C5PRVTER1N67VRB7G04T8A":56},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":14,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":6,"updatedAt":41,"install":42,"resources":55},"01M6C5PRVTER1N67VRB7G04T8A","commit",null,"ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional commit format and issue references. Trigger on any commit, git commit, save changes, or commit message task.","CoralShades\u002Facm-ai","CoralShades","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F220297585?v=4","01M6C5211QSJHZ8HXSDDWCR507","Coral Shades AI Agency","01M6C52161FNQDRQ0FRR8DAA9D",0,"MIT","https:\u002F\u002Fgithub.com\u002FCoralShades\u002Facm-ai\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fcommit\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29],"git commit","code","git","commit message","sentry","conventional commit","save","commits","format","use","never","2026-11-10 10:12:30",false,"---\nname: commit\ndescription: ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional commit format and issue references. Trigger on any commit, git commit, save changes, or commit message task.\n---\n\n# Sentry Commit Messages\n\nFollow these conventions when creating commits for Sentry projects.\n\n## Prerequisites\n\nBefore committing, always check the current branch:\n\n```bash\ngit branch --show-current\n```\n\n**If you're on `main` or `master`, you MUST create a feature branch first** — unless the user explicitly asked to commit to main. Do not ask for confirmation; default to creating the branch.\n\n```bash\n# Create and switch to a new branch\ngit checkout -b \u003Ctype>\u002F\u003Cshort-description>\n```\n\nBranch naming should follow the pattern: `\u003Ctype>\u002F\u003Cshort-description>` where type matches the commit type (e.g., `feat\u002Fadd-user-auth`, `fix\u002Fnull-pointer-error`, `ref\u002Fextract-validation`).\n\n## Format\n\n```\n\u003Ctype>(\u003Cscope>): \u003Csubject>\n\n\u003Cbody>\n\n\u003Cfooter>\n```\n\nThe header is required. Scope is optional. All lines must stay under 100 characters.\n\n## Commit Types\n\n| Type | Purpose |\n|------|---------|\n| `feat` | New feature |\n| `fix` | Bug fix |\n| `ref` | Refactoring (no behavior change) |\n| `perf` | Performance improvement |\n| `docs` | Documentation only |\n| `test` | Test additions or corrections |\n| `build` | Build system or dependencies |\n| `ci` | CI configuration |\n| `chore` | Maintenance tasks |\n| `style` | Code formatting (no logic change) |\n| `meta` | Repository metadata |\n| `license` | License changes |\n\n## Subject Line Rules\n\n- Use imperative, present tense: \"Add feature\" not \"Added feature\"\n- Capitalize the first letter\n- No period at the end\n- Maximum 70 characters\n\n## Body Guidelines\n\n- Explain **what** and **why**, not how\n- Use imperative mood and present tense\n- Include motivation for the change\n- Contrast with previous behavior when relevant\n\n## Footer: Issue References\n\nReference issues in the footer using these patterns:\n\n```\nFixes GH-1234\nFixes #1234\nFixes SENTRY-1234\nRefs LINEAR-ABC-123\n```\n\n- `Fixes` closes the issue when merged\n- `Refs` links without closing\n\n## AI-Generated Changes\n\nWhen changes were primarily generated by a coding agent (like Claude Code), include the Co-Authored-By attribution in the commit footer:\n\n```\nCo-Authored-By: Claude \u003Cnoreply@anthropic.com>\n```\n\nThis is the only indicator of AI involvement that should appear in commits. Do not add phrases like \"Generated by AI\", \"Written with Claude\", or similar markers in the subject, body, or anywhere else in the commit message.\n\n## Examples\n\n### Simple fix\n\n```\nfix(api): Handle null response in user endpoint\n\nThe user API could return null for deleted accounts, causing a crash\nin the dashboard. Add null check before accessing user properties.\n\nFixes SENTRY-5678\nCo-Authored-By: Claude \u003Cnoreply@anthropic.com>\n```\n\n### Feature with scope\n\n```\nfeat(alerts): Add Slack thread replies for alert updates\n\nWhen an alert is updated or resolved, post a reply to the original\nSlack thread instead of creating a new message. This keeps related\nnotifications grouped together.\n\nRefs GH-1234\n```\n\n### Refactor\n\n```\nref: Extract common validation logic to shared module\n\nMove duplicate validation code from three endpoints into a shared\nvalidator class. No behavior change.\n```\n\n### Breaking change\n\n```\nfeat(api)!: Remove deprecated v1 endpoints\n\nRemove all v1 API endpoints that were deprecated in version 23.1.\nClients should migrate to v2 endpoints.\n\nBREAKING CHANGE: v1 endpoints no longer available\nFixes SENTRY-9999\n```\n\n## Revert Format\n\n```\nrevert: feat(api): Add new endpoint\n\nThis reverts commit abc123def456.\n\nReason: Caused performance regression in production.\n```\n\n## Principles\n\n- Each commit should be a single, stable change\n- Commits should be independently reviewable\n- The repository should be in a working state after each commit\n\n## References\n\n- [Sentry Commit Messages](https:\u002F\u002Fdevelop.sentry.dev\u002Fengineering-practices\u002Fcommit-messages\u002F)\n","# Sentry Commit Messages\n\nFollow these conventions when creating commits for Sentry projects.\n\n## Prerequisites\n\nBefore committing, always check the current branch:\n\n```bash\ngit branch --show-current\n```\n\n**If you're on `main` or `master`, you MUST create a feature branch first** — unless the user explicitly asked to commit to main. Do not ask for confirmation; default to creating the branch.\n\n```bash\n# Create and switch to a new branch\ngit checkout -b \u003Ctype>\u002F\u003Cshort-description>\n```\n\nBranch naming should follow the pattern: `\u003Ctype>\u002F\u003Cshort-description>` where type matches the commit type (e.g., `feat\u002Fadd-user-auth`, `fix\u002Fnull-pointer-error`, `ref\u002Fextract-validation`).\n\n## Format\n\n```\n\u003Ctype>(\u003Cscope>): \u003Csubject>\n\n\u003Cbody>\n\n\u003Cfooter>\n```\n\nThe header is required. Scope is optional. All lines must stay under 100 characters.\n\n## Commit Types\n\n| Type | Purpose |\n|------|---------|\n| `feat` | New feature |\n| `fix` | Bug fix |\n| `ref` | Refactoring (no behavior change) |\n| `perf` | Performance improvement |\n| `docs` | Documentation only |\n| `test` | Test additions or corrections |\n| `build` | Build system or dependencies |\n| `ci` | CI configuration |\n| `chore` | Maintenance tasks |\n| `style` | Code formatting (no logic change) |\n| `meta` | Repository metadata |\n| `license` | License changes |\n\n## Subject Line Rules\n\n- Use imperative, present tense: \"Add feature\" not \"Added feature\"\n- Capitalize the first letter\n- No period at the end\n- Maximum 70 characters\n\n## Body Guidelines\n\n- Explain **what** and **why**, not how\n- Use imperative mood and present tense\n- Include motivation for the change\n- Contrast with previous behavior when relevant\n\n## Footer: Issue References\n\nReference issues in the footer using these patterns:\n\n```\nFixes GH-1234\nFixes #1234\nFixes SENTRY-1234\nRefs LINEAR-ABC-123\n```\n\n- `Fixes` closes the issue when merged\n- `Refs` links without closing\n\n## AI-Generated Changes\n\nWhen changes were primarily generated by a coding agent (like Claude Code), include the Co-Authored-By attribution in the commit footer:\n\n```\nCo-Authored-By: Claude \u003Cnoreply@anthropic.com>\n```\n\nThis is the only indicator of AI involvement that should appear in commits. Do not add phrases like \"Generated by AI\", \"Written with Claude\", or similar markers in the subject, body, or anywhere else in the commit message.\n\n## Examples\n\n### Simple fix\n\n```\nfix(api): Handle null response in user endpoint\n\nThe user API could return null for deleted accounts, causing a crash\nin the dashboard. Add null check before accessing user properties.\n\nFixes SENTRY-5678\nCo-Authored-By: Claude \u003Cnoreply@anthropic.com>\n```\n\n### Feature with scope\n\n```\nfeat(alerts): Add Slack thread replies for alert updates\n\nWhen an alert is updated or resolved, post a reply to the original\nSlack thread instead of creating a new message. This keeps related\nnotifications grouped together.\n\nRefs GH-1234\n```\n\n### Refactor\n\n```\nref: Extract common validation logic to shared module\n\nMove duplicate validation code from three endpoints into a shared\nvalidator class. No behavior change.\n```\n\n### Breaking change\n\n```\nfeat(api)!: Remove deprecated v1 endpoints\n\nRemove all v1 API endpoints that were deprecated in version 23.1.\nClients should migrate to v2 endpoints.\n\nBREAKING CHANGE: v1 endpoints no longer available\nFixes SENTRY-9999\n```\n\n## Revert Format\n\n```\nrevert: feat(api): Add new endpoint\n\nThis reverts commit abc123def456.\n\nReason: Caused performance regression in production.\n```\n\n## Principles\n\n- Each commit should be a single, stable change\n- Commits should be independently reviewable\n- The repository should be in a working state after each commit\n\n## References\n\n- [Sentry Commit Messages](https:\u002F\u002Fdevelop.sentry.dev\u002Fengineering-practices\u002Fcommit-messages\u002F)\n",{"name":5,"description":7},"main","1ca81b0a7de199942400f965edd4d7544077ac5d",".codex\u002Fskills\u002Fcommit","https:\u002F\u002Fgithub.com\u002FCoralShades\u002Facm-ai","https:\u002F\u002Fgithub.com\u002FCoralShades","coralshades.com.au","2026-04-18 00:45:07",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add CoralShades\u002Facm-ai --skill commit",{"tool":48,"command":49},"bunx","bunx skills add CoralShades\u002Facm-ai --skill commit",{"tool":51,"command":52},"pnpm","pnpm dlx skills add CoralShades\u002Facm-ai --skill commit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCoralShades\u002Facm-ai\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fcommit\u002FSKILL.md",true,[],[57,79,92,108,130,140],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":68,"publishedAt":30},"01M6C63HKXA890HHV47WBAX0TB","uncodixfy","Prevents generic AI\u002FCodex UI patterns when generating frontend code. Use this skill whenever generating HTML, CSS, React, Vue, Svelte, or any frontend UI code to enforce clean, human-designed aesthetics inspired by Linear, Raycast, Stripe, and GitHub instead of typical AI-generated UI.","https:\u002F\u002Fgithub.com\u002FCoralShades\u002Facm-ai\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Funcodixfy\u002FSKILL.md",[63],{"categoryNo":64,"categoryName":65,"taxonomyType":66,"taxonomyTypeDesc":67},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[59,69,70,71,72,73,20,74,75,76,77,28,78],"github","frontend","css","codex","react","linear","ui","vue","generated","html",{"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":83,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":30},"01M6C63FJ2GEBBGZ5XSMV40KXB","runpodctl","Runpod CLI to manage your GPU workloads.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FCoralShades\u002Facm-ai\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Frunpodctl\u002FSKILL.md",[],[81,87,88,89,90,91],"macos","cli","linux","gpu","Bash",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":30},"01M6C63DPAV46TFVQ01SFYPJ7X","langgraph-persistence","INVOKE THIS SKILL when your LangGraph needs to persist state, remember conversations, travel through history, or configure subgraph checkpointer scoping. Covers checkpointers, thread_id, time travel, Store, and subgraph persistence modes.","https:\u002F\u002Fgithub.com\u002FCoralShades\u002Facm-ai\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Flanggraph-persistence\u002FSKILL.md",[],[99,100,101,102,103,104,105,106,107],"langgraph persistence","langgraph","persistence","travel","history","scoping","remember","state","configure",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":119,"publishedAt":30},"01M6C63BNS9CQEBTB8RNSSBFPA","langgraph-human-in-the-loop","INVOKE THIS SKILL when implementing human-in-the-loop patterns, pausing for approval, or handling errors in LangGraph. Covers interrupt(), Command(resume=...), approval\u002Fvalidation workflows, and the 4-tier error handling strategy.","https:\u002F\u002Fgithub.com\u002FCoralShades\u002Facm-ai\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Flanggraph-human-in-the-loop\u002FSKILL.md",[114],{"categoryNo":115,"categoryName":116,"taxonomyType":117,"taxonomyTypeDesc":118},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[120,121,100,122,123,124,125,126,127,128,129],"langgraph human in the loop","loop","workflows","error handling","validation","human-in-the-loop","command","strategy","approval","resume",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":30},"01M6C639GVYZFX3NFPV5FBDR4F","langgraph-fundamentals","INVOKE THIS SKILL when writing ANY LangGraph code. Covers StateGraph, state schemas, nodes, edges, Command, Send, invoke, streaming, and error handling.","https:\u002F\u002Fgithub.com\u002FCoralShades\u002Facm-ai\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Flanggraph-fundamentals\u002FSKILL.md",[],[137,100,123,106,138,139,126,20],"langgraph fundamentals","streaming","writing",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":30},"01M6C6375N34YX2GZ3SD3R7XR2","langchain-rag","INVOKE THIS SKILL when building ANY retrieval-augmented generation (RAG) system. Covers document loaders, RecursiveCharacterTextSplitter, embeddings (OpenAI), and vector stores (Chroma, FAISS, Pinecone).","https:\u002F\u002Fgithub.com\u002FCoralShades\u002Facm-ai\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Flangchain-rag\u002FSKILL.md",[],[147,148,149,150,151,152,153,154,155,156],"rag","langchain rag","langchain","embeddings","vector","openai","chroma","faiss","vector stores","system"]