[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75HXW2YQCBDT2T5EPPTV5MS":3,"skill-same:01M75HXW2YQCBDT2T5EPPTV5MS":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75HXW2YQCBDT2T5EPPTV5MS","review-pr",null,"Review a pull request diff and write structured feedback to review.json for the workflow to publish. Use when reviewing a checked-out PR from local artifacts like pr_diff.txt and pr_description.txt and producing machine-readable review output instead of posting directly to GitHub.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Freview-pr\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: review-pr\ndescription: Review a pull request diff and write structured feedback to review.json for the workflow to publish. Use when reviewing a checked-out PR from local artifacts like pr_diff.txt and pr_description.txt and producing machine-readable review output instead of posting directly to GitHub.\n---\n\n# Review PR Skill\n\nReview the current pull request and write the output to `review.json`.\n\n## Context\n\n- The working directory is the PR branch checkout.\n- The workflow provides an annotated diff in `pr_diff.txt`.\n- The workflow provides the PR description in `pr_description.txt`.\n- Focus on files and lines changed by this PR.\n- Do not post comments or reviews to GitHub directly.\n\n## Review Scope\n\n- Prioritize correctness, security, error handling, and meaningful performance issues.\n- Include style or nit comments only when you can provide a concrete suggestion block.\n- If a concern involves untouched code, mention it in the summary instead of an inline comment.\n- Do not suggest adding test cases that only vary constructor inputs or struct fields when the existing test already covers the meaningful behavior. Only suggest new tests when they exercise a distinct code path or edge case.\n- When a PR is clearly a V0 or initial implementation, frame robustness suggestions (timeouts, retries, lifecycle management) as optional future work rather than blocking concerns, unless they risk correctness, security, or data loss.\n\n## Diff Line Annotations\n\nThe diff file uses these prefixes:\n\n- `[OLD:n]` for deleted lines on the old side. Use `\"LEFT\"`.\n- `[NEW:n]` for added lines on the new side. Use `\"RIGHT\"`.\n- `[OLD:n,NEW:m]` for unchanged context. Use `\"RIGHT\"` with line `m`.\n\n## Comment Requirements\n\nEvery comment body must start with one of these labels:\n\n- `🚨 [CRITICAL]` for bugs, security issues, crashes, or data loss.\n- `⚠️ [IMPORTANT]` for logic problems, edge cases, or missing error handling.\n- `💡 [SUGGESTION]` for worthwhile improvements or better patterns.\n- `🧹 [NIT]` for cleanup only when the comment includes a suggestion block.\n\nWrite comments with these constraints:\n\n- Be concise, direct, and actionable.\n- Do not add compliments or hedging.\n- Prefer single-line comments.\n- Keep ranges to at most 10 lines.\n- Restrict inline comments to valid changed lines in this PR.\n\n## Suggestion Blocks\n\nWhen proposing a code change, use:\n\n```suggestion\n\u003Creplacement code here>\n```\n\nRules:\n\n- Match the exact indentation of the original file.\n- Include only replacement code.\n- For multi-line suggestions, set `start_line` to the first line and `line` to the last line.\n\n## Output Format\n\nCreate `review.json` with this shape:\n\n```json\n{\n  \"summary\": \"## Overview\\n...\\n\\n## Concerns\\n- ...\\n\\n## Verdict\\nFound: 1 critical, 2 important, 3 suggestions\\n\\n**Request changes**\",\n  \"comments\": [\n    {\n      \"path\": \"path\u002Fto\u002Ffile\",\n      \"line\": 42,\n      \"side\": \"RIGHT\",\n      \"start_line\": 40,\n      \"body\": \"⚠️ [IMPORTANT] Short explanation\\n\\n```suggestion\\nreplacement\\n```\"\n    }\n  ]\n}\n```\n\nField rules:\n\n- `path` must be relative to the repository root.\n- `line` is required and must target the correct side.\n- `start_line` is optional and only for multi-line ranges.\n- `side` must be `\"LEFT\"` or `\"RIGHT\"`.\n\n## Summary Requirements\n\nThe `summary` must include:\n\n- A high-level overview of the PR.\n- Important concerns and any untouched-code concerns that could not be commented inline.\n- Issue counts in the format `Found: X critical, Y important, Z suggestions`.\n- A final recommendation of `Approve`, `Approve with nits`, or `Request changes`.\n\n## Final Checks\n\nBefore finishing:\n\n- Validate `review.json` with `jq`.\n- Fix invalid JSON if validation fails.\n- Confirm line numbers match the annotated diff.\n- Do not run `gh pr review`, `gh pr comment`, `gh api`, or any other command that posts to GitHub.\n\nYour only output is the final `review.json`.\n","# Review PR Skill\n\nReview the current pull request and write the output to `review.json`.\n\n## Context\n\n- The working directory is the PR branch checkout.\n- The workflow provides an annotated diff in `pr_diff.txt`.\n- The workflow provides the PR description in `pr_description.txt`.\n- Focus on files and lines changed by this PR.\n- Do not post comments or reviews to GitHub directly.\n\n## Review Scope\n\n- Prioritize correctness, security, error handling, and meaningful performance issues.\n- Include style or nit comments only when you can provide a concrete suggestion block.\n- If a concern involves untouched code, mention it in the summary instead of an inline comment.\n- Do not suggest adding test cases that only vary constructor inputs or struct fields when the existing test already covers the meaningful behavior. Only suggest new tests when they exercise a distinct code path or edge case.\n- When a PR is clearly a V0 or initial implementation, frame robustness suggestions (timeouts, retries, lifecycle management) as optional future work rather than blocking concerns, unless they risk correctness, security, or data loss.\n\n## Diff Line Annotations\n\nThe diff file uses these prefixes:\n\n- `[OLD:n]` for deleted lines on the old side. Use `\"LEFT\"`.\n- `[NEW:n]` for added lines on the new side. Use `\"RIGHT\"`.\n- `[OLD:n,NEW:m]` for unchanged context. Use `\"RIGHT\"` with line `m`.\n\n## Comment Requirements\n\nEvery comment body must start with one of these labels:\n\n- `🚨 [CRITICAL]` for bugs, security issues, crashes, or data loss.\n- `⚠️ [IMPORTANT]` for logic problems, edge cases, or missing error handling.\n- `💡 [SUGGESTION]` for worthwhile improvements or better patterns.\n- `🧹 [NIT]` for cleanup only when the comment includes a suggestion block.\n\nWrite comments with these constraints:\n\n- Be concise, direct, and actionable.\n- Do not add compliments or hedging.\n- Prefer single-line comments.\n- Keep ranges to at most 10 lines.\n- Restrict inline comments to valid changed lines in this PR.\n\n## Suggestion Blocks\n\nWhen proposing a code change, use:\n\n```suggestion\n\u003Creplacement code here>\n```\n\nRules:\n\n- Match the exact indentation of the original file.\n- Include only replacement code.\n- For multi-line suggestions, set `start_line` to the first line and `line` to the last line.\n\n## Output Format\n\nCreate `review.json` with this shape:\n\n```json\n{\n  \"summary\": \"## Overview\\n...\\n\\n## Concerns\\n- ...\\n\\n## Verdict\\nFound: 1 critical, 2 important, 3 suggestions\\n\\n**Request changes**\",\n  \"comments\": [\n    {\n      \"path\": \"path\u002Fto\u002Ffile\",\n      \"line\": 42,\n      \"side\": \"RIGHT\",\n      \"start_line\": 40,\n      \"body\": \"⚠️ [IMPORTANT] Short explanation\\n\\n```suggestion\\nreplacement\\n```\"\n    }\n  ]\n}\n```\n\nField rules:\n\n- `path` must be relative to the repository root.\n- `line` is required and must target the correct side.\n- `start_line` is optional and only for multi-line ranges.\n- `side` must be `\"LEFT\"` or `\"RIGHT\"`.\n\n## Summary Requirements\n\nThe `summary` must include:\n\n- A high-level overview of the PR.\n- Important concerns and any untouched-code concerns that could not be commented inline.\n- Issue counts in the format `Found: X critical, Y important, Z suggestions`.\n- A final recommendation of `Approve`, `Approve with nits`, or `Request changes`.\n\n## Final Checks\n\nBefore finishing:\n\n- Validate `review.json` with `jq`.\n- Fix invalid JSON if validation fails.\n- Confirm line numbers match the annotated diff.\n- Do not run `gh pr review`, `gh pr comment`, `gh api`, or any other command that posts to GitHub.\n\nYour only output is the final `review.json`.\n",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Freview-pr",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill review-pr",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill review-pr",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill review-pr","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Freview-pr\u002FSKILL.md",true,[],[47,54,61,70,77,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]