[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M735A6NPRGFM4VAC2VKSZX65":3,"skill-same:01M735A6NPRGFM4VAC2VKSZX65":51},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":35,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":37,"install":38,"resources":50},"01M735A6NPRGFM4VAC2VKSZX65","split-concerns",null,"Split multi-concern PRs.","Morrison-Lab\u002Fai-config","Morrison-Lab","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F104235520?v=4","01M734G0451S2G35MN4HFQK7XP","Morrison Lab","01M734G059BYFDFQA8YTPDGPMH",4,"MIT","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fsplit-concerns\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: split-concerns\ndescription: \"Split multi-concern PRs.\"\nuser-invocable: true\nallowed-tools:\n  - Bash\n  - Read\n  - Edit\n  - Write\n---\n\n# split-concerns\n\nWhen a set of changes addresses multiple independent concerns, split them\ninto separate MRs\u002FPRs rather than bundling everything together.\n\n## When this fires\n\n- You're about to commit changes that touch unrelated subsystems\n- A reviewer flags \"this MR does too many things\"\n- You notice your commit message needs \"and\" more than once\n- The diff is large and contains logically separable chunks\n- One part of the change is controversial but another is straightforward\n\n## What counts as \"independent concerns\"\n\nTwo changes are independent if:\n- They could be merged in either order without conflict\n- They solve different problems \u002F close different issues\n- A revert of one wouldn't affect the other\n- They'd have different reviewers in an ideal world\n\nExamples:\n- Refactor + substantive modification (behavior change, bug fix, feature) → split: always refactor before modifying substance in a dedicated behavior-preserving PR, and stack the substantive change on top ([refactor-before-modifying-substance](..\u002F..\u002Fshared\u002Fprinciples\u002Frefactor-before-modifying-substance.md), [`stack-prs`](..\u002Fstack-prs\u002FSKILL.md))\n- Bug fix + unrelated refactor → split\n- Feature + the test for that feature → keep together\n- CI template fix + documentation update for that fix → keep together\n- CI template fix + unrelated linter config change → split\n- CI\u002Fworkflow change (`.github\u002Fworkflows\u002F`) + heavy simulation\u002Fvalidation dataset artifacts (`inst\u002Fextdata\u002F*.rds`, `*.parquet`, `*.RData`) → split\n- CI\u002Fworkflow change (`.github\u002Fworkflows\u002F`) + HPC job array updates → split\n- Heavy simulation\u002Fvalidation dataset artifacts (`inst\u002Fextdata\u002F*.rds`, `*.parquet`, `*.RData`) + HPC job array updates → split\n- Dependency update + code that uses the new dependency → keep together\n\n## Process\n\n1. **Identify the concerns** — list each logically independent change\n2. **Assess dependencies** — can they be merged independently?\n3. **Propose the split** to the user:\n   ```\n   This MR addresses 3 independent concerns:\n   1. Fix the review job trigger (closes #32)\n   2. Update stage naming convention\n   3. Add shellcheck to CI\n\n   Want me to split these into separate MRs? They can merge independently\n   and won't block each other during review.\n   ```\n4. **If approved**, create the branches:\n   - Start each from `main` (not from each other)\n   - Cherry-pick or recreate the relevant commits on each branch\n   - Open separate MRs with focused descriptions\n   - Cross-reference them (\"Related: #25, #26\")\n\n## Benefits to communicate\n\n- **Faster review** — smaller diffs are easier to review thoroughly\n- **Independent timelines** — a simple fix can merge while a complex change\n  is still being discussed\n- **Cleaner history** — each merge commit tells one story\n- **Lower risk** — if one change causes a regression, the revert is surgical\n- **Better CI signal** — failures are attributable to a specific change\n\n## When NOT to split\n\n- Changes are tightly coupled (splitting would break one or both)\n- The total diff is small (\u003C50 lines) and splitting adds more overhead than value\n- User explicitly says \"keep it in one MR\"\n- The concerns share significant context that would be lost if separated\n\n## When unsure how finely to split, split finer\n\nWhen the split could reasonably go either way,\ntake the finer one.\nA split that turns out too fine costs bookkeeping:\none more PR to open,\nand sometimes a temporary gap between the PRs,\nsuch as a link to content that the later PR has not yet added,\nwhich stays broken until that PR lands.\nA split that is too coarse gives up the \"Benefits to communicate\" above,\nmost visibly faster review and independent timelines.\n\n- **Do:** pick the finer split when both are defensible,\n  and accept a temporary gap that a later PR closes.\n  A gap makes the pieces dependent rather than independent in the sense above,\n  so open them as stacked PRs (`stack-prs`) and state the merge order.\n- **Don't:** settle on the coarser split just because it means fewer PRs to manage.\n- **Don't:** stretch the judgment items in \"When NOT to split\" above into tiebreakers.\n  The small-diff item applies to a diff that really is under 50 lines,\n  and the shared-context item only when a reviewer of one PR\n  could not follow it without reading the other's diff.\n  Context that a cross-reference (\"Related: #N\") carries is not lost.\n\n(Directive from the user, 2026-09-25:\n\"when uncertain, err on the side of more decomposition\",\nsaid about splitting a large lecture-notes consolidation into PRs.)\n","# split-concerns\n\nWhen a set of changes addresses multiple independent concerns, split them\ninto separate MRs\u002FPRs rather than bundling everything together.\n\n## When this fires\n\n- You're about to commit changes that touch unrelated subsystems\n- A reviewer flags \"this MR does too many things\"\n- You notice your commit message needs \"and\" more than once\n- The diff is large and contains logically separable chunks\n- One part of the change is controversial but another is straightforward\n\n## What counts as \"independent concerns\"\n\nTwo changes are independent if:\n- They could be merged in either order without conflict\n- They solve different problems \u002F close different issues\n- A revert of one wouldn't affect the other\n- They'd have different reviewers in an ideal world\n\nExamples:\n- Refactor + substantive modification (behavior change, bug fix, feature) → split: always refactor before modifying substance in a dedicated behavior-preserving PR, and stack the substantive change on top ([refactor-before-modifying-substance](..\u002F..\u002Fshared\u002Fprinciples\u002Frefactor-before-modifying-substance.md), [`stack-prs`](..\u002Fstack-prs\u002FSKILL.md))\n- Bug fix + unrelated refactor → split\n- Feature + the test for that feature → keep together\n- CI template fix + documentation update for that fix → keep together\n- CI template fix + unrelated linter config change → split\n- CI\u002Fworkflow change (`.github\u002Fworkflows\u002F`) + heavy simulation\u002Fvalidation dataset artifacts (`inst\u002Fextdata\u002F*.rds`, `*.parquet`, `*.RData`) → split\n- CI\u002Fworkflow change (`.github\u002Fworkflows\u002F`) + HPC job array updates → split\n- Heavy simulation\u002Fvalidation dataset artifacts (`inst\u002Fextdata\u002F*.rds`, `*.parquet`, `*.RData`) + HPC job array updates → split\n- Dependency update + code that uses the new dependency → keep together\n\n## Process\n\n1. **Identify the concerns** — list each logically independent change\n2. **Assess dependencies** — can they be merged independently?\n3. **Propose the split** to the user:\n   ```\n   This MR addresses 3 independent concerns:\n   1. Fix the review job trigger (closes #32)\n   2. Update stage naming convention\n   3. Add shellcheck to CI\n\n   Want me to split these into separate MRs? They can merge independently\n   and won't block each other during review.\n   ```\n4. **If approved**, create the branches:\n   - Start each from `main` (not from each other)\n   - Cherry-pick or recreate the relevant commits on each branch\n   - Open separate MRs with focused descriptions\n   - Cross-reference them (\"Related: #25, #26\")\n\n## Benefits to communicate\n\n- **Faster review** — smaller diffs are easier to review thoroughly\n- **Independent timelines** — a simple fix can merge while a complex change\n  is still being discussed\n- **Cleaner history** — each merge commit tells one story\n- **Lower risk** — if one change causes a regression, the revert is surgical\n- **Better CI signal** — failures are attributable to a specific change\n\n## When NOT to split\n\n- Changes are tightly coupled (splitting would break one or both)\n- The total diff is small (\u003C50 lines) and splitting adds more overhead than value\n- User explicitly says \"keep it in one MR\"\n- The concerns share significant context that would be lost if separated\n\n## When unsure how finely to split, split finer\n\nWhen the split could reasonably go either way,\ntake the finer one.\nA split that turns out too fine costs bookkeeping:\none more PR to open,\nand sometimes a temporary gap between the PRs,\nsuch as a link to content that the later PR has not yet added,\nwhich stays broken until that PR lands.\nA split that is too coarse gives up the \"Benefits to communicate\" above,\nmost visibly faster review and independent timelines.\n\n- **Do:** pick the finer split when both are defensible,\n  and accept a temporary gap that a later PR closes.\n  A gap makes the pieces dependent rather than independent in the sense above,\n  so open them as stacked PRs (`stack-prs`) and state the merge order.\n- **Don't:** settle on the coarser split just because it means fewer PRs to manage.\n- **Don't:** stretch the judgment items in \"When NOT to split\" above into tiebreakers.\n  The small-diff item applies to a diff that really is under 50 lines,\n  and the shared-context item only when a reviewer of one PR\n  could not follow it without reading the other's diff.\n  Context that a cross-reference (\"Related: #N\") carries is not lost.\n\n(Directive from the user, 2026-09-25:\n\"when uncertain, err on the side of more decomposition\",\nsaid about splitting a large lecture-notes consolidation into PRs.)\n",{"name":5,"description":7,"allowed-tools":24,"user-invocable":29},[25,26,27,28],"Bash","Read","Edit","Write",true,"main","0f720481f8ce3b3d9fef485f6e230d8b3035748e","skills\u002Fsplit-concerns",1,"https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config","https:\u002F\u002Fmorrison-lab.github.io\u002Fai-config\u002F","https:\u002F\u002Fgithub.com\u002FMorrison-Lab","2026-11-15 04:39:15",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":29},[40,43,46],{"tool":41,"command":42},"npx","npx skills add Morrison-Lab\u002Fai-config --skill split-concerns",{"tool":44,"command":45},"bunx","bunx skills add Morrison-Lab\u002Fai-config --skill split-concerns",{"tool":47,"command":48},"pnpm","pnpm dlx skills add Morrison-Lab\u002Fai-config --skill split-concerns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fsplit-concerns\u002FSKILL.md",[],[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M735BVYCGR5VEC65AFDVSNKW","wrap-up","End-of-session verification and UMS.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fwrap-up\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M735BTH469T1CQ8G2Q9GENCR","workaround-watcher","Watch upstream issue for fix.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fworkaround-watcher\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M735BRKZWFANSQ0GM380B4TD","wn","→ whats-next.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fwn\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M735BPE9V830B3B6NGXQ56J6","whats-next","Recommend concrete next step or action.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fwhats-next\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M735BMHQ60EAD5B7QAWXC5A0","wait-for-results","Wait for pipeline\u002FCI results.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fwait-for-results\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M735BKGZHPN1PEMJ7YBD5VJ8","wai","→ send-notes.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fwai\u002FSKILL.md",[],[]]