[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M750BMEVBY3RMT9MF5WZ365B":3,"skill-same:01M750BMEVBY3RMT9MF5WZ365B":47},{"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},"01M750BMEVBY3RMT9MF5WZ365B","make-pr-easy-to-review",null,"Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior. Use for \"make this easy to review\", \"tidy this PR\", \"clean up commits\", or \"annotate the diff\".","michael-denyer\u002Fpstack-claude","michael-denyer","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F97485362?v=4","01M7509NWA6PC2Z183SZ6D78FT","Michael Denyer","01M7509NX1YE4AYWW6Y30TCCRV",4309,"MIT","https:\u002F\u002Fgithub.com\u002Fmichael-denyer\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fmake-pr-easy-to-review\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: make-pr-easy-to-review\ndescription: Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior. Use for \"make this easy to review\", \"tidy this PR\", \"clean up commits\", or \"annotate the diff\".\n---\n\n# Make PR Easy to Review\n\nPrepare a PR so a reviewer can quickly understand the intent, important files, and risk. The default goal is reviewability without behavior changes.\n\n## Workflow\n\n1. Resolve the target PR from the user-provided URL or current branch.\n2. Inspect commits, diff size, changed paths, generated files, and PR description.\n3. Identify reviewability issues: noisy commits, stale description, unrelated changes, mixed mechanical and logic changes, missing tests, or unclear reviewer entry points.\n4. Propose a plan before rewriting history or force-pushing.\n5. Apply safe improvements, then verify the tree or diff still matches the intended code.\n\n## History Cleanup\n\nOnly rewrite history when the user asks for it or agrees to the plan. Before rewriting:\n\n```bash\ngh pr view \u003CPR> --json title,headRefName,baseRefName,state,commits\ngit fetch origin \u003CheadRefName> \u003CbaseRefName>\nORIGINAL_TREE=$(git rev-parse origin\u002F\u003CheadRefName>^{tree})\n```\n\nGood commit groupings usually follow dependency order:\n\n1. Schema\u002Fstorage or generated API definitions.\n2. Core logic.\n3. Wiring and integration.\n4. UI or surface behavior.\n5. Tests.\n\nAfter rewriting, verify content identity:\n\n```bash\necho \"Original tree: $ORIGINAL_TREE\"\necho \"Current tree:  $(git rev-parse HEAD^{tree})\"\ngit diff origin\u002F\u003CheadRefName> --stat\n```\n\nDo not push if the tree changed unintentionally.\n\n## Reviewer Guidance\n\nWhen code behavior should stay untouched, prefer PR description and review notes:\n\n- Add a TL;DR that matches the actual diff.\n- Separate core files from generated or mechanical files.\n- Call out risky behavior changes, migration order, rollout plan, and test coverage.\n- Link issue trackers, dashboards, or design docs when they explain intent.\n\n## Guardrails\n\n- Never hide meaningful behavior changes inside \"cleanup\".\n- Do not bypass hooks unless the user explicitly asks.\n- If the PR is too large to make reviewable with notes, recommend splitting instead of polishing around the problem.\n","# Make PR Easy to Review\n\nPrepare a PR so a reviewer can quickly understand the intent, important files, and risk. The default goal is reviewability without behavior changes.\n\n## Workflow\n\n1. Resolve the target PR from the user-provided URL or current branch.\n2. Inspect commits, diff size, changed paths, generated files, and PR description.\n3. Identify reviewability issues: noisy commits, stale description, unrelated changes, mixed mechanical and logic changes, missing tests, or unclear reviewer entry points.\n4. Propose a plan before rewriting history or force-pushing.\n5. Apply safe improvements, then verify the tree or diff still matches the intended code.\n\n## History Cleanup\n\nOnly rewrite history when the user asks for it or agrees to the plan. Before rewriting:\n\n```bash\ngh pr view \u003CPR> --json title,headRefName,baseRefName,state,commits\ngit fetch origin \u003CheadRefName> \u003CbaseRefName>\nORIGINAL_TREE=$(git rev-parse origin\u002F\u003CheadRefName>^{tree})\n```\n\nGood commit groupings usually follow dependency order:\n\n1. Schema\u002Fstorage or generated API definitions.\n2. Core logic.\n3. Wiring and integration.\n4. UI or surface behavior.\n5. Tests.\n\nAfter rewriting, verify content identity:\n\n```bash\necho \"Original tree: $ORIGINAL_TREE\"\necho \"Current tree:  $(git rev-parse HEAD^{tree})\"\ngit diff origin\u002F\u003CheadRefName> --stat\n```\n\nDo not push if the tree changed unintentionally.\n\n## Reviewer Guidance\n\nWhen code behavior should stay untouched, prefer PR description and review notes:\n\n- Add a TL;DR that matches the actual diff.\n- Separate core files from generated or mechanical files.\n- Call out risky behavior changes, migration order, rollout plan, and test coverage.\n- Link issue trackers, dashboards, or design docs when they explain intent.\n\n## Guardrails\n\n- Never hide meaningful behavior changes inside \"cleanup\".\n- Do not bypass hooks unless the user explicitly asks.\n- If the PR is too large to make reviewable with notes, recommend splitting instead of polishing around the problem.\n",{"name":5,"description":7},"main","bc09365fe61c725c486ba95157fc4048bf8a0b99","plugins\u002Fpstack\u002Fskills\u002Fmake-pr-easy-to-review",397,"https:\u002F\u002Fgithub.com\u002Fmichael-denyer\u002Fpstack-claude","https:\u002F\u002Fgithub.com\u002Fmichael-denyer","https:\u002F\u002Fwww.wisdompanel.com\u002F","Software Engineer and Bioinformatician","2026-11-13 23:53:05",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add michael-denyer\u002Fpstack-claude --skill make-pr-easy-to-review",{"tool":39,"command":40},"bunx","bunx skills add michael-denyer\u002Fpstack-claude --skill make-pr-easy-to-review",{"tool":42,"command":43},"pnpm","pnpm dlx skills add michael-denyer\u002Fpstack-claude --skill make-pr-easy-to-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmichael-denyer\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fmake-pr-easy-to-review\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M750F31RNVHGK1JVWBJHDGTX","why","Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002Fmichael-denyer\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M750F17NKT7YCP8ND5675XHN","what-did-i-get-done","Summarize authored commits over a user-specified time period into a concise update","https:\u002F\u002Fgithub.com\u002Fmichael-denyer\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fwhat-did-i-get-done\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M750EYD7DP60DDPQY6GK3TTR","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Fmichael-denyer\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M750EWQG73FRRSA065D2NMRZ","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fmichael-denyer\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Ftypescript-best-practices\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":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M750ETTMA3MB36DJQJ1H4QGB","thermos","Launch both thermo-nuclear review subagents in parallel, then synthesize their findings. Use for thermos, double thermo review, or combined bug\u002Fsecurity and code-quality branch audits.","https:\u002F\u002Fgithub.com\u002Fmichael-denyer\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fthermos\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M750EQVQMQSW08KYGM7TG8K0","thermo-nuclear-review","Comprehensive security and correctness audit of a branch's changes. Use for thermo nuclear, thermonuclear, or deep review requests, or branch\u002FPR diff audits focused on bugs, breaking changes, security issues, devex regressions, and feature-gate leaks.","https:\u002F\u002Fgithub.com\u002Fmichael-denyer\u002Fpstack-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fthermo-nuclear-review\u002FSKILL.md",[],[]]