[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JMEX7KPATHSSZN87DPEY0N":3,"skill-same:01M6JMEX7KPATHSSZN87DPEY0N":64},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M6JMEX7KPATHSSZN87DPEY0N","commit",null,"Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.","transaurus\u002Fstaging-davila7-claude-code-templates","transaurus","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F210882017?v=4","01M6JH1R6ZCRXGJCTDP5ZKZBE6","Page Turner Agent","01M6JH1RBBR2P6Y0XWDGM4B0G7",0,"MIT","https:\u002F\u002Fgithub.com\u002Ftransaurus\u002Fstaging-davila7-claude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsentry\u002Fcommit\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"changes","writing","with","formatting","create commit","conventions","references","conventional commits","issue","use","history","commit messages","commits","messages","sentry","git","code","create","2026-11-10 10:12:30",false,"---\nname: commit\ndescription: Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.\n---\n\n# Sentry Commit Messages\n\nFollow these conventions when creating commits for Sentry projects.\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## 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\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## 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## 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\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","34fa6acf794b9a6310d298cbb8fb8c9420a5edcf","cli-tool\u002Fcomponents\u002Fskills\u002Fsentry\u002Fcommit",2,"https:\u002F\u002Fgithub.com\u002Ftransaurus\u002Fstaging-davila7-claude-code-templates","https:\u002F\u002Fgithub.com\u002Ftransaurus","Automated works of Page Turner","2026-03-28 10:12:59",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add transaurus\u002Fstaging-davila7-claude-code-templates --skill commit",{"tool":56,"command":57},"bunx","bunx skills add transaurus\u002Fstaging-davila7-claude-code-templates --skill commit",{"tool":59,"command":60},"pnpm","pnpm dlx skills add transaurus\u002Fstaging-davila7-claude-code-templates --skill commit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftransaurus\u002Fstaging-davila7-claude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsentry\u002Fcommit\u002FSKILL.md",true,[],[65,94,114,137,157,183],{"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":76,"publishedAt":37},"01M6JMRJR3BE0HGWFWDZSB853S","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002Ftransaurus\u002Fstaging-davila7-claude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fzapier-make-patterns\u002FSKILL.md",[71],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[77,78,79,80,20,81,82,35,83,84,28,85,86,87,88,89,90,91,92,93],"zapier make patterns","patterns","make","zapier","workflow","automation","integrations","business","power","complexity","platform","apps","how to","No-Code","which","for","spawner",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":37},"01M6JMR8YK6SWPCTG1MCQTMN9S","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","https:\u002F\u002Fgithub.com\u002Ftransaurus\u002Fstaging-davila7-claude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FSKILL.md",[],[96,101,102,5,103,104,105,106,107,108,109,110,28,111,112,113],"cli","github","pull request","openai","pull","push","flow","open","gh","user","only","stage","github cli",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":121,"publishedAt":37},"01M6JMQNFE64ZASQK90HARRXW8","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002Ftransaurus\u002Fstaging-davila7-claude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fworkflow-automation\u002FSKILL.md",[120],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},[81,82,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,21,92,93],"Workflow Automation","ai agents","accessibility","workflows","apache","execution","inngest","parallel","orchestrator","resume","n8n","payment","worker","scripts","temporal",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":37},"01M6JMQDYJ0XETERPHGDR3EVGN","trigger-dev","Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.","https:\u002F\u002Fgithub.com\u002Ftransaurus\u002Fstaging-davila7-claude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Ftrigger-dev\u002FSKILL.md",[],[144,145,146,147,148,125,149,126,127,150,28,151,152,153,154,155,156,21,92,93],"dev","trigger dev","trigger","design","typescript","async execution","first","async","developer experience","expert","task","background jobs","long",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":166,"publishedAt":37},"01M6JMQ5J6KK3GSX9FJCWWK6G6","planning-with-files","Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.","https:\u002F\u002Fgithub.com\u002Ftransaurus\u002Fstaging-davila7-claude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fplanning-with-files\u002FSKILL.md",[163],{"categoryNo":164,"categoryName":165,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000021","资料检索与研究",[167,168,169,21,170,81,171,172,173,174,175,176,28,177,178,179,180,181,182,92],"planning with files","planning","files","with files","storage","tasks","markdown","knowledge","projects","work","manus","structured output","progress","transforms","multi","output",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":193,"publishedAt":37},"01M6JMPWAT60RXXNEC4V9TRBRS","n8n-workflow-patterns","Proven workflow architectural patterns from real n8n workflows. Use when building new workflows, designing workflow structure, choosing workflow patterns, planning workflow architecture, or asking about webhook processing, HTTP API integration, database operations, AI agent workflows, or scheduled tasks.","https:\u002F\u002Fgithub.com\u002Ftransaurus\u002Fstaging-davila7-claude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fn8n\u002Fn8n-workflow-patterns\u002FSKILL.md",[189,192],{"categoryNo":190,"categoryName":191,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},[81,194,132,195,78,196,197,125,198,172,168,199,200,201,202,203,204,205,206,207],"n8n workflow patterns","workflow patterns","n8n workflow","ai agent","architecture","database","api","planning workflow","structure","database operations","webhook","processing","http api","scheduled"]