[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72TH9X5WA6P2NACHX7YRRRT":3,"skill-same:01M72TH9X5WA6P2NACHX7YRRRT":46},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M72TH9X5WA6P2NACHX7YRRRT","resolving-merge-conflicts",null,"Use when you need to resolve an in-progress git merge\u002Frebase conflict.","Mekann2904\u002Fmekann","Mekann2904","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F149444390?v=4","01M72TBR4X3TE5S6305ZXYHZYH","Mekann","01M72TBR5E4BWYB1VBWHTHEG5T",0,"MIT","https:\u002F\u002Fgithub.com\u002FMekann2904\u002Fmekann\u002Fblob\u002Fmain\u002Fmekann\u002Fskills\u002Fresolving-merge-conflicts\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: resolving-merge-conflicts\ndescription: \"Use when you need to resolve an in-progress git merge\u002Frebase conflict.\"\n---\n\n1. **See the current state** of the merge\u002Frebase. Check git history, and the conflicting files.\n\n2. **Find the primary sources** for each conflict. Understand deeply why each change was made, and what the original intent was. Read the commit messages, check the PRs, check original issues\u002Ftickets.\n\n3. **Resolve each hunk.** Preserve both intents where possible. Where incompatible, pick the one matching the merge's stated goal and note the trade-off. Do **not** invent new behaviour. Always resolve; never `--abort`.\n\n4. Discover the project's **automated checks** and run them — typically typecheck, then tests, then format. Fix anything the merge broke.\n\n5. **Finish the merge\u002Frebase.** Stage everything and commit. If rebasing, continue the rebase process until all commits are rebased.\n","1. **See the current state** of the merge\u002Frebase. Check git history, and the conflicting files.\n\n2. **Find the primary sources** for each conflict. Understand deeply why each change was made, and what the original intent was. Read the commit messages, check the PRs, check original issues\u002Ftickets.\n\n3. **Resolve each hunk.** Preserve both intents where possible. Where incompatible, pick the one matching the merge's stated goal and note the trade-off. Do **not** invent new behaviour. Always resolve; never `--abort`.\n\n4. Discover the project's **automated checks** and run them — typically typecheck, then tests, then format. Fix anything the merge broke.\n\n5. **Finish the merge\u002Frebase.** Stage everything and commit. If rebasing, continue the rebase process until all commits are rebased.\n",{"name":5,"description":7},"main","ffd7ea99bf2436d312931261a5616ba93f865f62","mekann\u002Fskills\u002Fresolving-merge-conflicts","https:\u002F\u002Fgithub.com\u002FMekann2904\u002Fmekann","https:\u002F\u002Fgithub.com\u002FMekann2904","https:\u002F\u002Fblog.mekann.workers.dev","琉大 y23 ","2026-08-07 01:44:53",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Mekann2904\u002Fmekann --skill resolving-merge-conflicts",{"tool":38,"command":39},"bunx","bunx skills add Mekann2904\u002Fmekann --skill resolving-merge-conflicts",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Mekann2904\u002Fmekann --skill resolving-merge-conflicts","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMekann2904\u002Fmekann\u002Fblob\u002Fmain\u002Fmekann\u002Fskills\u002Fresolving-merge-conflicts\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M72THYFJF13P93N2F0SCN7BF","writing-assistant","Create, edit, and improve articles and technical documents by planning structure, clarifying dependencies, preserving technical accuracy, and tightening prose. Use when the user wants to draft, revise, or improve an article, guide, reference, design document, proposal, or other technical writing.","https:\u002F\u002Fgithub.com\u002FMekann2904\u002Fmekann\u002Fblob\u002Fmain\u002Fmekann\u002Fskills\u002Fwriting-assistant\u002FSKILL.md",[],[],{"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},"01M72THVWJNXRBYKRV9KERZETA","triage","Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.","https:\u002F\u002Fgithub.com\u002FMekann2904\u002Fmekann\u002Fblob\u002Fmain\u002Fmekann\u002Fskills\u002Ftriage\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},"01M72THSWAY2FKT4B2CMPATPPA","to-prd","Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.","https:\u002F\u002Fgithub.com\u002FMekann2904\u002Fmekann\u002Fblob\u002Fmain\u002Fmekann\u002Fskills\u002Fto-prd\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},"01M72THQ5B1G8M2SNFJ1XEZ82N","to-issues","Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.","https:\u002F\u002Fgithub.com\u002FMekann2904\u002Fmekann\u002Fblob\u002Fmain\u002Fmekann\u002Fskills\u002Fto-issues\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},"01M72THMPT2V3TK4FS4512Z7TE","thermo-nuclear-code-quality-review","Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.","https:\u002F\u002Fgithub.com\u002FMekann2904\u002Fmekann\u002Fblob\u002Fmain\u002Fmekann\u002Fskills\u002Fthermo-nuclear-code-quality-review\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},"01M72THJ3JCC5F3H02C80WQM9F","teach","Teach the user a new skill or concept through a persistent, source-grounded learning workspace. Use when the user wants multi-session teaching, lessons, exercises, or a structured learning path.","https:\u002F\u002Fgithub.com\u002FMekann2904\u002Fmekann\u002Fblob\u002Fmain\u002Fmekann\u002Fskills\u002Fteach\u002FSKILL.md",[],[]]