[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EQJVCXNB1WFCMFJ8FSTY56":3,"skill-same:01M7EQJVCXNB1WFCMFJ8FSTY56":46},{"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":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7EQJVCXNB1WFCMFJ8FSTY56","pr-feedback",null,"Fetches PR review feedback and inline comments, categorizes them, and presents options to the user. Use when the user asks to get, read, address, or fix review comments on a pull request.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fpr-feedback\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: pr-feedback\ndescription: Fetches PR review feedback and inline comments, categorizes them, and presents options to the user. Use when the user asks to get, read, address, or fix review comments on a pull request.\n---\n\n# PR Review Feedback\n\nFetch PR review feedback and inline comments, categorize them, and present options to fix.\n\n## Process\n\n### 1. Determine the PR Number\n\nAuto-detect from the current branch:\n\n```bash\ngh pr view --json number -q .number\n```\n\nIf that fails (detached HEAD, no tracking branch), ask the user for the PR number or URL.\n\n### 2. Fetch All Feedback\n\nUse the bundled script to fetch reviews, inline comments, and issue-level comments in one shot:\n\n```bash\nbash .agents\u002Fskills\u002Fpr-feedback\u002Ffetch-pr-feedback.sh \u003Cnumber> [--repo owner\u002Frepo]\n```\n\n- Omit `\u003Cnumber>` to auto-detect from the current branch.\n- Use `--repo` when the PR is in a different repo than the current directory.\n\nThe script returns JSON with three arrays:\n- `reviews` — top-level review summaries (non-empty bodies only)\n- `inline_comments` — unresolved thread comments with `upvotes`\u002F`downvotes` arrays (usernames who reacted), `outdated` flag, and `diffHunk` on the first comment in each thread\n- `comments` — issue-level comments\n\n### 3. Summarize and Present to the User\n\nRead all the feedback, use your judgment to group related items, and present a numbered list of things to address. Keep each item to one line. Put the most impactful items first.\n\nUse upvotes, downvotes, and the PR author's own replies to determine priority:\n\n- **Upvoted by the PR author**: This signals agreement — recommend fixing it.\n- **Author replied agreeing** (e.g. \"good point\", \"I'll fix\", \"makes sense\"): Same as an upvote — recommend fixing it.\n- **Upvoted by other reviewers** (not the author): Signals community agreement the issue matters — lean toward recommending.\n- **No signal from the author**: Present as a suggestion but don't assume it should be fixed.\n- **Author replied disagreeing or explaining**: Present for context but mark as \"discussed — likely skip\".\n- **Outdated comments**: Group separately at the end — these may have been addressed by subsequent pushes.\n\nWhen presenting the list, annotate items you recommend fixing (based on the signals above) so the user can quickly confirm \"all recommended\" or cherry-pick.\n\n### 4. Fix What the User Selects\n\nAddress only the confirmed items. After fixing, briefly note what changed — one line per item.\n\n## Rules\n\n- Always auto-detect the PR number before asking the user.\n- Never fix anything before presenting the list and getting user confirmation.\n- If the output is too large to parse in one shot, focus on non-outdated comments first.\n","# PR Review Feedback\n\nFetch PR review feedback and inline comments, categorize them, and present options to fix.\n\n## Process\n\n### 1. Determine the PR Number\n\nAuto-detect from the current branch:\n\n```bash\ngh pr view --json number -q .number\n```\n\nIf that fails (detached HEAD, no tracking branch), ask the user for the PR number or URL.\n\n### 2. Fetch All Feedback\n\nUse the bundled script to fetch reviews, inline comments, and issue-level comments in one shot:\n\n```bash\nbash .agents\u002Fskills\u002Fpr-feedback\u002Ffetch-pr-feedback.sh \u003Cnumber> [--repo owner\u002Frepo]\n```\n\n- Omit `\u003Cnumber>` to auto-detect from the current branch.\n- Use `--repo` when the PR is in a different repo than the current directory.\n\nThe script returns JSON with three arrays:\n- `reviews` — top-level review summaries (non-empty bodies only)\n- `inline_comments` — unresolved thread comments with `upvotes`\u002F`downvotes` arrays (usernames who reacted), `outdated` flag, and `diffHunk` on the first comment in each thread\n- `comments` — issue-level comments\n\n### 3. Summarize and Present to the User\n\nRead all the feedback, use your judgment to group related items, and present a numbered list of things to address. Keep each item to one line. Put the most impactful items first.\n\nUse upvotes, downvotes, and the PR author's own replies to determine priority:\n\n- **Upvoted by the PR author**: This signals agreement — recommend fixing it.\n- **Author replied agreeing** (e.g. \"good point\", \"I'll fix\", \"makes sense\"): Same as an upvote — recommend fixing it.\n- **Upvoted by other reviewers** (not the author): Signals community agreement the issue matters — lean toward recommending.\n- **No signal from the author**: Present as a suggestion but don't assume it should be fixed.\n- **Author replied disagreeing or explaining**: Present for context but mark as \"discussed — likely skip\".\n- **Outdated comments**: Group separately at the end — these may have been addressed by subsequent pushes.\n\nWhen presenting the list, annotate items you recommend fixing (based on the signals above) so the user can quickly confirm \"all recommended\" or cherry-pick.\n\n### 4. Fix What the User Selects\n\nAddress only the confirmed items. After fixing, briefly note what changed — one line per item.\n\n## Rules\n\n- Always auto-detect the PR number before asking the user.\n- Never fix anything before presenting the list and getting user confirmation.\n- If the output is too large to parse in one shot, focus on non-outdated comments first.\n",{"name":5,"description":7},"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fpr-feedback",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill pr-feedback",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill pr-feedback",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill pr-feedback","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fpr-feedback\u002FSKILL.md",true,[],[47,54,61,68,76,83],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7EXRM12046G0GM1WGMMFXCN","ci-cd-and-automation","Automates CI\u002FCD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fci-cd-and-automation\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7EXRFYYSJ3Y15AGPDDEWWQD","chrome-devtools","Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to `--slim` mode (MCP configuration).","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fchrome-devtools\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7EXR6EYPE4X5X1BTAE6QJRV","chrome-cdp","Drive a real Chrome via the Chrome DevTools Protocol (CDP). Ensures a\ndebuggable Chrome is running (launching it if needed) so the agent can\nnavigate, read page content, inspect the DOM, run JavaScript, and take\nscreenshots — without the user typing any launch command. Includes a\nfirst-class \"review a live running app\" flow: point Chrome at the app under\ndevelopment and inspect\u002Fscreenshot the REAL page (what a static-artifact tool\ncannot do). Backed by Glimpse and the chrome-devtools MCP server. Use when\nasked to \"use chrome\", \"open chrome\", \"drive my browser\", \"read the page in\nchrome\", \"review the running app\", \"screenshot the app\", or \"\u002Fchrome-cdp\".","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fchrome-cdp\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7EXR1Y7E79KQKG4J798XGH6","check-identity-pack","Run an AFP 100-point or AUSTRAC safe-harbour identity check over a set of documents, and report exactly what's missing. Use when the user asks to check identity documents, verify someone's ID for onboarding, or assess whether a document pack satisfies Australian identity requirements.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fcheck-identity-pack\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},"01M7EXQXW7C7PGREJW9ZZTZ16H","changelog","Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fchangelog\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},"01M7EXQMH2ZME3ANN8Q8MEWPFB","cellxgene-census","Query the CZ CELLxGENE Census programmatically for versioned public single-cell and spatial transcriptomics data. Use when you need population-scale cell metadata, gene expression slices, Census summary counts, source H5AD URIs\u002Fdownloads, embeddings, spatial Census data, or reference atlas comparisons across organisms, tissues, diseases, assays, and cell types. For analyzing your own local single-cell data use scanpy, anndata, or scvi-tools.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fcellxgene-census\u002FSKILL.md",[],[]]