[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78FDHDT6QE3CDFWA5R4D5C2":3,"skill-same:01M78FDHDT6QE3CDFWA5R4D5C2":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":43},"01M78FDHDT6QE3CDFWA5R4D5C2","pr-title-description",null,"Review one or more pull requests and write plain titles and descriptions from the full diff.","jl-cmd-projects\u002Fclaude-dev-env","jl-cmd-projects","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F338158757?v=4","01M78F4M55P4QY5YPN27XBQA9N","01M78F4M65AGEYC88NV6PW4715",7,"MIT","https:\u002F\u002Fgithub.com\u002Fjl-cmd-projects\u002Fclaude-dev-env\u002Fblob\u002Fmain\u002Fskill-archive\u002Fpr-title-description\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: pr-title-description\ndescription: Review one or more pull requests and write plain titles and descriptions from the full diff.\ndisable-model-invocation: true\n---\n\nAccept one or more pull request links as arguments. Apply the prompt below to each link.\n\nWith no argument, use the current task, browser, worktree, or GitHub context to find the pull request or pull requests. If the context does not show a clear pull request, ask for a pull request link.\n\nReview this pull request: \u003CPR link>\n\nRead the PR and its full diff. Do not use the branch name, commit message, labels, current title, or a shallow summary.\n\n## Full-diff behavior standard\n\nBefore writing, inventory every independently observable behavior in the full diff. A behavior is independent when a user, caller, operator, automation, output, error, exit status, fallback, or side effect can observe it separately. Lead with the central behavior for readability, then give every other behavior its own short paragraph or bullet.\n\nFor each behavior, state the trigger or observer, the Before -> After result, the affected surface\u002Fcaller when shared, and focused proof. Include important preserved behavior and fallback paths when they help a coder rule a regression in or out. Describe outcomes, not line-by-line implementation, and do not hide multiple behaviors under vague umbrella wording.\n\n\nWrite like the reader is smart but knows nothing about this code. Pretend they asked you to explain it like they are five and feel stupid. If a word needs another sentence to explain it, replace the word — or turn it into a tiny story.\n\nYour job is not a dry API blurb. Your job is an illustrative before\u002Fafter a person can picture.\n\nGold voice for titles and “What this adds”:\n\nThe theme package has a phone icon somewhere. We need to find it.\n\nBefore: yell “anyone know how to find icons?” and wait for a hand.\n\nAfter: call the finder by its name tag: “icon finder, go.”\n\nThat’s all “operation id” is — the finder’s name tag.\n\nRules for that voice:\n\nStart from a concrete scene (what’s in someone’s hand, what they’re hunting for).\nPrefer Before \u002F After when the change is “how you ask” or “how you look it up.”\nUse picture words: hand it, open, find, check, save, skip, stop, call by name, name tag.\nPrefer spoken results: “found it,” “missing,” “duplicated,” “couldn’t.”\nWhen the diff uses an abstract word (operation id, registry, envelope, adapter, digest, schema), do one of two things:\nDrop it and say what the person does with their hands, or\nKeep it once, then gloss it in the same breath with a name-tag \u002F mailbox \u002F checklist metaphor — like the “finder’s name tag” line above.\nNever leave jargon unexplained. Never write as if the reader already knows the jargon.\nAdd a tiny concrete example in parentheses when a name is abstract (like “the phone icon”).\nFew words. Small words. Clear on first read.\nReturn:\n\nRecommended title\n\nFew words. Small words. Clear on first read.\nSay what you hand it, what it does, and what you get back — or the Before\u002FAfter of how you ask.\nPrefer picture words and spoken results.\nGood title: “Call the icon finder by its name tag instead of asking around”\nGood title: “Given a theme STP and an asset name, report whether that asset was found, missing, or duplicated”\nBad title: anything that only says operation id \u002F registry \u002F typed envelope \u002F adapter \u002F digest \u002F schema with no picture.\nUse “Add” only if it helps. Do not force it.\nNo vague words like “improve,” “enhance,” or “update.”\nReturn one title only.\nWhy this title fits\n\n1–2 short sentences in the same voice.\nIf needed, one Before \u002F After beat, then what you get back.\nIf this section is needed to decode the title, rewrite the title.\nEvidence\n\nKey files or functions that support the title.\nIf you cannot read the PR or full diff, say so and do not propose a title.\n\nThen write a short, paste-ready PR description.\n\nUse this structure:\n\nWhat this adds\n\nWhy\nOne short paragraph. Same plain level. Say who needs this and what goes wrong without it (the “yell and wait for a hand” problem). If this is needed to decode the feature, rewrite “What this adds.”\n\nVerification\nList only proof from the PR, CI, or your own checks.\n\nReported in the PR\n\n…\nChecked by you \u002F CI here\n\n…\nRules:\n\nFew words. Small words. Clear on first read. ELI5 I-am-stupid mark.\nDo not invent behavior, tests, or benefits.\nStrip branch names, hashes, draft notes, agent notes, and merge notes.\nNo vague words like “improve,” “enhance,” or “update.”\nIllustrative first. Abstract labels only if glossed in the same breath.\nUse the recommended title and paste-ready description to run `gh pr edit \u003CPR link> --title ... --body-file ...`, then run `gh pr view \u003CPR link> --json title,body` to confirm the saved title and body. Report the saved result.\n","Accept one or more pull request links as arguments. Apply the prompt below to each link.\n\nWith no argument, use the current task, browser, worktree, or GitHub context to find the pull request or pull requests. If the context does not show a clear pull request, ask for a pull request link.\n\nReview this pull request: \u003CPR link>\n\nRead the PR and its full diff. Do not use the branch name, commit message, labels, current title, or a shallow summary.\n\n## Full-diff behavior standard\n\nBefore writing, inventory every independently observable behavior in the full diff. A behavior is independent when a user, caller, operator, automation, output, error, exit status, fallback, or side effect can observe it separately. Lead with the central behavior for readability, then give every other behavior its own short paragraph or bullet.\n\nFor each behavior, state the trigger or observer, the Before -> After result, the affected surface\u002Fcaller when shared, and focused proof. Include important preserved behavior and fallback paths when they help a coder rule a regression in or out. Describe outcomes, not line-by-line implementation, and do not hide multiple behaviors under vague umbrella wording.\n\n\nWrite like the reader is smart but knows nothing about this code. Pretend they asked you to explain it like they are five and feel stupid. If a word needs another sentence to explain it, replace the word — or turn it into a tiny story.\n\nYour job is not a dry API blurb. Your job is an illustrative before\u002Fafter a person can picture.\n\nGold voice for titles and “What this adds”:\n\nThe theme package has a phone icon somewhere. We need to find it.\n\nBefore: yell “anyone know how to find icons?” and wait for a hand.\n\nAfter: call the finder by its name tag: “icon finder, go.”\n\nThat’s all “operation id” is — the finder’s name tag.\n\nRules for that voice:\n\nStart from a concrete scene (what’s in someone’s hand, what they’re hunting for).\nPrefer Before \u002F After when the change is “how you ask” or “how you look it up.”\nUse picture words: hand it, open, find, check, save, skip, stop, call by name, name tag.\nPrefer spoken results: “found it,” “missing,” “duplicated,” “couldn’t.”\nWhen the diff uses an abstract word (operation id, registry, envelope, adapter, digest, schema), do one of two things:\nDrop it and say what the person does with their hands, or\nKeep it once, then gloss it in the same breath with a name-tag \u002F mailbox \u002F checklist metaphor — like the “finder’s name tag” line above.\nNever leave jargon unexplained. Never write as if the reader already knows the jargon.\nAdd a tiny concrete example in parentheses when a name is abstract (like “the phone icon”).\nFew words. Small words. Clear on first read.\nReturn:\n\nRecommended title\n\nFew words. Small words. Clear on first read.\nSay what you hand it, what it does, and what you get back — or the Before\u002FAfter of how you ask.\nPrefer picture words and spoken results.\nGood title: “Call the icon finder by its name tag instead of asking around”\nGood title: “Given a theme STP and an asset name, report whether that asset was found, missing, or duplicated”\nBad title: anything that only says operation id \u002F registry \u002F typed envelope \u002F adapter \u002F digest \u002F schema with no picture.\nUse “Add” only if it helps. Do not force it.\nNo vague words like “improve,” “enhance,” or “update.”\nReturn one title only.\nWhy this title fits\n\n1–2 short sentences in the same voice.\nIf needed, one Before \u002F After beat, then what you get back.\nIf this section is needed to decode the title, rewrite the title.\nEvidence\n\nKey files or functions that support the title.\nIf you cannot read the PR or full diff, say so and do not propose a title.\n\nThen write a short, paste-ready PR description.\n\nUse this structure:\n\nWhat this adds\n\nWhy\nOne short paragraph. Same plain level. Say who needs this and what goes wrong without it (the “yell and wait for a hand” problem). If this is needed to decode the feature, rewrite “What this adds.”\n\nVerification\nList only proof from the PR, CI, or your own checks.\n\nReported in the PR\n\n…\nChecked by you \u002F CI here\n\n…\nRules:\n\nFew words. Small words. Clear on first read. ELI5 I-am-stupid mark.\nDo not invent behavior, tests, or benefits.\nStrip branch names, hashes, draft notes, agent notes, and merge notes.\nNo vague words like “improve,” “enhance,” or “update.”\nIllustrative first. Abstract labels only if glossed in the same breath.\nUse the recommended title and paste-ready description to run `gh pr edit \u003CPR link> --title ... --body-file ...`, then run `gh pr view \u003CPR link> --json title,body` to confirm the saved title and body. Report the saved result.\n",{"name":5,"description":7,"disable-model-invocation":23},true,"main","974284b42eeb4609e94d4ebc1f6e36df400d54ca","skill-archive\u002Fpr-title-description",1,"https:\u002F\u002Fgithub.com\u002Fjl-cmd-projects\u002Fclaude-dev-env","https:\u002F\u002Fgithub.com\u002Fjl-cmd-projects","2026-11-15 05:02:47",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":23},[33,36,39],{"tool":34,"command":35},"npx","npx skills add jl-cmd-projects\u002Fclaude-dev-env --skill pr-title-description",{"tool":37,"command":38},"bunx","bunx skills add jl-cmd-projects\u002Fclaude-dev-env --skill pr-title-description",{"tool":40,"command":41},"pnpm","pnpm dlx skills add jl-cmd-projects\u002Fclaude-dev-env --skill pr-title-description","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjl-cmd-projects\u002Fclaude-dev-env\u002Fblob\u002Fmain\u002Fskill-archive\u002Fpr-title-description\u002FSKILL.md",[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M78FER7S09AE87MMJFT1E87E","update","Fast-forwards a local repository's main branch to a remote's main after confirming the repo path and source remote through AskUserQuestion. Use when the user says '\u002Fupdate', 'update main', 'fast-forward main', 'sync main from origin', 'pull latest main into \u003Cpath>', or 'bring main up to date'.","https:\u002F\u002Fgithub.com\u002Fjl-cmd-projects\u002Fclaude-dev-env\u002Fblob\u002Fmain\u002Fskill-archive\u002Fupdate\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M78FENWZS01MB4PMGX6801X6","source-command-sr-loop","Converging cleanup loop: repeat \u002Fsimplify until clean, then repeat \u002Fcode-review --fix until clean","https:\u002F\u002Fgithub.com\u002Fjl-cmd-projects\u002Fclaude-dev-env\u002Fblob\u002Fmain\u002Fskill-archive\u002Fsource-command-sr-loop\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M78FEGZ7JDWEG3RM78M9Y8F8","skill-builder","Skill lifecycle: classify, scaffold, write via the skill-writer-agent, self-audit, compose sub-skills, polish description triggers, enforce deterministic scripts. Triggers: build a skill, new skill workflow, improve this skill, optimize skill description, skill development lifecycle, skill modularity, skill composition, description trigger catalog, deterministic skill scripts.","https:\u002F\u002Fgithub.com\u002Fjl-cmd-projects\u002Fclaude-dev-env\u002Fblob\u002Fmain\u002Fskill-archive\u002Fskill-builder\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M78FEDEYHJYKTER9S566DMEZ","session-tidy","Audit, clean, and consolidate session logs in the Obsidian vault. Fixes format drift, resolves orphaned next-steps, updates stale statuses, and generates project rollup summaries. Use when session logs feel cluttered or before starting a new project milestone. Triggers on '\u002Fsession-tidy', 'tidy sessions', 'clean up session logs', 'session audit'.","https:\u002F\u002Fgithub.com\u002Fjl-cmd-projects\u002Fclaude-dev-env\u002Fblob\u002Fmain\u002Fskill-archive\u002Fsession-tidy\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M78FE8QR789SKBF3A78N2T13","session-log","Logs a session report as an HTML page, tracks vault context, extracts decisions, and outputs a \u002Frename command. Use for \u002Fsession-log, 'journal this session', 'log this work', 'session report', 'summarize\u002Flog\u002Frecord this session', 'save session', 'capture session', or 'document what we did'.","https:\u002F\u002Fgithub.com\u002Fjl-cmd-projects\u002Fclaude-dev-env\u002Fblob\u002Fmain\u002Fskill-archive\u002Fsession-log\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M78FE4JDJHKTJPWRWNQEX2HT","run-claude-dev-env","Build, install, run, and test the claude-dev-env installer. Use when asked to run claude-dev-env, install the Claude Code config into ~\u002F.claude, drive the installer, smoke-test it against a sandbox, or run its test suite.","https:\u002F\u002Fgithub.com\u002Fjl-cmd-projects\u002Fclaude-dev-env\u002Fblob\u002Fmain\u002Fskill-archive\u002Frun-claude-dev-env\u002FSKILL.md",[],[]]