[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BMM72YPZEE32034YTE7804":3,"skill-same:01M7BMM72YPZEE32034YTE7804":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":20,"frontMatter":21,"refName":22,"commitSha":23,"skillDirectory":24,"forksCount":25,"repositoryHtmlUrl":26,"repositoryHomepageUrl":27,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7BMM72YPZEE32034YTE7804","github-pr",null,"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-AI-模型服务\u002FYYC3-AI-模型服务-zeroclaw\u002F.claude\u002Fskills\u002Fgithub-pr\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"# Skill: github-pr\n\nOpen or update a GitHub Pull Request for ZeroClaw. Handles creating new PRs with a fully filled-out template body, and updating existing PRs (title, body sections, labels, comments). Use this skill whenever the user wants to open a PR, create a pull request, update a PR, edit PR description, add labels to a PR, or sync a PR after new commits — even if they don't say \"PR\" explicitly (e.g., \"submit this for review\", \"push and open for merge\").\n\n## Instructions\n\nThis skill supports two modes: **Open** (create a new PR) and **Update** (edit an existing PR). Detect the mode from context — if there's already an open PR for the current branch and the user didn't say \"open a new PR\", default to update mode.\n\nThe PR template at `.github\u002Fpull_request_template.md` is the source of truth for the PR body structure. Read it every time — never assume or hardcode section names, fields, or their order. The template may change over time and the skill should always reflect its current state.\n\n---\n\n## Shared: Read the PR Template\n\nBefore opening or updating a PR body, read `.github\u002Fpull_request_template.md` and parse it to understand:\n\n- The `## ` section headers (these are the top-level sections of the PR body)\n- The bullet points, fields, and prompts within each section\n- Which sections are marked `(required)` vs optional\u002Frecommended\n- Any inline formatting conventions (backtick options, Yes\u002FNo fields, etc.)\n\nThis parsed structure drives how you fill, present, and edit the PR body.\n\n## Shared: Authorship Hygiene\n\nZeroClaw PR bodies and landed commit-message tails should not include bot or AI\nattribution such as `Co-authored-by: Claude \u003C...>`, `Co-authored-by: Codex\n\u003C...>`, or generated footers like `Created with Claude Code` \u002F `Generated with\nClaude Code`.\n\nBefore opening a PR, scan local commit messages and the drafted PR body:\n\n```bash\ngit log origin\u002Fmaster..HEAD --format=%B | rg -i '(^[[:space:]]*(Co-authored-by|Co-Authored-By):.*(Claude|Codex|ChatGPT|Copilot|GitHub Copilot|Gemini|\\[bot\\]|dependabot|github-actions|web-flow|blacksmith|noreply@(anthropic|openai)\\.com)|^[[:space:]]*(Created with Claude Code|Generated with Claude Code)[[:space:]]*$)'\n```\n\nBefore showing or submitting PR text, remove bot\u002FAI co-author trailers and\ngenerated tool footers. If local unpublished commits contain those footers, tell\nthe user and ask before rewriting commit history. Do not rewrite a pushed branch\nor contributor branch solely for attribution cleanup without explicit approval.\n\n---\n\n## Mode: Open a New PR\n\n### Step 1: Gather Context\n\nCollect information to pre-fill the PR body. Run these in parallel:\n\n```bash\n# Branch and commit context\ngit branch --show-current\ngit log master..HEAD --oneline\ngit diff master...HEAD --stat\n\n# Check if branch is pushed\ngit rev-parse --abbrev-ref --symbolic-full-name @{u} 2>\u002Fdev\u002Fnull\n\n# Environment (for validation evidence)\nrustc --version 2>\u002Fdev\u002Fnull\n```\n\nAlso review the changed files and commit messages to understand the nature of the change (bug fix, feature, refactor, docs, chore, etc.) and which subsystems are affected.\n\n### Step 1a: Run the Validation Battery (required before drafting)\n\nBefore drafting the PR body, actually run the commands the PR template's \"Validation Evidence\" section asks for. Do not paraphrase results, do not write \"tests pass\" from memory, do not skip on the assumption that CI will catch it. The evidence section needs literal output from a real local run:\n\n```bash\ncargo fmt --all -- --check\ncargo clippy --all-targets -- -D warnings\ncargo test\n```\n\nFor docs-only changes, replace the Rust battery with markdown lint and link-integrity checks per `AGENTS.md`, and if touching bootstrap scripts add `bash -n install.sh`.\n\nCapture the tail of each command's output. You will paste the relevant excerpts (last 5–10 lines, any failures, any warnings) into the PR body's Validation Evidence section. If a command fails, stop and fix the underlying issue before drafting the PR — do not draft a PR on a broken tree.\n\nIf a command is intentionally skipped (e.g., platform-blocked), note it explicitly in the evidence with a one-line reason. \"Skipped\" without explanation is not acceptable.\n\nIf the validation run emits any `WARN` \u002F `ERROR` \u002F `warning:` lines, investigate them the same way a reviewer would: confirm pre-existing on master with root cause, or flag as something to address before opening. Do not ship a PR whose own local validation surfaces warnings you cannot explain.\n\n### Step 2: Pre-Fill the Template\n\nWhen populating the \"Validation Evidence\" section, paste the actual tail output of the commands from Step 1a — do not paraphrase. The reviewer will be looking for literal strings to diff against their own validation run.\n\nUsing the parsed template structure and gathered context, draft a complete PR body:\n\n- For each `## ` section from the template, fill in the bullet points and fields based on context from the commits, diff, and changed files.\n- Use the field descriptions and placeholder text in the template as guidance for what each field expects.\n- For Yes\u002FNo fields, infer from the diff (e.g., if no files in `src\u002Fsecurity\u002F` changed, security impact is likely all No).\n- For required sections, always provide a substantive answer. For optional sections, fill if there's enough context, otherwise leave the template prompts in place.\n- Draft a conventional commit-style PR title based on the changes (e.g., `feat(provider): add retry budget override`, `fix(channel): handle disconnect gracefully`, `chore(ci): update workflow targets`).\n- Apply the shared authorship-hygiene check before showing or submitting the PR\n  body.\n\n### Step 3: Present Draft for Review\n\nShow the user the complete draft:\n\n```\n## PR Draft: \u003Ctitle>\n**Branch**: \u003Chead> -> master\n**Labels**: \u003Csuggested labels>\n\n\u003Cfull body with all sections filled>\n```\n\nAsk the user to review: \"Here's the pre-filled PR. Review and let me know what to change, or say 'submit' to open it.\"\n\nIterate on changes until the user approves.\n\n### Step 4: Push and Create\n\n1. If the branch isn't pushed yet, push it:\n   ```bash\n   git push -u origin \u003Cbranch>\n   ```\n\n2. Create the PR using a HEREDOC for the body:\n   ```bash\n   gh pr create --title \"\u003Ctitle>\" --base master --body \"$(cat \u003C\u003C'PR_BODY_EOF'\n   \u003Cfull body>\n   PR_BODY_EOF\n   )\"\n   ```\n\n3. If labels were agreed on, add them:\n   ```bash\n   gh pr edit \u003Cnumber> --add-label \"\u003Clabel1>,\u003Clabel2>\"\n   ```\n\n4. Return the PR URL to the user.\n\n---\n\n## Mode: Update an Existing PR\n\n### Step 1: Identify the PR\n\n1. **If a PR number or URL is given**: use that directly.\n2. **If on a branch with an open PR**: auto-detect:\n   ```bash\n   gh pr view --json number,title,body,labels,state,author,url,headRefName 2>\u002Fdev\u002Fnull\n   ```\n3. **If neither**: ask the user for the PR number.\n\nVerify the current user is the PR author:\n```bash\nCURRENT_USER=$(gh api user --jq '.login')\nPR_AUTHOR=$(gh pr view \u003Cnumber> --json author --jq '.author.login')\n```\nIf not the author, stop and inform the user.\n\n### Step 2: Fetch Current State\n\n```bash\ngh pr view \u003Cnumber> --json number,title,body,labels,state,baseRefName,headRefName,url,author,reviewDecision,statusCheckRollup,commits\n```\n\nDisplay a summary:\n```\n## PR #\u003Cnumber>: \u003Ctitle>\n**State**: \u003Copen\u002Fclosed\u002Fmerged>\n**Branch**: \u003Chead> -> \u003Cbase>\n**Labels**: \u003Clabel list>\n**Checks**: \u003Cpass\u002Ffail\u002Fpending>\n**URL**: \u003Curl>\n```\n\n### Step 3: Determine What to Update\n\nSupport these operations:\n\n| Operation | How |\n|---|---|\n| **Edit title** | `gh pr edit \u003Cnumber> --title \"\u003Cnew title>\"` |\n| **Edit full body** | `gh pr edit \u003Cnumber> --body \"\u003Cnew body>\"` |\n| **Add labels** | `gh pr edit \u003Cnumber> --add-label \"\u003Clabel1>,\u003Clabel2>\"` |\n| **Remove labels** | `gh pr edit \u003Cnumber> --remove-label \"\u003Clabel1>\"` |\n| **Edit specific section** | Parse body by `## ` headers, modify target section, re-submit full body |\n| **Add a comment** | `gh pr comment \u003Cnumber> --body \"\u003Ccomment>\"` |\n| **Link an issue** | Edit the linked-issue section in the body |\n| **Smart update after new commits** | Re-analyze and suggest section updates |\n\n### Step 4: Handle Body Section Edits\n\nWhen editing a specific section:\n\n1. Parse the current PR body into sections by `## ` headers\n2. Match the user's request to the corresponding section from the template\n3. Show the current content of that section and the proposed replacement\n4. On confirmation, modify only that section, reconstruct the full body, and submit\n\n### Step 5: Smart Update After New Commits\n\nWhen the user wants to sync the PR description after pushing new changes:\n\n1. Identify new commits:\n   ```bash\n   gh pr view \u003Cnumber> --json commits --jq '.commits[].messageHeadline'\n   git log \u003Cbase>..\u003Chead> --oneline\n   git diff \u003Cbase>...\u003Chead> --stat\n   ```\n\n2. Re-read the PR template. Analyze which sections are now stale based on the new changes — use the template's section names and field descriptions to identify what needs updating rather than relying on hardcoded assumptions.\n\n3. **If any of the new commits touch code (not pure docs)**, re-run the validation battery from Step 1a before updating the Validation Evidence section. Stale validation evidence is worse than no evidence — it misleads the reviewer.\n\n4. Apply the shared authorship-hygiene check before showing or submitting the\n   update.\n\n5. Present proposed updates section-by-section and confirm before applying.\n\n### Step 6: Apply Updates\n\nFor title\u002Flabel changes, use direct `gh pr edit` flags.\n\nFor body edits, use a HEREDOC:\n```bash\ngh pr edit \u003Cnumber> --body \"$(cat \u003C\u003C'PR_BODY_EOF'\n\u003Cfull updated body>\nPR_BODY_EOF\n)\"\n```\n\nFor comments:\n```bash\ngh pr comment \u003Cnumber> --body \"$(cat \u003C\u003C'COMMENT_EOF'\n\u003Ccomment text>\nCOMMENT_EOF\n)\"\n```\n\n### Step 7: Confirm\n\nFetch and display the updated state:\n```bash\ngh pr view \u003Cnumber> --json number,title,labels,url\n```\n\nReturn the PR URL.\n\n---\n\n## Important Rules\n\n- **Always read `.github\u002Fpull_request_template.md`** before filling or editing a PR body. Never assume section names, fields, or structure — derive everything from the template. It's the source of truth and may change.\n- **For updates, only modify requested sections.** Preserve everything else exactly as-is.\n- **Always show diffs before applying body edits.** Present current vs proposed for each changed section.\n- **Never include personal\u002Fsensitive data** in PR content per ZeroClaw's privacy contract.\n- **Never include bot\u002FAI attribution footers** in PR body text. Follow\n  **Shared: Authorship Hygiene** before showing or submitting PR text.\n- **For label changes**, only use labels that exist in the repository. Check with `gh label list` if unsure.\n- **Fetch the latest body before editing** to avoid clobbering concurrent changes.\n- **For new PRs**, push the branch before creating (with `-u` to set upstream tracking).\n",{},"main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-AI-模型服务\u002FYYC3-AI-模型服务-zeroclaw\u002F.claude\u002Fskills\u002Fgithub-pr",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":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill github-pr",{"tool":37,"command":38},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill github-pr",{"tool":40,"command":41},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill github-pr","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-AI-模型服务\u002FYYC3-AI-模型服务-zeroclaw\u002F.claude\u002Fskills\u002Fgithub-pr\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"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":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"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":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"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":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"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",[],[]]