[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B33RBZ37FKMFWP9J4451R8":3,"skill-same:01M7B33RBZ37FKMFWP9J4451R8":47},{"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":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7B33RBZ37FKMFWP9J4451R8","people-first-pr-descriptions",null,"Write and update pull-request titles and descriptions for technical work. Use whenever creating, revising, or reviewing a PR body, release-style PR summary, or reviewer-facing change explanation—even if the user only says “open a PR,” “update the PR,” “make this understandable,” or provides technical notes. Put people, user outcomes, and why first; move implementation detail and validation after the plain-language explanation.","gethamster\u002Fskills","gethamster","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F215697643?v=4","01M7B2R6PGB3SDZZ71E0WE2S74","Hamster","01M7B2R6Q21HWJRXZZWB78BNDG",4,"MIT","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F.experimental\u002Fpeople-first-pr-descriptions\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: people-first-pr-descriptions\ndescription: \"Write and update pull-request titles and descriptions for technical work. Use whenever creating, revising, or reviewing a PR body, release-style PR summary, or reviewer-facing change explanation—even if the user only says “open a PR,” “update the PR,” “make this understandable,” or provides technical notes. Put people, user outcomes, and why first; move implementation detail and validation after the plain-language explanation.\"\n---\n\n# People-first pull-request descriptions\n\nWrite PR descriptions for readers who need to understand the change before they need to inspect the code: product, support, QA, designers, leadership, and reviewers outside the subsystem.\n\n## Required companion workflow\n\nBefore opening a pull request or marking one ready for review, complete [Hamster Pre-PR Review](..\u002Fhamster-pre-pr-review\u002FSKILL.md). It makes this people-first description mandatory and verifies the branch, diff, blockers, and quality gates.\n\n## Ground the description first\n\nBefore writing or updating a PR body:\n\n1. Read the current PR body, diff, review feedback, and validation evidence.\n2. Identify the user-visible or operational problem in one plain sentence.\n3. Distinguish confirmed behavior from pending validation, limits, and follow-up work.\n4. Preserve an existing Hamster brief link\u002Fpath and any facts that remain accurate.\n\nDo not claim a test, CI run, deployment, live canary, migration, or user outcome unless it was actually observed.\n\n## Default structure\n\nUse this order unless the PR is truly trivial:\n\n```markdown\n## What changed\nOne or two plain-language sentences about the capability or behavior.\n\n## Why it matters\nDescribe the prior user, customer, operator, or maintainer problem. Use a concrete failure mode when useful.\n\n## How it works\nExplain the approach at a conceptual level. Prefer short bullets for steps, guarantees, and safeguards.\n\n## User impact\nState what a person can now do, what stays the same, and what they will see when a limit or error occurs.\n\n## Scope, limits, and follow-up\nState deliberate exclusions, unsupported providers, preview limits, rollout dependencies, or remaining live validation. Do not bury these caveats.\n\n## Validation\nList only executed checks and their outcome.\n\n## Technical details\nOptional. Include only details that help a reviewer navigate a non-obvious implementation.\n\n## Brief\nPreserve the exact linked brief when one exists.\n```\n\nOmit empty sections. For a small bug fix, combine `How it works` and `User impact`; do not force a long template onto a two-line change.\n\n## Writing rules\n\n- Lead with behavior and consequences, not filenames, classes, APIs, or implementation verbs.\n- Translate jargon on first use: for example, say “reads every page of Jira results” before “pagination.”\n- Explain safeguards as outcomes: “does not report a final count when the read is incomplete,” not only “fails closed.”\n- Be specific about the before\u002Fafter flow when it clarifies the value.\n- Put filenames, internal tool names, commits, architecture, schemas, and test mechanics after the people-first explanation.\n- Use short paragraphs, ordinary words, active voice, and scannable bullets.\n- Do not oversell. Name material limitations plainly.\n- Never replace a technical truth with a vague product claim.\n\n## Update workflow\n\nWhen the user asks to update an existing PR:\n\n1. Preserve correct historical context and the brief.\n2. Re-check every validation claim against the current HEAD. Rerun a relevant check when the change could affect it; otherwise label the result as predating the latest commit.\n3. Replace stale implementation-first prose with the people-first structure.\n4. Keep user-impact claims proportional to what the current branch actually changes.\n5. Verify the published body after updating it.\n\n## Quality check\n\nBefore publishing, ask:\n\n- Can a non-engineer explain the problem and outcome after reading only `What changed` and `Why it matters`?\n- Can a reviewer identify the important safety behavior without reading code?\n- Are limits and pending validation explicit?\n- Are technical details present only after the human explanation?\n\nIf any answer is no, revise the description before publishing.\n","# People-first pull-request descriptions\n\nWrite PR descriptions for readers who need to understand the change before they need to inspect the code: product, support, QA, designers, leadership, and reviewers outside the subsystem.\n\n## Required companion workflow\n\nBefore opening a pull request or marking one ready for review, complete [Hamster Pre-PR Review](..\u002Fhamster-pre-pr-review\u002FSKILL.md). It makes this people-first description mandatory and verifies the branch, diff, blockers, and quality gates.\n\n## Ground the description first\n\nBefore writing or updating a PR body:\n\n1. Read the current PR body, diff, review feedback, and validation evidence.\n2. Identify the user-visible or operational problem in one plain sentence.\n3. Distinguish confirmed behavior from pending validation, limits, and follow-up work.\n4. Preserve an existing Hamster brief link\u002Fpath and any facts that remain accurate.\n\nDo not claim a test, CI run, deployment, live canary, migration, or user outcome unless it was actually observed.\n\n## Default structure\n\nUse this order unless the PR is truly trivial:\n\n```markdown\n## What changed\nOne or two plain-language sentences about the capability or behavior.\n\n## Why it matters\nDescribe the prior user, customer, operator, or maintainer problem. Use a concrete failure mode when useful.\n\n## How it works\nExplain the approach at a conceptual level. Prefer short bullets for steps, guarantees, and safeguards.\n\n## User impact\nState what a person can now do, what stays the same, and what they will see when a limit or error occurs.\n\n## Scope, limits, and follow-up\nState deliberate exclusions, unsupported providers, preview limits, rollout dependencies, or remaining live validation. Do not bury these caveats.\n\n## Validation\nList only executed checks and their outcome.\n\n## Technical details\nOptional. Include only details that help a reviewer navigate a non-obvious implementation.\n\n## Brief\nPreserve the exact linked brief when one exists.\n```\n\nOmit empty sections. For a small bug fix, combine `How it works` and `User impact`; do not force a long template onto a two-line change.\n\n## Writing rules\n\n- Lead with behavior and consequences, not filenames, classes, APIs, or implementation verbs.\n- Translate jargon on first use: for example, say “reads every page of Jira results” before “pagination.”\n- Explain safeguards as outcomes: “does not report a final count when the read is incomplete,” not only “fails closed.”\n- Be specific about the before\u002Fafter flow when it clarifies the value.\n- Put filenames, internal tool names, commits, architecture, schemas, and test mechanics after the people-first explanation.\n- Use short paragraphs, ordinary words, active voice, and scannable bullets.\n- Do not oversell. Name material limitations plainly.\n- Never replace a technical truth with a vague product claim.\n\n## Update workflow\n\nWhen the user asks to update an existing PR:\n\n1. Preserve correct historical context and the brief.\n2. Re-check every validation claim against the current HEAD. Rerun a relevant check when the change could affect it; otherwise label the result as predating the latest commit.\n3. Replace stale implementation-first prose with the people-first structure.\n4. Keep user-impact claims proportional to what the current branch actually changes.\n5. Verify the published body after updating it.\n\n## Quality check\n\nBefore publishing, ask:\n\n- Can a non-engineer explain the problem and outcome after reading only `What changed` and `Why it matters`?\n- Can a reviewer identify the important safety behavior without reading code?\n- Are limits and pending validation explicit?\n- Are technical details present only after the human explanation?\n\nIf any answer is no, revise the description before publishing.\n",{"name":5,"description":7},"main","fe3bb1476c3ec23d8a366eac0fa8cd9f0852360a","skills\u002F.experimental\u002Fpeople-first-pr-descriptions",0,"https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills","https:\u002F\u002Fgithub.com\u002Fgethamster","https:\u002F\u002Ftryhamster.com","We're building the AI-native future of work, unlocking the promised acceleration for your whole team, from idea to impact.","2026-11-05 11:33:33",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add gethamster\u002Fskills --skill people-first-pr-descriptions",{"tool":39,"command":40},"bunx","bunx skills add gethamster\u002Fskills --skill people-first-pr-descriptions",{"tool":42,"command":43},"pnpm","pnpm dlx skills add gethamster\u002Fskills --skill people-first-pr-descriptions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F.experimental\u002Fpeople-first-pr-descriptions\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7B5MWYW0KE251276S56KQDZ","writing-waterfall-requirements-documents","Write a waterfall requirements document: elicit, structure and review testable, traceable requirements, then baseline the specification before design.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-waterfall-requirements-documents\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7B5MRCXWWPKREPB1CHQ7H90","writing-vision-and-values-statements","Write a V2MOM vision a reader can test and a ranked list of values that settles real tradeoffs, so the rest of the document has a clear anchor.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-vision-and-values-statements\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7B5MKH2CH22YZAHQW3080VQ","writing-system-prompts-for-claude","Write Claude prompts and CLAUDE.md files that supply exact inputs, scope the task, and define done so the first attempt can be checked.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-system-prompts-for-claude\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7B5ME1Y3X9RNRKP5HKHKACZ","writing-page-specific-website-copy","Website copywriting by page type: write homepage, landing page, pricing page and feature page copy that fits each page's visitor and single job.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-page-specific-website-copy\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},"01M7B5M8MQNM8MN8PYH6BVWJ2B","writing-internal-press-releases","How to write an internal press release: the one-page working backwards press release that opens a PR\u002FFAQ document before anything is built.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-internal-press-releases\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},"01M7B5M3P3YH1XF37R8PWXXSBK","writing-email-sequences-that-sell","Email sequence copywriting for nurture and sales: give each email one job, write clear subject lines, and close with one specific call to action.","https:\u002F\u002Fgithub.com\u002Fgethamster\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-email-sequences-that-sell\u002FSKILL.md",[],[]]