[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CZWQE0SDFVRZGR8CW5DZF4":3,"skill-same:01M7CZWQE0SDFVRZGR8CW5DZF4":60},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7CZWQE0SDFVRZGR8CW5DZF4","pr-writing",null,"Write or review clear commit messages, PR titles, and PR descriptions that explain what changed and why. Use before writing git history or when asked to improve it. Not for code comments, chat replies, or docs pages.","fern-works\u002Fgreenline","fern-works","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F330252531?v=4","01M7CZ6VNSYC4MB0XZS6BWJRX3","fernworks","01M7CZ6VPZYZWBPRG404SRBNA9",0,"MIT","https:\u002F\u002Fgithub.com\u002Ffern-works\u002Fgreenline\u002Fblob\u002Fmain\u002Fcorpus\u002Fupstream\u002Ftjcages\u002F170f1ca406f926f47433217f731ebf80a613719c\u002Fpr-writing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: pr-writing\nlicense: MIT\nmetadata:\n  version: \"1.0.0\"\ndescription: >-\n  Write or review clear commit messages, PR titles, and PR descriptions that\n  explain what changed and why. Use before writing git history or when asked to\n  improve it. Not for code comments, chat replies, or docs pages.\n---\n\n# PR writing\n\nFull rules: [METHODOLOGY.md](.\u002FMETHODOLOGY.md). Before\u002Fafter: [EXAMPLES.md](.\u002FEXAMPLES.md). Chat shape: [RESPONSE.md](.\u002FRESPONSE.md).\n\n**These are requirements, not preferences.** A message that breaks one gets rewritten, not shipped.\n\n## Operating order\n\n### 1. Read the diff first\n\n`git diff main...HEAD --stat` then the real hunks. You cannot state *why* from a file list.\n\n### 2. Write the subject (§1)\n\nUnder 50 characters. Capitalized. No period. Imperative mood.\n\nTest every subject: **\"If applied, this commit will ___.\"** If the sentence breaks, the subject is wrong.\n\n```\nAdd retry guard to the token refresh path\n```\n\nBanned first words: `Added`, `Adding`, `Adds`, `Fixed`, `Fixes`, `Updated`, `Changes`, `WIP`, `Misc`, `Various`. Banned anywhere in a subject: emoji, ticket IDs, `[tags]`, trailing `.`.\n\n### 3. Blank line, then body wrapped at 72 (§1)\n\nNo exceptions — `rebase`, `format-patch`, and `git log` all break without the blank line, and the default pager does not wrap.\n\n### 4. Body says what and why, never how (§2)\n\nThe diff already says how. The body says: the problem that existed, why this solution, what you rejected, what it costs.\n\n### 5. Apply the language contract (§3–4)\n\nEvery sentence, in commits and PR bodies both:\n\n| Rule | Source | Test |\n|---|---|---|\n| Active voice, present tense | Google | Who does it? Name them. |\n| ≤20 words per instruction, ≤25 per statement | STE | Count it. |\n| One instruction per sentence | STE | Two verbs → two sentences. |\n| One word, one meaning, everywhere | STE | Same thing, same noun. No synonyms. |\n| Keep articles (`the`, `a`) | STE | Telegraph style is a defect. |\n| ≤3 words per noun cluster | STE | `user account creation failure` → rewrite. |\n| Second person `you`, never `we` | Google | `we refactored` → `this change refactors`. |\n| Conditions before instructions | Google | `If X, do Y` — never `Do Y if X`. |\n| Sentence case headings, serial commas | Google | — |\n| Code font for identifiers, paths, flags | Google | — |\n| ISO dates (`2026-08-12`) | Google | Never `08\u002F12\u002F26`. |\n\nBanned words: `simply`, `just`, `easily`, `obviously`, `please`, `leverage`, `utilize`, `in order to`, `various improvements`, `under the hood`, `out of the box`, `low-hanging fruit`. Banned opener: `This PR ...` — do not pre-announce.\n\n### 6. Fill the PR body template (§5)\n\n```markdown\n## What changed\n\u003C1–3 sentences. Active voice, present tense.>\n\n## Why\n\u003CThe problem. The reason for this solution. What you rejected.>\n\n## How to verify\n1. \u003COne action per step.>\n2. \u003CExpected result, stated concretely.>\n\n## Risk\n\u003CWhat breaks if this is wrong. How to roll it back.>\n\nCloses ABC-123\n```\n\nDrop a section only when it is genuinely empty, and say so: `Risk: none — docs only.`\n\n### 7. Gate before you push\n\n```bash\nbash scripts\u002Fpr-lint.sh\n```\n\nExit non-zero → fix the message. Do not run `gh pr create` on a failing message.\n\n## Non-negotiables\n\n1. Never `git commit -m` for a change that needs a body. Use a message file or a heredoc.\n2. The PR title obeys the subject rules exactly — 50 characters, imperative, no period.\n3. A squash-merge message is a commit message. Same rules.\n4. Never let a template heading survive with placeholder text under it.\n5. If you cannot state the *why*, you do not understand the change yet. Go read the diff again.\n","# PR writing\n\nFull rules: [METHODOLOGY.md](.\u002FMETHODOLOGY.md). Before\u002Fafter: [EXAMPLES.md](.\u002FEXAMPLES.md). Chat shape: [RESPONSE.md](.\u002FRESPONSE.md).\n\n**These are requirements, not preferences.** A message that breaks one gets rewritten, not shipped.\n\n## Operating order\n\n### 1. Read the diff first\n\n`git diff main...HEAD --stat` then the real hunks. You cannot state *why* from a file list.\n\n### 2. Write the subject (§1)\n\nUnder 50 characters. Capitalized. No period. Imperative mood.\n\nTest every subject: **\"If applied, this commit will ___.\"** If the sentence breaks, the subject is wrong.\n\n```\nAdd retry guard to the token refresh path\n```\n\nBanned first words: `Added`, `Adding`, `Adds`, `Fixed`, `Fixes`, `Updated`, `Changes`, `WIP`, `Misc`, `Various`. Banned anywhere in a subject: emoji, ticket IDs, `[tags]`, trailing `.`.\n\n### 3. Blank line, then body wrapped at 72 (§1)\n\nNo exceptions — `rebase`, `format-patch`, and `git log` all break without the blank line, and the default pager does not wrap.\n\n### 4. Body says what and why, never how (§2)\n\nThe diff already says how. The body says: the problem that existed, why this solution, what you rejected, what it costs.\n\n### 5. Apply the language contract (§3–4)\n\nEvery sentence, in commits and PR bodies both:\n\n| Rule | Source | Test |\n|---|---|---|\n| Active voice, present tense | Google | Who does it? Name them. |\n| ≤20 words per instruction, ≤25 per statement | STE | Count it. |\n| One instruction per sentence | STE | Two verbs → two sentences. |\n| One word, one meaning, everywhere | STE | Same thing, same noun. No synonyms. |\n| Keep articles (`the`, `a`) | STE | Telegraph style is a defect. |\n| ≤3 words per noun cluster | STE | `user account creation failure` → rewrite. |\n| Second person `you`, never `we` | Google | `we refactored` → `this change refactors`. |\n| Conditions before instructions | Google | `If X, do Y` — never `Do Y if X`. |\n| Sentence case headings, serial commas | Google | — |\n| Code font for identifiers, paths, flags | Google | — |\n| ISO dates (`2026-08-12`) | Google | Never `08\u002F12\u002F26`. |\n\nBanned words: `simply`, `just`, `easily`, `obviously`, `please`, `leverage`, `utilize`, `in order to`, `various improvements`, `under the hood`, `out of the box`, `low-hanging fruit`. Banned opener: `This PR ...` — do not pre-announce.\n\n### 6. Fill the PR body template (§5)\n\n```markdown\n## What changed\n\u003C1–3 sentences. Active voice, present tense.>\n\n## Why\n\u003CThe problem. The reason for this solution. What you rejected.>\n\n## How to verify\n1. \u003COne action per step.>\n2. \u003CExpected result, stated concretely.>\n\n## Risk\n\u003CWhat breaks if this is wrong. How to roll it back.>\n\nCloses ABC-123\n```\n\nDrop a section only when it is genuinely empty, and say so: `Risk: none — docs only.`\n\n### 7. Gate before you push\n\n```bash\nbash scripts\u002Fpr-lint.sh\n```\n\nExit non-zero → fix the message. Do not run `gh pr create` on a failing message.\n\n## Non-negotiables\n\n1. Never `git commit -m` for a change that needs a body. Use a message file or a heredoc.\n2. The PR title obeys the subject rules exactly — 50 characters, imperative, no period.\n3. A squash-merge message is a commit message. Same rules.\n4. Never let a template heading survive with placeholder text under it.\n5. If you cannot state the *why*, you do not understand the change yet. Go read the diff again.\n",{"name":5,"license":15,"metadata":24,"description":7},{"version":25},"1.0.0","main","c4a6bc27da835d109348b8708301821838e98db2","corpus\u002Fupstream\u002Ftjcages\u002F170f1ca406f926f47433217f731ebf80a613719c\u002Fpr-writing","https:\u002F\u002Fgithub.com\u002Ffern-works\u002Fgreenline","https:\u002F\u002Fgithub.com\u002Ffern-works","2026-10-21 15:51:59",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add fern-works\u002Fgreenline --skill pr-writing",{"tool":38,"command":39},"bunx","bunx skills add fern-works\u002Fgreenline --skill pr-writing",{"tool":41,"command":42},"pnpm","pnpm dlx skills add fern-works\u002Fgreenline --skill pr-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffern-works\u002Fgreenline\u002Fblob\u002Fmain\u002Fcorpus\u002Fupstream\u002Ftjcages\u002F170f1ca406f926f47433217f731ebf80a613719c\u002Fpr-writing\u002FSKILL.md",true,[46,52,56],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"EXAMPLES.md","REFERENCE","参考文档",5813,"https:\u002F\u002Fgithub.com\u002Ffern-works\u002Fgreenline\u002Fblob\u002Fmain\u002Fcorpus\u002Fupstream\u002Ftjcages\u002F170f1ca406f926f47433217f731ebf80a613719c\u002Fpr-writing\u002FEXAMPLES.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"METHODOLOGY.md",10901,"https:\u002F\u002Fgithub.com\u002Ffern-works\u002Fgreenline\u002Fblob\u002Fmain\u002Fcorpus\u002Fupstream\u002Ftjcages\u002F170f1ca406f926f47433217f731ebf80a613719c\u002Fpr-writing\u002FMETHODOLOGY.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"RESPONSE.md",1398,"https:\u002F\u002Fgithub.com\u002Ffern-works\u002Fgreenline\u002Fblob\u002Fmain\u002Fcorpus\u002Fupstream\u002Ftjcages\u002F170f1ca406f926f47433217f731ebf80a613719c\u002Fpr-writing\u002FRESPONSE.md",[61,68,73,80,87,94],{"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},"01M7D04ARSVW93Y1EGVM7HQQR8","use-garden","Consulting garden, the separately installed guidance command this repository's owner enabled, when an open engineering choice the repository does not settle, made in a change or only recommended, would be informed by published guidance. Use for a choice between approaches, a pattern or pitfall for a technology or concern the work touches, or a unit a repository decision names; not for a question about this repository's own facts or a change whose choices are already settled.","https:\u002F\u002Fgithub.com\u002Ffern-works\u002Fgreenline\u002Fblob\u002Fmain\u002Ftest\u002Fgoldens\u002Fgarden-enabled\u002Fdot-claude\u002Fskills\u002Fuse-garden\u002FSKILL.md",[],[],{"skillNo":69,"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":70,"categories":71,"keywords":72,"publishedAt":19},"01M7D045RXH0SEYZKHHW2YD0FQ","https:\u002F\u002Fgithub.com\u002Ffern-works\u002Fgreenline\u002Fblob\u002Fmain\u002Ftest\u002Fgoldens\u002Fgarden-enabled\u002Fdot-agents\u002Fskills\u002Fuse-garden\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},"01M7D03ZXQHBP1RASSRHH5DX7S","what-to-build","Propose what this product could do next at three altitudes: sharpen a shipped slice, extend one, or open ground the product does not stand on yet. Use for 'what should we build next', 'any ideas for this app', 'what's missing', 'is this done or is there more in it', and quick-win hunts. Not for refactors, which belong to the architecture survey.","https:\u002F\u002Fgithub.com\u002Ffern-works\u002Fgreenline\u002Fblob\u002Fmain\u002Ftest\u002Fgoldens\u002Fcorpus\u002Fdot-claude\u002Fskills\u002Fwhat-to-build\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},"01M7D03WVYR3NN0N0CTN51RWBV","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets in a plan directory's map.md, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Ffern-works\u002Fgreenline\u002Fblob\u002Fmain\u002Ftest\u002Fgoldens\u002Fcorpus\u002Fdot-claude\u002Fskills\u002Fwayfinder\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},"01M7D03R6MAHHKQ42E5NBRHSF6","verify","Prove a change's claims with fresh evidence: restate each item of its acceptance so it can fail, capture a baseline and a treatment with the same command, compare the raw artifacts, and return VERIFIED, NOT VERIFIED or INCONCLUSIVE for each, at the depth the change's mode gives the verify step. Use when the mode reaches verify, or when the owner says \"verify this\", \"prove it works\" or \"did this fix it\".","https:\u002F\u002Fgithub.com\u002Ffern-works\u002Fgreenline\u002Fblob\u002Fmain\u002Ftest\u002Fgoldens\u002Fcorpus\u002Fdot-claude\u002Fskills\u002Fverify\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7D03JYGW4945FSJV6CDE2K9","tdd","Test-first development at any step: discover the repository's own test commands, name the break a test catches, watch it fail for the intended reason, make it pass with the smallest change, and add a new test only where it catches a realistic failure the existing ones would miss. Use when writing or changing a test, building a feature or fixing a bug test-first, or deciding whether a change needs a new test; also on 'red-green-refactor' and integration tests.","https:\u002F\u002Fgithub.com\u002Ffern-works\u002Fgreenline\u002Fblob\u002Fmain\u002Ftest\u002Fgoldens\u002Fcorpus\u002Fdot-claude\u002Fskills\u002Ftdd\u002FSKILL.md",[],[]]