[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M791VD8N8ZBPB2V90THSC9KM":3,"skill-same:01M791VD8N8ZBPB2V90THSC9KM":53},{"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":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M791VD8N8ZBPB2V90THSC9KM","conventional-commit",null,"Create git commits using Conventional Commits. Use when the user asks to commit code, prepare a commit, write a commit message, or standardize commit history with conventional commit types, scopes, breaking-change markers, and safe git workflow checks.","endalk200\u002Fartiflow","endalk200","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F44495881?v=4","01M6BYRJ2PAY7EXZ7DJF5VZ7DB","Endalkachew Biruk","01M791V154K6ZZGYPMJTA8FZ8Y",2,"MIT","https:\u002F\u002Fgithub.com\u002Fendalk200\u002Fartiflow\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconventional-commit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: conventional-commit\ndescription: Create git commits using Conventional Commits. Use when the user asks to commit code, prepare a commit, write a commit message, or standardize commit history with conventional commit types, scopes, breaking-change markers, and safe git workflow checks.\n---\n\n# Conventional Commit\n\nCreate focused git commits using the Conventional Commits format.\n\n## Commit Format\n\nUse this structure:\n\n```text\n\u003Ctype>[optional scope][!]: \u003Cdescription>\n\n[optional body]\n\n[optional footer(s)]\n```\n\nExamples:\n\n```text\nfeat(auth): add password reset flow\nfix(api): handle expired session tokens\ndocs: clarify deployment steps\nrefactor!: remove legacy payment adapter\n```\n\n## Types\n\nPrefer these types:\n\n- `feat`: a new user-facing or externally observable capability\n- `fix`: a bug fix\n- `docs`: documentation-only changes\n- `style`: formatting or style-only changes that do not affect behavior\n- `refactor`: code restructuring that neither fixes a bug nor adds a feature\n- `perf`: performance improvement\n- `test`: adding or updating tests only\n- `build`: build system, packaging, or dependency changes\n- `ci`: CI configuration or workflow changes\n- `chore`: maintenance work that does not fit another type\n- `revert`: revert a previous commit\n\nUse the most specific accurate type. Do not use `feat` unless the change adds a new capability. Do not use `fix` unless it corrects broken behavior.\n\n## Scope\n\nAdd a scope when it improves clarity:\n\n- Use a package, app, module, route, domain, or subsystem name.\n- Keep scope lowercase and short, such as `api`, `auth`, `ui`, `deps`, `billing`.\n- Omit scope if the change is broad or no concise scope is obvious.\n\n## Description\n\nWrite the description in imperative mood, lowercase unless a proper noun requires capitalization.\n\n- Good: `fix(auth): reject expired tokens`\n- Good: `docs: add local setup notes`\n- Avoid: `fixed auth token issue`\n- Avoid: `updates stuff`\n\nKeep the subject line concise, ideally 72 characters or less.\n\n## Breaking Changes\n\nMark breaking changes with `!` after the type or scope and include a footer:\n\n```text\nfeat(api)!: require project id for exports\n\nBREAKING CHANGE: Export requests must now include a project id.\n```\n\nOnly mark a breaking change when existing consumers, persisted data, public APIs, commands, configuration, or documented behavior require migration.\n\n## Safe Workflow\n\nBefore committing:\n\n1. Run `git status --short` to inspect modified, staged, and untracked files.\n2. Run `git diff` and `git diff --staged` to understand unstaged and staged changes.\n3. Run `git log --oneline -n 10` to learn the repository's existing commit style.\n4. Identify which changes belong in this commit. Do not stage unrelated user changes.\n5. Do not commit secrets, credentials, local environment files, generated artifacts, or unrelated formatting churn.\n6. If there are suspicious files such as `.env`, private keys, tokens, or credential JSON files, stop and ask before committing them.\n\nWhen staging:\n\n- Stage only files directly related to the requested commit.\n- Preserve unrelated worktree changes.\n- Prefer explicit paths with `git add \u003Cpath>`.\n- Avoid broad staging with `git add .` unless all changes have been reviewed and clearly belong together.\n\nWhen committing:\n\n- Decide whether the commit needs a body by applying the Commit Body criteria below.\n- Use `git commit -m \"\u003Cconventional subject>\"` when the subject fully communicates the change and its rationale is self-evident.\n- Use multiple `-m` flags when adding a body or footer.\n- Do not bypass hooks with `--no-verify` unless the user explicitly asks.\n- Do not amend unless the user explicitly asks.\n- Do not push unless the user explicitly asks.\n\nAfter committing:\n\n1. Run `git status --short` to verify the commit succeeded and confirm any remaining changes are intentional.\n2. Report the commit hash and message.\n3. Mention any uncommitted changes left behind.\n\n## Message Selection\n\nChoose the message from the actual diff, not from the user's phrasing alone.\n\nUse this decision process:\n\n1. If the diff is documentation only, use `docs`.\n2. If the diff is tests only, use `test`.\n3. If the diff changes build tooling, package metadata, lockfiles, or dependencies, use `build` unless it is purely CI.\n4. If the diff changes CI files or automation workflows, use `ci`.\n5. If the diff fixes incorrect behavior, use `fix`.\n6. If the diff adds a new capability, use `feat`.\n7. If the diff restructures code without behavior change, use `refactor`.\n8. If the diff improves runtime performance, use `perf`.\n9. If none apply and the work is maintenance, use `chore`.\n\nIf multiple unrelated changes are present, ask whether to split them into separate commits unless the user already specified grouping.\n\n## Commit Body (Optional)\n\nA commit body explains the reasoning or context behind the change. Consider one for every commit, but include it only when it adds durable information beyond the subject and diff.\n\nUse a body when it helps a future reader understand one or more of:\n\n- why the change was needed\n- why this approach was chosen over an obvious alternative\n- constraints, assumptions, or tradeoffs that shaped the implementation\n- non-obvious behavior changes, side effects, or migration context\n\nWrite the body as concise prose focused on cause and intent. A body is unnecessary when the rationale is self-evident from the subject and diff.\n\nExample:\n\n```text\nfix(cache): avoid stale project permissions\n\nRole updates were leaving cached permissions valid until their TTL expired. Include the role version in the cache key so permission changes take effect immediately without requiring broad cache invalidation.\n```\n\n## Footers\n\nUse footers for metadata such as issues, breaking changes, or co-authors:\n\n```text\nCloses #123\nRefs #456\nBREAKING CHANGE: The config file now uses `projectId` instead of `id`.\n```\n\n## Output Style\n\nWhen done, respond briefly:\n\n```text\nCommitted `\u003Chash>` with `type(scope): description`.\n```\n\nIf no commit was created, explain why and list the blocker.\n","# Conventional Commit\n\nCreate focused git commits using the Conventional Commits format.\n\n## Commit Format\n\nUse this structure:\n\n```text\n\u003Ctype>[optional scope][!]: \u003Cdescription>\n\n[optional body]\n\n[optional footer(s)]\n```\n\nExamples:\n\n```text\nfeat(auth): add password reset flow\nfix(api): handle expired session tokens\ndocs: clarify deployment steps\nrefactor!: remove legacy payment adapter\n```\n\n## Types\n\nPrefer these types:\n\n- `feat`: a new user-facing or externally observable capability\n- `fix`: a bug fix\n- `docs`: documentation-only changes\n- `style`: formatting or style-only changes that do not affect behavior\n- `refactor`: code restructuring that neither fixes a bug nor adds a feature\n- `perf`: performance improvement\n- `test`: adding or updating tests only\n- `build`: build system, packaging, or dependency changes\n- `ci`: CI configuration or workflow changes\n- `chore`: maintenance work that does not fit another type\n- `revert`: revert a previous commit\n\nUse the most specific accurate type. Do not use `feat` unless the change adds a new capability. Do not use `fix` unless it corrects broken behavior.\n\n## Scope\n\nAdd a scope when it improves clarity:\n\n- Use a package, app, module, route, domain, or subsystem name.\n- Keep scope lowercase and short, such as `api`, `auth`, `ui`, `deps`, `billing`.\n- Omit scope if the change is broad or no concise scope is obvious.\n\n## Description\n\nWrite the description in imperative mood, lowercase unless a proper noun requires capitalization.\n\n- Good: `fix(auth): reject expired tokens`\n- Good: `docs: add local setup notes`\n- Avoid: `fixed auth token issue`\n- Avoid: `updates stuff`\n\nKeep the subject line concise, ideally 72 characters or less.\n\n## Breaking Changes\n\nMark breaking changes with `!` after the type or scope and include a footer:\n\n```text\nfeat(api)!: require project id for exports\n\nBREAKING CHANGE: Export requests must now include a project id.\n```\n\nOnly mark a breaking change when existing consumers, persisted data, public APIs, commands, configuration, or documented behavior require migration.\n\n## Safe Workflow\n\nBefore committing:\n\n1. Run `git status --short` to inspect modified, staged, and untracked files.\n2. Run `git diff` and `git diff --staged` to understand unstaged and staged changes.\n3. Run `git log --oneline -n 10` to learn the repository's existing commit style.\n4. Identify which changes belong in this commit. Do not stage unrelated user changes.\n5. Do not commit secrets, credentials, local environment files, generated artifacts, or unrelated formatting churn.\n6. If there are suspicious files such as `.env`, private keys, tokens, or credential JSON files, stop and ask before committing them.\n\nWhen staging:\n\n- Stage only files directly related to the requested commit.\n- Preserve unrelated worktree changes.\n- Prefer explicit paths with `git add \u003Cpath>`.\n- Avoid broad staging with `git add .` unless all changes have been reviewed and clearly belong together.\n\nWhen committing:\n\n- Decide whether the commit needs a body by applying the Commit Body criteria below.\n- Use `git commit -m \"\u003Cconventional subject>\"` when the subject fully communicates the change and its rationale is self-evident.\n- Use multiple `-m` flags when adding a body or footer.\n- Do not bypass hooks with `--no-verify` unless the user explicitly asks.\n- Do not amend unless the user explicitly asks.\n- Do not push unless the user explicitly asks.\n\nAfter committing:\n\n1. Run `git status --short` to verify the commit succeeded and confirm any remaining changes are intentional.\n2. Report the commit hash and message.\n3. Mention any uncommitted changes left behind.\n\n## Message Selection\n\nChoose the message from the actual diff, not from the user's phrasing alone.\n\nUse this decision process:\n\n1. If the diff is documentation only, use `docs`.\n2. If the diff is tests only, use `test`.\n3. If the diff changes build tooling, package metadata, lockfiles, or dependencies, use `build` unless it is purely CI.\n4. If the diff changes CI files or automation workflows, use `ci`.\n5. If the diff fixes incorrect behavior, use `fix`.\n6. If the diff adds a new capability, use `feat`.\n7. If the diff restructures code without behavior change, use `refactor`.\n8. If the diff improves runtime performance, use `perf`.\n9. If none apply and the work is maintenance, use `chore`.\n\nIf multiple unrelated changes are present, ask whether to split them into separate commits unless the user already specified grouping.\n\n## Commit Body (Optional)\n\nA commit body explains the reasoning or context behind the change. Consider one for every commit, but include it only when it adds durable information beyond the subject and diff.\n\nUse a body when it helps a future reader understand one or more of:\n\n- why the change was needed\n- why this approach was chosen over an obvious alternative\n- constraints, assumptions, or tradeoffs that shaped the implementation\n- non-obvious behavior changes, side effects, or migration context\n\nWrite the body as concise prose focused on cause and intent. A body is unnecessary when the rationale is self-evident from the subject and diff.\n\nExample:\n\n```text\nfix(cache): avoid stale project permissions\n\nRole updates were leaving cached permissions valid until their TTL expired. Include the role version in the cache key so permission changes take effect immediately without requiring broad cache invalidation.\n```\n\n## Footers\n\nUse footers for metadata such as issues, breaking changes, or co-authors:\n\n```text\nCloses #123\nRefs #456\nBREAKING CHANGE: The config file now uses `projectId` instead of `id`.\n```\n\n## Output Style\n\nWhen done, respond briefly:\n\n```text\nCommitted `\u003Chash>` with `type(scope): description`.\n```\n\nIf no commit was created, explain why and list the blocker.\n",{"name":5,"description":7},"main","c05ef3c037b0f9c253f339c951b487b9118ad69b",".agents\u002Fskills\u002Fconventional-commit",0,"https:\u002F\u002Fgithub.com\u002Fendalk200\u002Fartiflow","https:\u002F\u002Fgithub.com\u002Fendalk200","endalk200.com","Senior Software Engineer & Technical Lead","2026-11-03 15:10:49",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add endalk200\u002Fartiflow --skill conventional-commit",{"tool":39,"command":40},"bunx","bunx skills add endalk200\u002Fartiflow --skill conventional-commit",{"tool":42,"command":43},"pnpm","pnpm dlx skills add endalk200\u002Fartiflow --skill conventional-commit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fendalk200\u002Fartiflow\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconventional-commit\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",105,"https:\u002F\u002Fgithub.com\u002Fendalk200\u002Fartiflow\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fconventional-commit\u002Fagents\u002Fopenai.yaml",[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M791YFNVRKXWX13VFE5KJ54S","artiflow","Publish a polished visual Artifact for the current plan, report, review, or explanation.","https:\u002F\u002Fgithub.com\u002Fendalk200\u002Fartiflow\u002Fblob\u002Fmain\u002Fskills\u002Fartiflow\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M791YDNX6GBGJJS7QHTN767T","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fendalk200\u002Fartiflow\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M791YARDC91FEWW5R8NH6QBT","wayfinder","Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Fendalk200\u002Fartiflow\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M791Y98HBXMVR6F9T9DF3M1E","wait-what","Stop. That last message did not land — re-pitch it.","https:\u002F\u002Fgithub.com\u002Fendalk200\u002Fartiflow\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwait-what\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M791Y0DNPW30WKXJ0N3YH0MN","turborepo","Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines,\ndependsOn, caching, remote cache, the \"turbo\" CLI, --filter, --affected, CI optimization, environment\nvariables, internal packages, monorepo structure\u002Fbest practices, and boundaries.\n\nUse when user: configures tasks\u002Fworkflows\u002Fpipelines, creates packages, sets up\nmonorepo, shares code between apps, runs changed\u002Faffected packages, debugs cache,\nor has apps\u002Fpackages directories.","https:\u002F\u002Fgithub.com\u002Fendalk200\u002Fartiflow\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fturborepo\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M791XVV64WSJWC5JQSQ4F34Q","triage","Move issues and external pull requests through triage roles — categorise, verify, grill if needed, and write agent-ready briefs.","https:\u002F\u002Fgithub.com\u002Fendalk200\u002Fartiflow\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftriage\u002FSKILL.md",[],[]]