[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77XTPQ8KQB45ECM76YYBGYZ":3,"skill-same:01M77XTPQ8KQB45ECM76YYBGYZ":58},{"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":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":40,"ownerHtmlUrl":41,"ownerBlogUrl":40,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M77XTPQ8KQB45ECM76YYBGYZ","create-pr",null,"Open one pull request as a draft, with a body the reviewer can act on.","synmux\u002Fclaude-commit","synmux","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F66192?v=4","01M77XNT1GDNA1H74K0RYJ4FBM","syn","01M77XNT2BD5GEXVJ5HP24GTG8",1,"MIT","https:\u002F\u002Fgithub.com\u002Fsynmux\u002Fclaude-commit\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fcreate-pr\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: create-pr\ndescription: Open one pull request as a draft, with a body the reviewer can act on.\nmetadata:\n  credits:\n    - skill: show-me\n      author: Dex Horthy\n      organisation: Humanlayer\n      url: \"https:\u002F\u002Fgithub.com\u002Fhumanlayer\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fshow-me\u002Fskills\u002Fshow-me\u002FSKILL.md\"\n    - skill: pr\n      author: Matt Pocock\n      url: \"https:\u002F\u002Fgithub.com\u002Fmattpocock\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fpr\u002FSKILL.md\"\n---\n\n# Create PR\n\nRead `\u002Fwriting-for-humans` skill first. It carries the title, the shape, the evidence\nrules, and the de-slopping pass. This skill adds only what a pull request needs on\ntop.\n\nThe work is already written and committed. This turns it into a pull request a\nreviewer can act on. It opens as a **draft**. Marking it ready for review is the\nauthor's call, never yours.\n\n## The body carries what the diff can't\n\nThe diff is already open in the reviewer's tab. Anything they can read there is not\nyour job to restate: bullets that say \"adds X\", \"moves Y\", \"renames Z\" pad the body\nwithout giving the reviewer something new. The body is these sections, in this order:\n\n1. `## What problem this solves` — the issue that already exists, or the feature\n   that is missing. What was true before, and what forced the change: the trigger,\n   the report, the deadline, the security note.\n2. `## How this PR solves it` — the idea holding the lines together, and the\n   alternative you rejected. The reviewer reads the diff for the lines; they read\n   this for the shape, so show it: see **Show the shape**.\n3. `## What happens when this merges` — the effect downstream. Behaviour that\n   changes for users, a migration that has to run, a follow-up this unblocks. Name\n   the **door**: one-way when the merge is hard to walk back (a destructive\n   migration, a published contract, deleted data), two-way when a revert undoes it.\n   Then the **blast radius**: what breaks if the change is wrong (consumers, layout,\n   mobile, a scheduled job).\n4. `## QA steps` — how a person tries the change by hand before it merges, as a list\n   of scenarios. Each scenario is an unticked checkbox naming one behaviour, with its\n   steps numbered beneath it from a checkout of the branch: the command to run or the\n   thing to click, then the result they should see. Scenarios for the changed\n   behaviour come first, then its blast radius. CI already reports the tests, so every\n   step is something a person does by hand. A change with no visible behaviour, such\n   as a refactor, gets the scenario that shows nothing moved. Whoever tries a scenario\n   and sees it pass ticks its box.\n\n   ```markdown\n   - [ ] **Saving settings shows a toast**\n     1. `pnpm dev`, open `\u002Fsettings` → the form loads with your current values.\n     2. Change the name, click Save → a \"Saved\" toast appears.\n   ```\n\n5. `## Notes` — what a careful reader still cannot infer from the diff after\n   reading it. Invariants that hold across the change, a decision that looks\n   arbitrary but was deliberate, a gotcha that will trip the next person, a\n   constraint from outside the repo.\n\nAnything belonging to none of them gets its own section after them, named the way a\ncolleague would name it.\n\nEvery section survives on the test \"could the reviewer figure this out from the diff\nalone?\" A section that fails comes out rather than getting padded. What problem this\nsolves and QA steps stay regardless — the reason for a change and how to try it are\nnever in the diff — so a body carrying only those two is a fine pull request.\n\n## Show the shape\n\nPick the smallest visual that makes the approach clear, and place it beside the\nsentence it supports. Usually one, sometimes two:\n\n- Logic or an algorithm: pseudocode.\n- Runtime control flow: a call tree.\n- UI structure: a component tree, with the state and module boundaries that matter.\n- File responsibilities or a broad refactor: a shallow file tree, one comment per\n  folder.\n- Interaction or data flow between parts: a Mermaid diagram.\n- A change to a shape that already exists: a `diff` block of that tree or flow.\n\n```diff\n submitForm\n   createSession\n     persistPrompt\n+    expandSkillMention\n     launchAgent\n```\n\nKeep only the calls, files and boundaries the reviewer needs to see the idea. A\nvisual that copies the code diff fails the diff-alone test like any bullet.\n\n## Read the diff, don't imagine it\n\n`git diff \u003Cbase>...HEAD` and `git log \u003Cbase>..HEAD` before you write a word.\n\nEvery claim in the body traces back to a line you read. A body that describes a\nchange the diff does not contain costs the reviewer more than an empty body:\nthey have to find the lie before they can start reviewing.\n\nReading the diff also settles which sections are real. If a bullet you drafted\nturns out to sit in plain view of the diff, it fails the test and comes out.\n\n## The title becomes history\n\nYour title is the line the squashed merge commit carries, so write it for\n`git log`.\n\n## Link the ticket\n\n`Closes owner\u002Frepo#123` at the bottom of the body, so merging closes the ticket. Reference\nthe ticket by ID rather than pasting a link: some trackers put private detail in\nthe URL.\n\nNo ticket exists? Write the body anyway and leave the line off. Do not open a\nticket just to link it.\n\n## Length\n\nOne change per PR. A refactor and a fix in the same diff make the reviewer grade\ntwo things at once, and they will do both worse.\n\n## Process\n\n### 1. Check where you are\n\nYou need a branch that is not the default one, and a clean tree with your work\ncommitted. On the default branch, or holding uncommitted changes? Say so and\nstop.\n\n**Done when:** you know the base branch, the current branch, and that nothing is\nuncommitted.\n\n### 2. Read the change\n\nThe diff, the log, and the ticket it closes.\n\n**Done when:** from what you read, you can state the problem, the approach, the\ndownstream effect with its door and blast radius, the QA scenarios a reviewer will try,\nand every Note you plan to include.\n\n### 3. Draft the body\n\nTitle, then the sections in order, then any section that fits none of them,\nthen the ticket line. Drop a section that fails the diff-alone test rather than\nfilling it.\n\n### 4. Clean it up\n\nRun the draft through `\u002Fwriting-for-humans`: the title, the evidence, the secrets\ncheck, and the humanizer pass. Extra tells in a pull request:\n\n- A bullet per file that only restates the filename.\n- A second section of checks beside `## QA steps` (`How you know`, `Verification`).\n  Fold it into QA steps, or cut it if it only restated the diff.\n\n### 5. Open it\n\nPush the branch and open the pull request **as a draft**:\n\n```shell\ngh pr create --draft --base \u003Cbase> --title \"\u003Ctitle>\" --body \"\u003Cbody>\"\n```\n\nReturn the link, and say plainly that it is a draft waiting for them to mark it\nready for review.\n\nLabels go on after it exists (`gh pr edit \u003Cn> --add-label ...`), and only labels\nthe repo already has.\n\n## Where it goes\n\nGitHub through the `gh` CLI is the fallback. Before you settle for it, check\n`git remote -v`: GitLab takes `glab`, where the draft flag is `--draft` on\n`glab mr create`.\n\nA repo pull request template at `.github\u002Fpull_request_template.md` is the house\nstyle, and it wins. Fill its sections; sections that do not apply to this change\ncome out rather than getting padded. A template with no QA section still gets\n`## QA steps`, after its own sections.\n\n## Boundaries\n\nOpens the pull request. Reviewing it, merging it, and marking it ready for review\nbelong to a person.\n","# Create PR\n\nRead `\u002Fwriting-for-humans` skill first. It carries the title, the shape, the evidence\nrules, and the de-slopping pass. This skill adds only what a pull request needs on\ntop.\n\nThe work is already written and committed. This turns it into a pull request a\nreviewer can act on. It opens as a **draft**. Marking it ready for review is the\nauthor's call, never yours.\n\n## The body carries what the diff can't\n\nThe diff is already open in the reviewer's tab. Anything they can read there is not\nyour job to restate: bullets that say \"adds X\", \"moves Y\", \"renames Z\" pad the body\nwithout giving the reviewer something new. The body is these sections, in this order:\n\n1. `## What problem this solves` — the issue that already exists, or the feature\n   that is missing. What was true before, and what forced the change: the trigger,\n   the report, the deadline, the security note.\n2. `## How this PR solves it` — the idea holding the lines together, and the\n   alternative you rejected. The reviewer reads the diff for the lines; they read\n   this for the shape, so show it: see **Show the shape**.\n3. `## What happens when this merges` — the effect downstream. Behaviour that\n   changes for users, a migration that has to run, a follow-up this unblocks. Name\n   the **door**: one-way when the merge is hard to walk back (a destructive\n   migration, a published contract, deleted data), two-way when a revert undoes it.\n   Then the **blast radius**: what breaks if the change is wrong (consumers, layout,\n   mobile, a scheduled job).\n4. `## QA steps` — how a person tries the change by hand before it merges, as a list\n   of scenarios. Each scenario is an unticked checkbox naming one behaviour, with its\n   steps numbered beneath it from a checkout of the branch: the command to run or the\n   thing to click, then the result they should see. Scenarios for the changed\n   behaviour come first, then its blast radius. CI already reports the tests, so every\n   step is something a person does by hand. A change with no visible behaviour, such\n   as a refactor, gets the scenario that shows nothing moved. Whoever tries a scenario\n   and sees it pass ticks its box.\n\n   ```markdown\n   - [ ] **Saving settings shows a toast**\n     1. `pnpm dev`, open `\u002Fsettings` → the form loads with your current values.\n     2. Change the name, click Save → a \"Saved\" toast appears.\n   ```\n\n5. `## Notes` — what a careful reader still cannot infer from the diff after\n   reading it. Invariants that hold across the change, a decision that looks\n   arbitrary but was deliberate, a gotcha that will trip the next person, a\n   constraint from outside the repo.\n\nAnything belonging to none of them gets its own section after them, named the way a\ncolleague would name it.\n\nEvery section survives on the test \"could the reviewer figure this out from the diff\nalone?\" A section that fails comes out rather than getting padded. What problem this\nsolves and QA steps stay regardless — the reason for a change and how to try it are\nnever in the diff — so a body carrying only those two is a fine pull request.\n\n## Show the shape\n\nPick the smallest visual that makes the approach clear, and place it beside the\nsentence it supports. Usually one, sometimes two:\n\n- Logic or an algorithm: pseudocode.\n- Runtime control flow: a call tree.\n- UI structure: a component tree, with the state and module boundaries that matter.\n- File responsibilities or a broad refactor: a shallow file tree, one comment per\n  folder.\n- Interaction or data flow between parts: a Mermaid diagram.\n- A change to a shape that already exists: a `diff` block of that tree or flow.\n\n```diff\n submitForm\n   createSession\n     persistPrompt\n+    expandSkillMention\n     launchAgent\n```\n\nKeep only the calls, files and boundaries the reviewer needs to see the idea. A\nvisual that copies the code diff fails the diff-alone test like any bullet.\n\n## Read the diff, don't imagine it\n\n`git diff \u003Cbase>...HEAD` and `git log \u003Cbase>..HEAD` before you write a word.\n\nEvery claim in the body traces back to a line you read. A body that describes a\nchange the diff does not contain costs the reviewer more than an empty body:\nthey have to find the lie before they can start reviewing.\n\nReading the diff also settles which sections are real. If a bullet you drafted\nturns out to sit in plain view of the diff, it fails the test and comes out.\n\n## The title becomes history\n\nYour title is the line the squashed merge commit carries, so write it for\n`git log`.\n\n## Link the ticket\n\n`Closes owner\u002Frepo#123` at the bottom of the body, so merging closes the ticket. Reference\nthe ticket by ID rather than pasting a link: some trackers put private detail in\nthe URL.\n\nNo ticket exists? Write the body anyway and leave the line off. Do not open a\nticket just to link it.\n\n## Length\n\nOne change per PR. A refactor and a fix in the same diff make the reviewer grade\ntwo things at once, and they will do both worse.\n\n## Process\n\n### 1. Check where you are\n\nYou need a branch that is not the default one, and a clean tree with your work\ncommitted. On the default branch, or holding uncommitted changes? Say so and\nstop.\n\n**Done when:** you know the base branch, the current branch, and that nothing is\nuncommitted.\n\n### 2. Read the change\n\nThe diff, the log, and the ticket it closes.\n\n**Done when:** from what you read, you can state the problem, the approach, the\ndownstream effect with its door and blast radius, the QA scenarios a reviewer will try,\nand every Note you plan to include.\n\n### 3. Draft the body\n\nTitle, then the sections in order, then any section that fits none of them,\nthen the ticket line. Drop a section that fails the diff-alone test rather than\nfilling it.\n\n### 4. Clean it up\n\nRun the draft through `\u002Fwriting-for-humans`: the title, the evidence, the secrets\ncheck, and the humanizer pass. Extra tells in a pull request:\n\n- A bullet per file that only restates the filename.\n- A second section of checks beside `## QA steps` (`How you know`, `Verification`).\n  Fold it into QA steps, or cut it if it only restated the diff.\n\n### 5. Open it\n\nPush the branch and open the pull request **as a draft**:\n\n```shell\ngh pr create --draft --base \u003Cbase> --title \"\u003Ctitle>\" --body \"\u003Cbody>\"\n```\n\nReturn the link, and say plainly that it is a draft waiting for them to mark it\nready for review.\n\nLabels go on after it exists (`gh pr edit \u003Cn> --add-label ...`), and only labels\nthe repo already has.\n\n## Where it goes\n\nGitHub through the `gh` CLI is the fallback. Before you settle for it, check\n`git remote -v`: GitLab takes `glab`, where the draft flag is `--draft` on\n`glab mr create`.\n\nA repo pull request template at `.github\u002Fpull_request_template.md` is the house\nstyle, and it wins. Fill its sections; sections that do not apply to this change\ncome out rather than getting padded. A template with no QA section still gets\n`## QA steps`, after its own sections.\n\n## Boundaries\n\nOpens the pull request. Reviewing it, merging it, and marking it ready for review\nbelong to a person.\n",{"name":5,"metadata":24,"description":7},{"credits":25},[26,31],{"url":27,"skill":28,"author":29,"organisation":30},"https:\u002F\u002Fgithub.com\u002Fhumanlayer\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fshow-me\u002Fskills\u002Fshow-me\u002FSKILL.md","show-me","Dex Horthy","Humanlayer",{"url":32,"skill":33,"author":34},"https:\u002F\u002Fgithub.com\u002Fmattpocock\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fpr\u002FSKILL.md","pr","Matt Pocock","main","23304ae178bfb875579dfdaa2dc851ac66d9a5e9",".kilo\u002Fskills\u002Fcreate-pr",0,"https:\u002F\u002Fgithub.com\u002Fsynmux\u002Fclaude-commit","https:\u002F\u002Fsyn.horse","https:\u002F\u002Fgithub.com\u002Fsynmux","Want code from one of my retired repositories? See the README in daveio\u002Fboneyard for instructions.","2026-11-12 20:07:00",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add synmux\u002Fclaude-commit --skill create-pr",{"tool":50,"command":51},"bunx","bunx skills add synmux\u002Fclaude-commit --skill create-pr",{"tool":53,"command":54},"pnpm","pnpm dlx skills add synmux\u002Fclaude-commit --skill create-pr","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsynmux\u002Fclaude-commit\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fcreate-pr\u002FSKILL.md",true,[],[59,66,73,80,87,94],{"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},"01M77XWGBE1WRTHTF82HND0Z8F","writing-for-humans","How to write a short document a person has to read and act on - a ticket, a pull request body, a commit message, a handover note. Covers the title, a shape people skim, evidence that survives a refactor, and stripping the AI phrasing out. Call it before drafting any of those.","https:\u002F\u002Fgithub.com\u002Fsynmux\u002Fclaude-commit\u002Fblob\u002Fmain\u002F.skills\u002Fwriting-for-humans\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},"01M77XWEMJVMH16P0Y7Y4YJ293","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fsynmux\u002Fclaude-commit\u002Fblob\u002Fmain\u002F.skills\u002Fwriting-for-agents\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},"01M77XWAWFFNCMRH2CM36N5FBF","node-cli","Patterns and conventions for building Node.js CLI tools — src structure, entry point setup, Commander wiring, and update notifications. Use when creating or modifying a Node.js CLI, adding Commander commands, wiring update-notifier, or asking how to structure a CLI entry point or src directory.","https:\u002F\u002Fgithub.com\u002Fsynmux\u002Fclaude-commit\u002Fblob\u002Fmain\u002F.skills\u002Fnode-cli\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},"01M77XW4VB02TTKC7WF4KN1P0B","humanizer","Removes traces of AI-generated text. Suitable for editing or reviewing text to make it sound more natural and human-written. Based on the comprehensive Wikipedia guide on \"AI writing characteristics.\" Detects and fixes patterns such as: exaggerated symbolism, promotional language, superficial analysis ending in \"-ing,\" vague attribution, overuse of dashes, the rule of three, AI-typical vocabulary, negative parallelism, and excessive transitional phrases.","https:\u002F\u002Fgithub.com\u002Fsynmux\u002Fclaude-commit\u002Fblob\u002Fmain\u002F.skills\u002Fhumanizer\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},"01M77XW2AZEFV3VQ08H10Q0B8J","create-ticket","Draft one small, plain ticket as a markdown file, then file it on the project's tracker once the user approves.","https:\u002F\u002Fgithub.com\u002Fsynmux\u002Fclaude-commit\u002Fblob\u002Fmain\u002F.skills\u002Fcreate-ticket\u002FSKILL.md",[],[],{"skillNo":95,"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":96,"categories":97,"keywords":98,"publishedAt":19},"01M77XVZBJZGKMC1YZKVB5WGCQ","https:\u002F\u002Fgithub.com\u002Fsynmux\u002Fclaude-commit\u002Fblob\u002Fmain\u002F.skills\u002Fcreate-pr\u002FSKILL.md",[],[]]