[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D6CZ1VMB0EAT1PEFJHATTS":3,"skill-same:01M7D6CZ1VMB0EAT1PEFJHATTS":66},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":25,"commitSha":26,"skillDirectory":5,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7D6CZ1VMB0EAT1PEFJHATTS","commit-work",null,"Create high-quality git commits: review\u002Fstage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.","tangyixiao\u002Ftangyixiao-skills","tangyixiao","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F115929632?v=4","01M7D582YK6A4M63CAK4CSY4EW","Tang Yixiao","01M7D582Z64DMRSYR872SR34SA",2,"MIT","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fcommit-work\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fcommit-work\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: commit-work\ndescription: \"Create high-quality git commits: review\u002Fstage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.\"\n---\n\n# Commit work\n\n## Goal\nMake commits that are easy to review and safe to ship:\n- only intended changes are included\n- commits are logically scoped (split when needed)\n- commit messages describe what changed and why\n\n## Inputs to ask for (if missing)\n- Single commit or multiple commits? (If unsure: default to multiple small commits when there are unrelated changes.)\n- Commit style: Conventional Commits are required.\n- Any rules: max subject length, required scopes.\n\n## Workflow (checklist)\n1) Inspect the working tree before staging\n   - `git status`\n   - `git diff` (unstaged)\n   - If many changes: `git diff --stat`\n2) Decide commit boundaries (split if needed)\n   - Split by: feature vs refactor, backend vs frontend, formatting vs logic, tests vs prod code, dependency bumps vs behavior changes.\n   - If changes are mixed in one file, plan to use patch staging.\n3) Stage only what belongs in the next commit\n   - Prefer patch staging for mixed changes: `git add -p`\n   - To unstage a hunk\u002Ffile: `git restore --staged -p` or `git restore --staged \u003Cpath>`\n4) Review what will actually be committed\n   - `git diff --cached`\n   - Sanity checks:\n     - no secrets or tokens\n     - no accidental debug logging\n     - no unrelated formatting churn\n5) Describe the staged change in 1-2 sentences (before writing the message)\n   - \"What changed?\" + \"Why?\"\n   - If you cannot describe it cleanly, the commit is probably too big or mixed; go back to step 2.\n6) Write the commit message\n   - Use Conventional Commits (required):\n     - `type(scope): short summary`\n     - blank line\n     - body (what\u002Fwhy, not implementation diary)\n     - footer (BREAKING CHANGE) if needed\n   - Prefer an editor for multi-line messages: `git commit -v`\n   - Use `references\u002Fcommit-message-template.md` if helpful.\n7) Run the smallest relevant verification\n   - Run the repo's fastest meaningful check (unit tests, lint, or build) before moving on.\n8) Repeat for the next commit until the working tree is clean\n\n## Deliverable\nProvide:\n- the final commit message(s)\n- a short summary per commit (what\u002Fwhy)\n- the commands used to stage\u002Freview (at minimum: `git diff --cached`, plus any tests run)\n","# Commit work\n\n## Goal\nMake commits that are easy to review and safe to ship:\n- only intended changes are included\n- commits are logically scoped (split when needed)\n- commit messages describe what changed and why\n\n## Inputs to ask for (if missing)\n- Single commit or multiple commits? (If unsure: default to multiple small commits when there are unrelated changes.)\n- Commit style: Conventional Commits are required.\n- Any rules: max subject length, required scopes.\n\n## Workflow (checklist)\n1) Inspect the working tree before staging\n   - `git status`\n   - `git diff` (unstaged)\n   - If many changes: `git diff --stat`\n2) Decide commit boundaries (split if needed)\n   - Split by: feature vs refactor, backend vs frontend, formatting vs logic, tests vs prod code, dependency bumps vs behavior changes.\n   - If changes are mixed in one file, plan to use patch staging.\n3) Stage only what belongs in the next commit\n   - Prefer patch staging for mixed changes: `git add -p`\n   - To unstage a hunk\u002Ffile: `git restore --staged -p` or `git restore --staged \u003Cpath>`\n4) Review what will actually be committed\n   - `git diff --cached`\n   - Sanity checks:\n     - no secrets or tokens\n     - no accidental debug logging\n     - no unrelated formatting churn\n5) Describe the staged change in 1-2 sentences (before writing the message)\n   - \"What changed?\" + \"Why?\"\n   - If you cannot describe it cleanly, the commit is probably too big or mixed; go back to step 2.\n6) Write the commit message\n   - Use Conventional Commits (required):\n     - `type(scope): short summary`\n     - blank line\n     - body (what\u002Fwhy, not implementation diary)\n     - footer (BREAKING CHANGE) if needed\n   - Prefer an editor for multi-line messages: `git commit -v`\n   - Use `references\u002Fcommit-message-template.md` if helpful.\n7) Run the smallest relevant verification\n   - Run the repo's fastest meaningful check (unit tests, lint, or build) before moving on.\n8) Repeat for the next commit until the working tree is clean\n\n## Deliverable\nProvide:\n- the final commit message(s)\n- a short summary per commit (what\u002Fwhy)\n- the commands used to stage\u002Freview (at minimum: `git diff --cached`, plus any tests run)\n",{"name":5,"description":7},"main","2a870f189175a48c39f5f7e26a6d93b0be9cd13b",0,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills","https:\u002F\u002Ftangyixiao.github.io\u002Ftangyixiao-skills\u002F","https:\u002F\u002Fgithub.com\u002Ftangyixiao","http:\u002F\u002Fwww.sxyz.net\u002F","I am Tang Yixiao, a student in Shaoxing No.1 High School. I am eager to learn on GitHub and contribute my part to this community.","2026-11-11 15:45:59",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add tangyixiao\u002Ftangyixiao-skills --skill commit-work",{"tool":40,"command":41},"bunx","bunx skills add tangyixiao\u002Ftangyixiao-skills --skill commit-work",{"tool":43,"command":44},"pnpm","pnpm dlx skills add tangyixiao\u002Ftangyixiao-skills --skill commit-work","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fcommit-work\u002FSKILL.md",true,[48,54,58,62],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"INSTALL-SOURCE.json","REFERENCE","参考文档",218,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fcommit-work\u002FINSTALL-SOURCE.json",{"path":55,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":16},"LICENSE","许可证",1072,{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"README.md",4921,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fcommit-work\u002FREADME.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fcommit-message-template.md",347,"https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fcommit-work\u002Freferences\u002Fcommit-message-template.md",[67,76,84,92,100,108],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":72,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":20},"01M7D8JK8FYBFNNAJXWD89CFH7","xlsx","Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like \"the xlsx in my downloads\") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fxlsx\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fxlsx\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":20},"01M7D8JG8ERGGQQAMX0DWCG9GR","writing-shape","Writing, exploit: shape raw material into an article, paragraph by paragraph.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-shape\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-shape\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":20},"01M7D8JE672GW3EHSE8EF185M4","writing-fragments","Writing, explore: mine raw fragments, no structure yet.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-fragments\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-fragments\u002FSKILL.md",[],[],{"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":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":20},"01M7D8JBK572YDFMND8Q6CEYJW","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-for-agents\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":104,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":20},"01M7D8J5QPWEXX61EGBKYH73R8","writing-clearly-and-concisely","Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-clearly-and-concisely\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-clearly-and-concisely\u002FSKILL.md",[],[],{"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":112,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":20},"01M7D8J36YWC8WZS5DK5AH03CD","writing-beats","Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-beats\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Ftangyixiao\u002Ftangyixiao-skills\u002Fblob\u002Fmain\u002Fwriting-beats\u002FSKILL.md",[],[]]