[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CVP755T7KT4YS814FMM7JS":3,"skill-same:01M7CVP755T7KT4YS814FMM7JS":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},"01M7CVP755T7KT4YS814FMM7JS","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\".","arjitj2\u002Fopen-pstack","arjitj2","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F15092149?v=4","01M7CVKN74D16AA1B4Y0CP3JKA","Arjit Jaiswal","01M7CVKN7SCSQVHE6GTQZC7XN6",16,"MIT","https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fmake-pr-easy-to-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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","264230bc14d9055d1333804799e7187e8e6e135c","plugins\u002Fpstack\u002Fskills\u002Fmake-pr-easy-to-review",2,"https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack","https:\u002F\u002Fgithub.com\u002Farjitj2","https:\u002F\u002Farjit.me\u002F","I want to work with great people to build great things that change the world.","2026-11-04 11:44:10",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add arjitj2\u002Fopen-pstack --skill make-pr-easy-to-review",{"tool":39,"command":40},"bunx","bunx skills add arjitj2\u002Fopen-pstack --skill make-pr-easy-to-review",{"tool":42,"command":43},"pnpm","pnpm dlx skills add arjitj2\u002Fopen-pstack --skill make-pr-easy-to-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\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},"01M7CVW5H20VXPF7Z01VXY20G2","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\u002Farjitj2\u002Fopen-pstack\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},"01M7CVW3937916EAX061GZTS4A","what-did-i-get-done","Summarize authored commits over a user-specified time period into a concise update","https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\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},"01M7CVW0Z4XXRTZ4GGCW4CT95B","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\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},"01M7CVVXMMWBB13598A412BXPR","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\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},"01M7CVVSD76JCSPTD6P55K24B0","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\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Fthermo-nuclear-code-quality-review\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},"01M7CVVN2PRJKWMSXTH2G6SBWY","technical-writing","Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for \u002Ftechnical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.","https:\u002F\u002Fgithub.com\u002Farjitj2\u002Fopen-pstack\u002Fblob\u002Fmain\u002Fplugins\u002Fpstack\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[]]