[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M781QJSF3Y3RJS8HGHP5K5F1":3,"skill-same:01M781QJSF3Y3RJS8HGHP5K5F1":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},"01M781QJSF3Y3RJS8HGHP5K5F1","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\".","TheAngryPit\u002FTheAngrySkills","TheAngryPit","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7040636?v=4","01M7803EENA9ATXJ46S9268QJX","Vitor Cepeda Lopes","01M7803EF9FMF4G4420XE4DV7Y",0,"MIT","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fsnapshot\u002Fcursor-team-kit\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","f31e1d2df163b90a48e30d0a3df67285f6641418","sources\u002Fcursor-plugins\u002Fsnapshot\u002Fcursor-team-kit\u002Fskills\u002Fmake-pr-easy-to-review",1,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills","https:\u002F\u002Fgithub.com\u002FTheAngryPit","www.vitorcepedalopes.com","Creative Director | Executive Producer | Storyteller | Narrative Worlds & Creative Production Systems\r\nFounder @TheHive-Mind ","2026-11-14 21:48:38",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TheAngryPit\u002FTheAngrySkills --skill make-pr-easy-to-review",{"tool":39,"command":40},"bunx","bunx skills add TheAngryPit\u002FTheAngrySkills --skill make-pr-easy-to-review",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TheAngryPit\u002FTheAngrySkills --skill make-pr-easy-to-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fsnapshot\u002Fcursor-team-kit\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},"01M782GJ4CTPNKZN0WXTASXXZ4","X MCP guide","ALWAYS read this before using any X tool (the X plugin, any X MCP, or Grok Bot's built-in public X reads) and again on any X error. X tools are included in Grok Bot at no cost: never estimate costs, check credits, or tell the user to buy credits. tools=0 \u002F user-X-* not found is a setup failure, not a paywall. Covers Spaces, communities, and Lists (reads and list writes), X Chat (XChat, inbox, DMs, unread, message requests, Chat PIN, juicebox, xchat_lite: clone xchat-grokbot-helper yourself and decrypt locally), scheduled X calls (schedule_call, list_scheduled_calls and the other call tools), and livestreams (stream sources, broadcasts, scheduled broadcasts, broadcast chat, moderators, mutes). Chat, call, livestream, Spaces, or Lists tools missing while other X tools work: reconnect the X plugin.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fx\u002Fskills\u002Fx-api-mcp-guide\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},"01M782GBW77901ESC9PD3XAM6V","X Money guide","Read this before the first X Money action in a session and again on any X Money error, refusal, or missing capability. Covers the approval rule for every action that moves money (always ask, every time, no exceptions), how the connection works (connection code plus passkey in the X app), how to guide the user through connect, reconnect, and revoke at x.com\u002Fi\u002Fmoney\u002Fsettings\u002Fconnections, and what each failure message means.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fx-money\u002Fskills\u002Fx-money-guide\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},"01M782G7CMYD2JSVT3RX81QRB8","google-slides","Build and edit Google Slides through the google-slides MCP tools - slides, grids of cards and columns, text boxes, shapes, images, tables, styling, layout inspection, and per-slide PNG rendering. Use when creating a deck, laying out slide elements, matching a template, or verifying how a slide looks.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fgoogle-slides\u002Fskills\u002Fgoogle-slides\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},"01M782G4DDAJ4SMGJEF13HTX69","google-sheets","Build and edit Google Sheets with the google-sheets tools - values, formatting, charts, conditional formatting, structure, validation, named and protected ranges. Use when creating a spreadsheet or dashboard, formatting cells, adding or fixing charts, or reorganizing tabs and rows.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fgoogle-sheets\u002Fskills\u002Fgoogle-sheets\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},"01M782G1F8QNMNKRSY6M3Y0QG6","google-drive","Work with Google Drive through its MCP tools - search, read, create, organize, share, comment, and export files. Use when creating files in specific folders, moving or renaming, converting Markdown\u002FCSV into Docs\u002FSheets, managing comments, or exporting a rendered PDF.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fgoogle-drive\u002Fskills\u002Fgoogle-drive\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},"01M782FYVJ5XTP2R0B446RRYTX","google-docs","Author and edit Google Docs with the google-docs tools - structured writing, character and paragraph styling, lists, tables, images, headers\u002Ffooters. Use when creating a formatted document, editing document content, or applying styles.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fgoogle-docs\u002Fskills\u002Fgoogle-docs\u002FSKILL.md",[],[]]