[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CMW4AXRH294WBK28D5CDD9":3,"skill-same:01M7CMW4AXRH294WBK28D5CDD9":49},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7CMW4AXRH294WBK28D5CDD9","pr-writer",null,"Create pull requests following Sentry's engineering practices.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fpr-writer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: pr-writer\ndescription: \"Create pull requests following Sentry's engineering practices.\"\nrisk: unknown\nsource: community\n---\n\n# PR Writer\n\nCreate pull requests following Sentry's engineering practices.\n\n**Requires**: GitHub CLI (`gh`) authenticated and available.\n\n## When to Use\n- You are ready to open a pull request and need a structured description based on the committed branch diff.\n- You want the PR body to capture what changed, why it changed, and any reviewer context.\n- You are using GitHub CLI and need a repeatable PR-writing workflow rather than writing the description ad hoc.\n\n## Prerequisites\n\nBefore creating a PR, ensure all changes are committed. If there are uncommitted changes, run the `sentry-skills:commit` skill first to commit them properly.\n\n```bash\n# Check for uncommitted changes\ngit status --porcelain\n```\n\nIf the output shows any uncommitted changes (modified, added, or untracked files that should be included), invoke the `sentry-skills:commit` skill before proceeding.\n\n## Process\n\n### Step 1: Verify Branch State\n\n```bash\n# Detect the default branch — note the output for use in subsequent commands\ngh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'\n```\n\n```bash\n# Check current branch and status (substitute the detected branch name above for BASE)\ngit status\ngit log BASE..HEAD --oneline\n```\n\nEnsure:\n- All changes are committed\n- Branch is up to date with remote\n- Changes are rebased on the base branch if needed\n\n### Step 2: Analyze Changes\n\nReview what will be included in the PR:\n\n```bash\n# See all commits that will be in the PR (substitute detected branch name for BASE)\ngit log BASE..HEAD\n\n# See the full diff\ngit diff BASE...HEAD\n```\n\nUnderstand the scope and purpose of all changes before writing the description.\n\n### Step 3: Write the PR Description\n\nUse this structure for PR descriptions (ignoring any repository PR templates):\n\n```markdown\n\u003Cbrief description of what the PR does>\n\n\u003Cwhy these changes are being made - the motivation>\n\n\u003Calternative approaches considered, if any>\n\n\u003Cany additional context reviewers need>\n```\n\n**Do NOT include:**\n- \"Test plan\" sections\n- Checkbox lists of testing steps\n- Redundant summaries of the diff\n\n**Do include:**\n- Clear explanation of what and why\n- Links to relevant issues or tickets\n- Context that isn't obvious from the code\n- Notes on specific areas that need careful review\n\n### Step 4: Create the PR\n\n```bash\ngh pr create --draft --title \"\u003Ctype>(\u003Cscope>): \u003Cdescription>\" --body \"$(cat \u003C\u003C'EOF'\n\u003Cdescription body here>\nEOF\n)\"\n```\n\n**Title format** follows commit conventions:\n- `feat(scope): Add new feature`\n- `fix(scope): Fix the bug`\n- `ref: Refactor something`\n\n## PR Description Examples\n\n### Feature PR\n\n```markdown\nAdd Slack thread replies for alert notifications\n\nWhen an alert is updated or resolved, we now post a reply to the original\nSlack thread instead of creating a new message. This keeps related\nnotifications grouped and reduces channel noise.\n\nPreviously considered posting edits to the original message, but threading\nbetter preserves the timeline of events and works when the original message\nis older than Slack's edit window.\n\nRefs SENTRY-1234\n```\n\n### Bug Fix PR\n\n```markdown\nHandle null response in user API endpoint\n\nThe user endpoint could return null for soft-deleted accounts, causing\ndashboard crashes when accessing user properties. This adds a null check\nand returns a proper 404 response.\n\nFound while investigating SENTRY-5678.\n\nFixes SENTRY-5678\n```\n\n### Refactor PR\n\n```markdown\nExtract validation logic to shared module\n\nMoves duplicate validation code from the alerts, issues, and projects\nendpoints into a shared validator class. No behavior change.\n\nThis prepares for adding new validation rules in SENTRY-9999 without\nduplicating logic across endpoints.\n```\n\n## Issue References\n\nReference issues in the PR body:\n\n| Syntax | Effect |\n|--------|--------|\n| `Fixes #1234` | Closes GitHub issue on merge |\n| `Fixes SENTRY-1234` | Closes Sentry issue |\n| `Refs GH-1234` | Links without closing |\n| `Refs LINEAR-ABC-123` | Links Linear issue |\n\n## Guidelines\n\n- **One PR per feature\u002Ffix** - Don't bundle unrelated changes\n- **Keep PRs reviewable** - Smaller PRs get faster, better reviews\n- **Explain the why** - Code shows what; description explains why\n- **Mark WIP early** - Use draft PRs for early feedback\n\n## Editing Existing PRs\n\nIf you need to update a PR after creation, use `gh api` instead of `gh pr edit`:\n\n```bash\n# Update PR description\ngh api -X PATCH repos\u002F{owner}\u002F{repo}\u002Fpulls\u002FPR_NUMBER -f body=\"$(cat \u003C\u003C'EOF'\nUpdated description here\nEOF\n)\"\n\n# Update PR title\ngh api -X PATCH repos\u002F{owner}\u002F{repo}\u002Fpulls\u002FPR_NUMBER -f title='new: Title here'\n\n# Update both\ngh api -X PATCH repos\u002F{owner}\u002F{repo}\u002Fpulls\u002FPR_NUMBER \\\n  -f title='new: Title' \\\n  -f body='New description'\n```\n\nNote: `gh pr edit` is currently broken due to GitHub's Projects (classic) deprecation.\n\n## References\n\n- [Sentry Code Review Guidelines](https:\u002F\u002Fdevelop.sentry.dev\u002Fengineering-practices\u002Fcode-review\u002F)\n- [Sentry Commit Messages](https:\u002F\u002Fdevelop.sentry.dev\u002Fengineering-practices\u002Fcommit-messages\u002F)\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# PR Writer\n\nCreate pull requests following Sentry's engineering practices.\n\n**Requires**: GitHub CLI (`gh`) authenticated and available.\n\n## When to Use\n- You are ready to open a pull request and need a structured description based on the committed branch diff.\n- You want the PR body to capture what changed, why it changed, and any reviewer context.\n- You are using GitHub CLI and need a repeatable PR-writing workflow rather than writing the description ad hoc.\n\n## Prerequisites\n\nBefore creating a PR, ensure all changes are committed. If there are uncommitted changes, run the `sentry-skills:commit` skill first to commit them properly.\n\n```bash\n# Check for uncommitted changes\ngit status --porcelain\n```\n\nIf the output shows any uncommitted changes (modified, added, or untracked files that should be included), invoke the `sentry-skills:commit` skill before proceeding.\n\n## Process\n\n### Step 1: Verify Branch State\n\n```bash\n# Detect the default branch — note the output for use in subsequent commands\ngh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'\n```\n\n```bash\n# Check current branch and status (substitute the detected branch name above for BASE)\ngit status\ngit log BASE..HEAD --oneline\n```\n\nEnsure:\n- All changes are committed\n- Branch is up to date with remote\n- Changes are rebased on the base branch if needed\n\n### Step 2: Analyze Changes\n\nReview what will be included in the PR:\n\n```bash\n# See all commits that will be in the PR (substitute detected branch name for BASE)\ngit log BASE..HEAD\n\n# See the full diff\ngit diff BASE...HEAD\n```\n\nUnderstand the scope and purpose of all changes before writing the description.\n\n### Step 3: Write the PR Description\n\nUse this structure for PR descriptions (ignoring any repository PR templates):\n\n```markdown\n\u003Cbrief description of what the PR does>\n\n\u003Cwhy these changes are being made - the motivation>\n\n\u003Calternative approaches considered, if any>\n\n\u003Cany additional context reviewers need>\n```\n\n**Do NOT include:**\n- \"Test plan\" sections\n- Checkbox lists of testing steps\n- Redundant summaries of the diff\n\n**Do include:**\n- Clear explanation of what and why\n- Links to relevant issues or tickets\n- Context that isn't obvious from the code\n- Notes on specific areas that need careful review\n\n### Step 4: Create the PR\n\n```bash\ngh pr create --draft --title \"\u003Ctype>(\u003Cscope>): \u003Cdescription>\" --body \"$(cat \u003C\u003C'EOF'\n\u003Cdescription body here>\nEOF\n)\"\n```\n\n**Title format** follows commit conventions:\n- `feat(scope): Add new feature`\n- `fix(scope): Fix the bug`\n- `ref: Refactor something`\n\n## PR Description Examples\n\n### Feature PR\n\n```markdown\nAdd Slack thread replies for alert notifications\n\nWhen an alert is updated or resolved, we now post a reply to the original\nSlack thread instead of creating a new message. This keeps related\nnotifications grouped and reduces channel noise.\n\nPreviously considered posting edits to the original message, but threading\nbetter preserves the timeline of events and works when the original message\nis older than Slack's edit window.\n\nRefs SENTRY-1234\n```\n\n### Bug Fix PR\n\n```markdown\nHandle null response in user API endpoint\n\nThe user endpoint could return null for soft-deleted accounts, causing\ndashboard crashes when accessing user properties. This adds a null check\nand returns a proper 404 response.\n\nFound while investigating SENTRY-5678.\n\nFixes SENTRY-5678\n```\n\n### Refactor PR\n\n```markdown\nExtract validation logic to shared module\n\nMoves duplicate validation code from the alerts, issues, and projects\nendpoints into a shared validator class. No behavior change.\n\nThis prepares for adding new validation rules in SENTRY-9999 without\nduplicating logic across endpoints.\n```\n\n## Issue References\n\nReference issues in the PR body:\n\n| Syntax | Effect |\n|--------|--------|\n| `Fixes #1234` | Closes GitHub issue on merge |\n| `Fixes SENTRY-1234` | Closes Sentry issue |\n| `Refs GH-1234` | Links without closing |\n| `Refs LINEAR-ABC-123` | Links Linear issue |\n\n## Guidelines\n\n- **One PR per feature\u002Ffix** - Don't bundle unrelated changes\n- **Keep PRs reviewable** - Smaller PRs get faster, better reviews\n- **Explain the why** - Code shows what; description explains why\n- **Mark WIP early** - Use draft PRs for early feedback\n\n## Editing Existing PRs\n\nIf you need to update a PR after creation, use `gh api` instead of `gh pr edit`:\n\n```bash\n# Update PR description\ngh api -X PATCH repos\u002F{owner}\u002F{repo}\u002Fpulls\u002FPR_NUMBER -f body=\"$(cat \u003C\u003C'EOF'\nUpdated description here\nEOF\n)\"\n\n# Update PR title\ngh api -X PATCH repos\u002F{owner}\u002F{repo}\u002Fpulls\u002FPR_NUMBER -f title='new: Title here'\n\n# Update both\ngh api -X PATCH repos\u002F{owner}\u002F{repo}\u002Fpulls\u002FPR_NUMBER \\\n  -f title='new: Title' \\\n  -f body='New description'\n```\n\nNote: `gh pr edit` is currently broken due to GitHub's Projects (classic) deprecation.\n\n## References\n\n- [Sentry Code Review Guidelines](https:\u002F\u002Fdevelop.sentry.dev\u002Fengineering-practices\u002Fcode-review\u002F)\n- [Sentry Commit Messages](https:\u002F\u002Fdevelop.sentry.dev\u002Fengineering-practices\u002Fcommit-messages\u002F)\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"description":7},"unknown","community","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fpr-writer",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill pr-writer",{"tool":41,"command":42},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill pr-writer",{"tool":44,"command":45},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill pr-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fpr-writer\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]