[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-acd11c22-a3ee-4ec4-99e6-2accfaee4f14":3,"$fiuIkJUPKq0RIN5P8KiJQGQi3p3lIOCOtnAVc6_wLY2o":43},{"id":4,"title":5,"description":6,"categoryId":7,"moduleId":8,"tags":9,"prompt":10,"icon":11,"source":12,"sourceUrl":13,"authorId":14,"authorName":15,"isPublic":16,"stars":17,"runs":18,"createdAt":19,"updatedAt":19,"module":20,"category":27,"packages":34},"acd11c22-a3ee-4ec4-99e6-2accfaee4f14","commit","始终在提交代码更改时使用此技能——绝不要在没有它的情况下直接提交。遵循Sentry约定创建具有正确常规提交格式和问题引用的提交。在任意提交、git提交、保存更改或提交消息任务时触发。","cat_life_career","mod_other","sickn33,other","---\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.\nrisk: critical\nsource: community\n---\n\n# Sentry Commit Messages\n\nFollow these conventions when creating commits for Sentry projects.\n\n## When to Use\n- The user asks to commit code, prepare a commit message, or save changes in git.\n- You need Sentry-style commit formatting with conventional commit structure and issue references.\n- The task requires enforcing branch safety before committing, especially avoiding direct commits on `main` or `master`.\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 the user whether to create a branch; just proceed with branch creation. The `create-branch` skill will still propose a branch name for the user to confirm.\n\nUse the `create-branch` skill to create the branch. After `create-branch` completes, verify the current branch has changed before proceeding:\n\n```bash\ngit branch --show-current\n```\n\nIf still on `main` or `master` (e.g., the user aborted branch creation), stop — do not commit.\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\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","","imported","https:\u002F\u002Fgithub.com\u002Fsickn33\u002Fantigravity-awesome-skills","user_system_seed","SkillOPIC",true,209,1288,"2026-05-16 13:12:19",{"id":8,"name":21,"slug":22,"icon":23,"description":24,"sort":25,"createdAt":26},"其他","other","mdi-page-next-outline","其他类型Skill",5,"2026-05-16 12:53:40",{"id":7,"name":28,"slug":29,"icon":30,"description":31,"moduleId":8,"sort":32,"skillCount":33,"createdAt":26},"职场发展","career","mdi-briefcase-outline","面试准备、简历优化、职业规划",4,575,[35],{"id":36,"skillId":4,"version":37,"fileName":38,"fileSize":39,"filePath":40,"fileHash":41,"manifest":42,"createdAt":19},"b20bf123-a6c6-4d40-8495-059ae0aea466","1.0.0","commit.zip",2364,"uploads\u002Fskills\u002Facd11c22-a3ee-4ec4-99e6-2accfaee4f14\u002Fcommit.zip","d49e49d8216e6829882a314ad5d6d96a67d99ce98338729175f9cb79e207ba06","[{\"path\":\"SKILL.md\",\"isDirectory\":false,\"size\":4830}]",{"code":44,"message":45,"data":46},200,"success",{"items":47,"stats":48,"page":51},[],{"averageRating":49,"totalRatings":49,"ratingCounts":50},0,[49,49,49,49,49],{"limit":52,"offset":49,"hasMore":53,"nextOffset":52,"ratedOnly":16},15,false]