[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78BYNGHSRPCBN89ZZPW2ASE":3,"skill-same:01M78BYNGHSRPCBN89ZZPW2ASE":51},{"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":6,"updatedAt":30,"install":31,"resources":44},"01M78BYNGHSRPCBN89ZZPW2ASE","write-pr-description",null,"Draft or revise a standard pull-request description from the current repository's PR template and actual branch changes. Use when asked to write, generate, prepare, update, or improve a PR body, pull-request summary, testing notes, reviewer context, or checklist for a code change.","adriancodes\u002Fskills","adriancodes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F940414?v=4","01M6NJ91CRRXPC6RRKWM4CVEGJ","Adrian Martin","01M78BV1DGXZ4VG3VVC30VH0MC",1,"MIT","https:\u002F\u002Fgithub.com\u002Fadriancodes\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-skill\u002Fevals\u002Fresults\u002Fopportunity\u002Fdiscovery-cheaper\u002Fnone\u002Frun-1\u002Fartifacts\u002Fwrite-pr-description\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: write-pr-description\ndescription: Draft or revise a standard pull-request description from the current repository's PR template and actual branch changes. Use when asked to write, generate, prepare, update, or improve a PR body, pull-request summary, testing notes, reviewer context, or checklist for a code change.\n---\n\n# Write a PR Description\n\n## Gather evidence\n\n1. Locate repository instructions and pull-request templates before drafting. Search tracked and hidden paths, especially `AGENTS.md`, `.github\u002FPULL_REQUEST_TEMPLATE.md`, `.github\u002Fpull_request_template.md`, `.github\u002FPULL_REQUEST_TEMPLATE\u002F`, `docs\u002F`, and contributor documentation. If several templates exist, select the one matching the change type; ask only when the choice materially changes the result.\n2. Determine the comparison base from user input, branch configuration, or the repository's default branch. State the assumed base if it cannot be established reliably.\n3. Inspect the branch diff, changed-file summary, and relevant commits against that base. Read enough changed code and tests to explain behavior and verification accurately. Do not infer the PR solely from commit messages.\n4. Check issue references or user-provided context. Never invent ticket numbers, test results, screenshots, rollout details, or breaking-change claims.\n\nPrefer read-only commands such as:\n\n```sh\nrg --files -uu | rg '(^|\u002F)(AGENTS\\.md|PULL_REQUEST_TEMPLATE|pull_request_template|CONTRIBUTING)'\ngit status --short\ngit diff --stat \u003Cbase>...HEAD\ngit diff \u003Cbase>...HEAD\ngit log --oneline \u003Cbase>..HEAD\n```\n\n## Draft against the repository template\n\n- Preserve the template's section order, headings, checklist wording, comments, and required markers. Treat it as the output schema rather than replacing it with a generic format.\n- Fill every applicable section with concise, reviewer-oriented facts. Explain what changed, why it changed, meaningful implementation choices, user impact, risks, and validation where the template asks for them.\n- Mark checklist items complete only when supported by evidence. Leave unsupported items unchecked. Use `N\u002FA` with a short reason only when the template permits it.\n- Keep HTML comments when the result is intended to be pasted directly into a PR and the comments provide author guidance or automation markers. Omit purely instructional comments only when the user requests a clean rendered version.\n- Describe tests as commands or checks actually run. If none were run or their status is unknown, say so plainly and give the reason when known.\n- Mention screenshots only for visible UI changes and never fabricate them. Retain the template's placeholder when screenshots still need to be supplied.\n- Use issue-closing syntax only when the referenced issue and desired relationship are known.\n\nIf no repository template exists, use this compact fallback:\n\n```markdown\n## Summary\n\n- \u003Cwhat changed and why>\n\n## Testing\n\n- \u003Cverified check, or \"Not run (reason)\">\n\n## Risks\n\n- \u003Crisk and mitigation, or \"None identified\">\n```\n\n## Verify and deliver\n\nCross-check every material statement against the diff, tests, or user context. Ensure no template section was silently dropped and no placeholder is presented as completed work. Return a paste-ready Markdown PR body unless the user explicitly asks to write it to a file or publish it. Do not create or update a remote pull request without explicit authorization.\n","# Write a PR Description\n\n## Gather evidence\n\n1. Locate repository instructions and pull-request templates before drafting. Search tracked and hidden paths, especially `AGENTS.md`, `.github\u002FPULL_REQUEST_TEMPLATE.md`, `.github\u002Fpull_request_template.md`, `.github\u002FPULL_REQUEST_TEMPLATE\u002F`, `docs\u002F`, and contributor documentation. If several templates exist, select the one matching the change type; ask only when the choice materially changes the result.\n2. Determine the comparison base from user input, branch configuration, or the repository's default branch. State the assumed base if it cannot be established reliably.\n3. Inspect the branch diff, changed-file summary, and relevant commits against that base. Read enough changed code and tests to explain behavior and verification accurately. Do not infer the PR solely from commit messages.\n4. Check issue references or user-provided context. Never invent ticket numbers, test results, screenshots, rollout details, or breaking-change claims.\n\nPrefer read-only commands such as:\n\n```sh\nrg --files -uu | rg '(^|\u002F)(AGENTS\\.md|PULL_REQUEST_TEMPLATE|pull_request_template|CONTRIBUTING)'\ngit status --short\ngit diff --stat \u003Cbase>...HEAD\ngit diff \u003Cbase>...HEAD\ngit log --oneline \u003Cbase>..HEAD\n```\n\n## Draft against the repository template\n\n- Preserve the template's section order, headings, checklist wording, comments, and required markers. Treat it as the output schema rather than replacing it with a generic format.\n- Fill every applicable section with concise, reviewer-oriented facts. Explain what changed, why it changed, meaningful implementation choices, user impact, risks, and validation where the template asks for them.\n- Mark checklist items complete only when supported by evidence. Leave unsupported items unchecked. Use `N\u002FA` with a short reason only when the template permits it.\n- Keep HTML comments when the result is intended to be pasted directly into a PR and the comments provide author guidance or automation markers. Omit purely instructional comments only when the user requests a clean rendered version.\n- Describe tests as commands or checks actually run. If none were run or their status is unknown, say so plainly and give the reason when known.\n- Mention screenshots only for visible UI changes and never fabricate them. Retain the template's placeholder when screenshots still need to be supplied.\n- Use issue-closing syntax only when the referenced issue and desired relationship are known.\n\nIf no repository template exists, use this compact fallback:\n\n```markdown\n## Summary\n\n- \u003Cwhat changed and why>\n\n## Testing\n\n- \u003Cverified check, or \"Not run (reason)\">\n\n## Risks\n\n- \u003Crisk and mitigation, or \"None identified\">\n```\n\n## Verify and deliver\n\nCross-check every material statement against the diff, tests, or user context. Ensure no template section was silently dropped and no placeholder is presented as completed work. Return a paste-ready Markdown PR body unless the user explicitly asks to write it to a file or publish it. Do not create or update a remote pull request without explicit authorization.\n",{"name":5,"description":7},"main","9a3fe345285b86c3071deb2ecb302dff99a855b8","skills\u002Fcreate-skill\u002Fevals\u002Fresults\u002Fopportunity\u002Fdiscovery-cheaper\u002Fnone\u002Frun-1\u002Fartifacts\u002Fwrite-pr-description",0,"https:\u002F\u002Fgithub.com\u002Fadriancodes\u002Fskills","https:\u002F\u002Fgithub.com\u002Fadriancodes","2026-11-12 06:06:49",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add adriancodes\u002Fskills --skill write-pr-description",{"tool":37,"command":38},"bunx","bunx skills add adriancodes\u002Fskills --skill write-pr-description",{"tool":40,"command":41},"pnpm","pnpm dlx skills add adriancodes\u002Fskills --skill write-pr-description","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fadriancodes\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-skill\u002Fevals\u002Fresults\u002Fopportunity\u002Fdiscovery-cheaper\u002Fnone\u002Frun-1\u002Fartifacts\u002Fwrite-pr-description\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",224,"https:\u002F\u002Fgithub.com\u002Fadriancodes\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-skill\u002Fevals\u002Fresults\u002Fopportunity\u002Fdiscovery-cheaper\u002Fnone\u002Frun-1\u002Fartifacts\u002Fwrite-pr-description\u002Fagents\u002Fopenai.yaml",[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M78C1QNZAXX06QMDJ8R65TTV","write-agent-instructions","Make the smallest evidence-backed change to persistent project instructions and test downstream behavior.","https:\u002F\u002Fgithub.com\u002Fadriancodes\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-agent-instructions\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M78C1K3QVP67S0TRERZ5YNGB","verify-work","Use when a finished, runnable artifact (a script, config, parser, prompt, or CLI, not a diff under review) must survive hostile input before shipping: the user asks to \"verify this script\", \"find the loopholes\", \"test this properly against bad input\", or asks \"is this ready to ship\" about one. Also when a shipped artifact failed on an input nobody tried, or when verification so far is a happy-path smoke test.","https:\u002F\u002Fgithub.com\u002Fadriancodes\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify-work\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M78C1DDYDEQ7H1HNW84VW1V3","understand-codebase","Use when the user asks to \"understand this codebase\", \"how does this feature work in this repo?\", \"trace this feature through the code\", or needs onboarding, an architecture explanation, or answers about unfamiliar code. Also use for read-only code-path questions before a change.","https:\u002F\u002Fgithub.com\u002Fadriancodes\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Funderstand-codebase\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M78C18C6TG62PY1PQBGCSKXR","tdd","Use when writing or changing production behavior: implementing a feature, fixing a bug whose cause is already known, or altering stored, transformed, migrated, serialized, or externally transmitted data. Also use when a user says \"use TDD\", \"test first\", or \"red-green-refactor\", and when code is being written before a failing test. For a failure whose cause is unknown, diagnose first.","https:\u002F\u002Fgithub.com\u002Fadriancodes\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Ftdd\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M78C151714X4Z3VQW5F23FZW","simplify-code","Use when the user asks to \"simplify this code\", \"remove the fluff\", or \"clean up this over-engineered module\", or wants working code that is bloated, duplicated, over-abstracted, or dependency-heavy reduced without changing behavior.","https:\u002F\u002Fgithub.com\u002Fadriancodes\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fsimplify-code\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M78C127TPYNJBX0B4BCF7246","review-session","Review an agent session for evidence-backed friction and the smallest measurable remedies.","https:\u002F\u002Fgithub.com\u002Fadriancodes\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Freview-session\u002FSKILL.md",[],[]]