[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B6849W8G6SEZMDGRZXJ5NT":3,"skill-same:01M7B6849W8G6SEZMDGRZXJ5NT":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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7B6849W8G6SEZMDGRZXJ5NT","modernize",null,"Rebase an aging pull request onto its current base and judge whether it should still land, recommending MODERNIZE, REWORK, or CLOSE. Use when asked to rebase, refresh, or modernize an old PR.","scruffydan\u002FAI-Agents","scruffydan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2068435?v=4","01M6C56C2R0BYE41M4FV0TFTYK","Dan Moutal","01M6C56C6D1V2XHNXQ3NA3Z80V",0,"MIT","https:\u002F\u002Fgithub.com\u002Fscruffydan\u002FAI-Agents\u002Fblob\u002Fmain\u002Fsource\u002Fskills\u002Fmodernize\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fscruffydan\u002FAI-Agents\u002Fblob\u002Fmain\u002Fsource\u002Fskills\u002Fmodernize\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: modernize\ndescription: Rebase an aging pull request onto its current base and judge whether it should still land, recommending MODERNIZE, REWORK, or CLOSE. Use when asked to rebase, refresh, or modernize an old PR.\n---\n\n# Modernize\n\nModernize the idea, not just the branch. A clean rebase does not prove that the\nPR still belongs in the product.\n\n## Guardrails\n\n- Always check to make sure you have pulled latest origin for your branch, main\n  branch, and any other branch related to your work before starting.\n- Treat existing worktree changes as user-owned. Use a disposable worktree when\n  the active worktree is dirty or is being used for other work.\n- A request to modernize or rebase a PR authorizes rebasing and updating that\n  PR's branch. It does not authorize merging, closing, changing the base branch,\n  or expanding scope. If the branch belongs to another contributor, confirm\n  before rewriting it.\n- Never use an unqualified force push. Update a rebased branch with\n  `--force-with-lease` against the head SHA observed before the rebase.\n- Do not post a PR comment unless the user asked for one. Use the\n  `leaving-pr-comments` skill for every comment posted on the user's behalf.\n\n## Establish the PR's intent\n\nResolve the PR and record its URL, state, base, head repository and branch,\ncurrent head SHA, author, checks, and review state. Read the title, body, linked\nissues, commits, review threads, and complete diff. State the smallest coherent\ngoal the PR was trying to accomplish before judging its implementation.\n\nFetch the latest remote base and PR head. Use the PR's actual base branch,\nusually `main`, rather than assuming the local branch is current. Record the\nmerge base so the original PR and subsequent base-branch changes can be\ncompared separately.\n\n## Check what changed around it\n\nInspect commits and diffs added to the base branch since the PR diverged. Search\nmerged and open PRs when titles, code paths, or behavior suggest a replacement\nor competing implementation.\n\nLook beyond overlapping lines:\n\n- Has the same user-facing problem already been solved?\n- Did APIs, types, schemas, dependencies, or architectural boundaries change?\n- Do both sides now claim ownership of the same behavior or invariant?\n- Was the code being changed deleted, moved, or intentionally simplified?\n- Would landing the PR restore an old behavior or create two ways to do the\n  same thing?\n- Is the original benefit still large enough to justify the maintenance cost?\n\nDo not describe a PR as current merely because Git reports no conflicts.\n\n## Choose a disposition before pushing\n\nUse one of these recommendations:\n\n- **MODERNIZE**: the goal is still useful and the implementation remains the\n  right shape. Rebase, resolve conflicts, test, and update the branch.\n- **REWORK**: the goal is still useful, but a mechanical rebase would preserve\n  the wrong implementation. Explain the smallest credible rewrite and stop\n  before pushing unless the user also asked for that rework.\n- **CLOSE**: the PR is superseded, obsolete, directionally wrong, or no longer\n  worth its cost. Cite concrete evidence and stop. Do not spend time rebasing an\n  obsolete branch, and do not close it without explicit permission.\n\nBe willing to recommend `CLOSE`. Age alone is not evidence, and sunk effort is\nnot a reason to keep a PR alive.\n\n## Rebase without losing intent\n\nFor a `MODERNIZE` disposition:\n\n1. Create a safe local branch or disposable worktree at the recorded PR head.\n2. Rebase its commits onto the freshly fetched base branch.\n3. Resolve each conflict according to the PR's current intent and the base\n   branch's newer invariants. If a conflict reveals a product or architecture\n   disagreement, stop and reconsider the disposition instead of guessing.\n4. Compare the pre-rebase and post-rebase commit series with `git range-diff`\n   and inspect the final diff. Confirm that no intentional behavior disappeared\n   and no already-landed behavior was reintroduced.\n5. Run the repository's focused checks for the touched area. Distinguish real\n   failures from pre-existing or infrastructure failures.\n6. Push with `--force-with-lease` tied to the previously observed remote head.\n   If the lease fails, fetch and reassess rather than overwriting new work.\n\nDo not merge the PR.\n\n## Report\n\nLead with `MODERNIZE`, `REWORK`, or `CLOSE` and the reason. Then summarize:\n\n- meaningful changes on the base branch;\n- conceptual conflicts or confirmation that none were found;\n- the rebase and push result, if performed;\n- checks run and their results;\n- the remaining decision or work, with a link to the PR.\n\nSeparate observed facts from judgment. Say what could not be verified instead\nof manufacturing confidence.\n\n## Source\n\nAdapted from Theo Browne's\n[tstack modernize skill](https:\u002F\u002Fgithub.com\u002Ft3dotgg\u002Ftstack\u002Fblob\u002F6efae364201abc9d9f07443e9caa461f42e51090\u002Fskills\u002Fmodernize\u002FSKILL.md).\nThe instruction body is unchanged except for the authorization guardrail, which\nnow scopes the update to the PR's own branch and asks before rewriting another\ncontributor's branch. The description was rewritten to name the three\noutcomes. Upstream's Codex-only `agents\u002Fopenai.yaml` was not copied, and this\nsource note was added. The upstream MIT notice is retained in [LICENSE](LICENSE).\n","# Modernize\n\nModernize the idea, not just the branch. A clean rebase does not prove that the\nPR still belongs in the product.\n\n## Guardrails\n\n- Always check to make sure you have pulled latest origin for your branch, main\n  branch, and any other branch related to your work before starting.\n- Treat existing worktree changes as user-owned. Use a disposable worktree when\n  the active worktree is dirty or is being used for other work.\n- A request to modernize or rebase a PR authorizes rebasing and updating that\n  PR's branch. It does not authorize merging, closing, changing the base branch,\n  or expanding scope. If the branch belongs to another contributor, confirm\n  before rewriting it.\n- Never use an unqualified force push. Update a rebased branch with\n  `--force-with-lease` against the head SHA observed before the rebase.\n- Do not post a PR comment unless the user asked for one. Use the\n  `leaving-pr-comments` skill for every comment posted on the user's behalf.\n\n## Establish the PR's intent\n\nResolve the PR and record its URL, state, base, head repository and branch,\ncurrent head SHA, author, checks, and review state. Read the title, body, linked\nissues, commits, review threads, and complete diff. State the smallest coherent\ngoal the PR was trying to accomplish before judging its implementation.\n\nFetch the latest remote base and PR head. Use the PR's actual base branch,\nusually `main`, rather than assuming the local branch is current. Record the\nmerge base so the original PR and subsequent base-branch changes can be\ncompared separately.\n\n## Check what changed around it\n\nInspect commits and diffs added to the base branch since the PR diverged. Search\nmerged and open PRs when titles, code paths, or behavior suggest a replacement\nor competing implementation.\n\nLook beyond overlapping lines:\n\n- Has the same user-facing problem already been solved?\n- Did APIs, types, schemas, dependencies, or architectural boundaries change?\n- Do both sides now claim ownership of the same behavior or invariant?\n- Was the code being changed deleted, moved, or intentionally simplified?\n- Would landing the PR restore an old behavior or create two ways to do the\n  same thing?\n- Is the original benefit still large enough to justify the maintenance cost?\n\nDo not describe a PR as current merely because Git reports no conflicts.\n\n## Choose a disposition before pushing\n\nUse one of these recommendations:\n\n- **MODERNIZE**: the goal is still useful and the implementation remains the\n  right shape. Rebase, resolve conflicts, test, and update the branch.\n- **REWORK**: the goal is still useful, but a mechanical rebase would preserve\n  the wrong implementation. Explain the smallest credible rewrite and stop\n  before pushing unless the user also asked for that rework.\n- **CLOSE**: the PR is superseded, obsolete, directionally wrong, or no longer\n  worth its cost. Cite concrete evidence and stop. Do not spend time rebasing an\n  obsolete branch, and do not close it without explicit permission.\n\nBe willing to recommend `CLOSE`. Age alone is not evidence, and sunk effort is\nnot a reason to keep a PR alive.\n\n## Rebase without losing intent\n\nFor a `MODERNIZE` disposition:\n\n1. Create a safe local branch or disposable worktree at the recorded PR head.\n2. Rebase its commits onto the freshly fetched base branch.\n3. Resolve each conflict according to the PR's current intent and the base\n   branch's newer invariants. If a conflict reveals a product or architecture\n   disagreement, stop and reconsider the disposition instead of guessing.\n4. Compare the pre-rebase and post-rebase commit series with `git range-diff`\n   and inspect the final diff. Confirm that no intentional behavior disappeared\n   and no already-landed behavior was reintroduced.\n5. Run the repository's focused checks for the touched area. Distinguish real\n   failures from pre-existing or infrastructure failures.\n6. Push with `--force-with-lease` tied to the previously observed remote head.\n   If the lease fails, fetch and reassess rather than overwriting new work.\n\nDo not merge the PR.\n\n## Report\n\nLead with `MODERNIZE`, `REWORK`, or `CLOSE` and the reason. Then summarize:\n\n- meaningful changes on the base branch;\n- conceptual conflicts or confirmation that none were found;\n- the rebase and push result, if performed;\n- checks run and their results;\n- the remaining decision or work, with a link to the PR.\n\nSeparate observed facts from judgment. Say what could not be verified instead\nof manufacturing confidence.\n\n## Source\n\nAdapted from Theo Browne's\n[tstack modernize skill](https:\u002F\u002Fgithub.com\u002Ft3dotgg\u002Ftstack\u002Fblob\u002F6efae364201abc9d9f07443e9caa461f42e51090\u002Fskills\u002Fmodernize\u002FSKILL.md).\nThe instruction body is unchanged except for the authorization guardrail, which\nnow scopes the update to the PR's own branch and asks before rewriting another\ncontributor's branch. The description was rewritten to name the three\noutcomes. Upstream's Codex-only `agents\u002Fopenai.yaml` was not copied, and this\nsource note was added. The upstream MIT notice is retained in [LICENSE](LICENSE).\n",{"name":5,"description":7},"main","d384d240bc9515ef5d58bbf638aef5e767854c51","source\u002Fskills\u002Fmodernize","https:\u002F\u002Fgithub.com\u002Fscruffydan\u002FAI-Agents","https:\u002F\u002Fgithub.com\u002Fscruffydan","ofdan.ca","Friendly neighbourhood sysadmin","2026-11-14 04:31:13",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add scruffydan\u002FAI-Agents --skill modernize",{"tool":39,"command":40},"bunx","bunx skills add scruffydan\u002FAI-Agents --skill modernize",{"tool":42,"command":43},"pnpm","pnpm dlx skills add scruffydan\u002FAI-Agents --skill modernize","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fscruffydan\u002FAI-Agents\u002Fblob\u002Fmain\u002Fsource\u002Fskills\u002Fmodernize\u002FSKILL.md",true,[47],{"path":48,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":16},"LICENSE","许可证",1068,[52,60,68,76,84,92],{"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":56,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":20},"01M7B68RJTMNJJRM89EGMGQ1WJ","writing-for-agents","Author or revise agent instruction artifacts such as AGENTS.md, skill instructions, and agent prompts. Use for their triggers, structure, constraints, and completion criteria, not ordinary coding answers or general prose editing.","https:\u002F\u002Fgithub.com\u002Fscruffydan\u002FAI-Agents\u002Fblob\u002Fmain\u002Fsource\u002Fskills\u002Fwriting-for-agents\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fscruffydan\u002FAI-Agents\u002Fblob\u002Fmain\u002Fsource\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":64,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":20},"01M7B68NGQRJXA232T7X9SQ9HM","why","Investigate why a design or architectural choice was made, using code history and decision records. Use for rationale questions like why X was built this way or chosen over Y, not how code works today (use teach), debugging failures, or Five Whys process analysis.","https:\u002F\u002Fgithub.com\u002Fscruffydan\u002FAI-Agents\u002Fblob\u002Fmain\u002Fsource\u002Fskills\u002Fwhy\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fscruffydan\u002FAI-Agents\u002Fblob\u002Fmain\u002Fsource\u002Fskills\u002Fwhy\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":72,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":20},"01M7B68J77GKP1C1T1XF1DZ97V","unslop","Edit prose to remove AI writing patterns such as stock vocabulary, filler, hedging, and mannered phrasing. Use when asked to unslop or de-AI text, or to polish a substantial prose draft; not for code, short routine replies, or deciding the content and structure of documentation or agent instructions.","https:\u002F\u002Fgithub.com\u002Fscruffydan\u002FAI-Agents\u002Fblob\u002Fmain\u002Fsource\u002Fskills\u002Funslop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fscruffydan\u002FAI-Agents\u002Fblob\u002Fmain\u002Fsource\u002Fskills\u002Funslop\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},"01M7B68F0GCQSF1V4SEGCW7100","to-tickets","Turn an established plan into independently verifiable vertical implementation slices with acceptance criteria, verification, and true dependencies. Use when breaking planned work into tickets; small changes can stay as one task.","https:\u002F\u002Fgithub.com\u002Fscruffydan\u002FAI-Agents\u002Fblob\u002Fmain\u002Fsource\u002Fskills\u002Fto-tickets\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fscruffydan\u002FAI-Agents\u002Fblob\u002Fmain\u002Fsource\u002Fskills\u002Fto-tickets\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},"01M7B68C77N5M2N5BHK8137V43","technical-writing","Write or revise technical documentation, tutorials, how-to guides, reference material, and explanations so readers can understand and complete their task.","https:\u002F\u002Fgithub.com\u002Fscruffydan\u002FAI-Agents\u002Fblob\u002Fmain\u002Fsource\u002Fskills\u002Ftechnical-writing\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fscruffydan\u002FAI-Agents\u002Fblob\u002Fmain\u002Fsource\u002Fskills\u002Ftechnical-writing\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},"01M7B689G60Y3H3S8FSR1MM5PJ","teach","Explain what a concept means or how code works today, from the current code and docs. Use for how-it-works questions, including why code behaves as it does, not why a design was chosen or introduced (use why) or diagnosing failures.","https:\u002F\u002Fgithub.com\u002Fscruffydan\u002FAI-Agents\u002Fblob\u002Fmain\u002Fsource\u002Fskills\u002Fteach\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fscruffydan\u002FAI-Agents\u002Fblob\u002Fmain\u002Fsource\u002Fskills\u002Fteach\u002FSKILL.md",[],[]]