[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78F5V41CJS8TM3TQ1NPNJ5Q":3,"skill-same:01M78F5V41CJS8TM3TQ1NPNJ5Q":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":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M78F5V41CJS8TM3TQ1NPNJ5Q","comments",null,"Draft, refine, or respond to pull-request review comments. Use when a user asks to \"write a review comment\", \"address review feedback\", or \"reply to a reviewer\".","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\u002Fpackages\u002Fclaude-dev-env\u002F.agents\u002Fskills-archived\u002Fcomments\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: comments\ndescription: >-\n  Draft, refine, or respond to pull-request review comments. Use when a user\n  asks to \"write a review comment\", \"address review feedback\", or \"reply to a reviewer\".\n---\n\n# Review Comment Guide\n\n## When to Use This Guide\n\nUse this guide to draft a finding, refine its tone, reply to reviewer feedback,\nor resolve a comment thread. Use the [review guide](..\u002Freviews\u002FSKILL.md#review-judgment)\nto decide whether a concern merits a finding.\n\n## Writing Useful Review Comments\n\nEach comment names the affected behavior, the observed concern, the relevant\nevidence, and the expected outcome. Give the author enough context to choose an\neffective fix.\n\n- Use `Required` for a change that materially affects the review judgment.\n- Use `Consider`, `Nit`, or `FYI` for improvement, polish, and context.\n- Explain the technical rationale when the connection from evidence to outcome\n  needs context.\n- Recognize strong decisions and completed fixes with the same specificity.\n\n## Respectful and Actionable Feedback\n\nTreat every contributor as capable and acting in good faith. Keep feedback\nabout the code, its behavior, and its effect on users or maintainers.\n\n- Consolidate a disagreement into one focused exchange with the relevant\n  context and reasoning.\n- Use proportionate language that directs attention to the required change.\n- Respect repository tooling and established formatting conventions.\n- Close a thread when its outcome satisfies the applicable review judgment.\n\n## Responding to Feedback\n\nStart with the substance of the feedback. Clarify the code, its tests, or its\ndocumentation when that gives future readers the needed context.\n\nAsk for clarification when the requested outcome remains unclear. Reply with\nthe trade-off, evidence, and proposed resolution when an alternative approach\nbetter serves the stated goal.\n\n## Resolving Pushback\n\nReassess a disputed finding against the repository rubric and the change's\nevidence. Keep advocating for a material improvement when the rationale remains\nsound, and accept an evidence-backed alternative that meets the same quality\ngoal.\n\nEscalate to a maintainer or lead when product direction or code ownership is\nneeded. Record the resulting decision in the pull request thread.\n\n## Related Guides\n\n- Use [reviews](..\u002Freviews\u002FSKILL.md#review-workflow) for substantive code\n  assessment.\n- Use [pr-small-cl](..\u002F..\u002Fskills\u002Fpr-small-cl\u002FSKILL.md#responding-to-review) for author-side\n  review responses and focused follow-up work.\n- Use [emergencies](..\u002Femergencies\u002FSKILL.md#while-the-incident-is-active) for\n  urgent production-change communication.\n","# Review Comment Guide\n\n## When to Use This Guide\n\nUse this guide to draft a finding, refine its tone, reply to reviewer feedback,\nor resolve a comment thread. Use the [review guide](..\u002Freviews\u002FSKILL.md#review-judgment)\nto decide whether a concern merits a finding.\n\n## Writing Useful Review Comments\n\nEach comment names the affected behavior, the observed concern, the relevant\nevidence, and the expected outcome. Give the author enough context to choose an\neffective fix.\n\n- Use `Required` for a change that materially affects the review judgment.\n- Use `Consider`, `Nit`, or `FYI` for improvement, polish, and context.\n- Explain the technical rationale when the connection from evidence to outcome\n  needs context.\n- Recognize strong decisions and completed fixes with the same specificity.\n\n## Respectful and Actionable Feedback\n\nTreat every contributor as capable and acting in good faith. Keep feedback\nabout the code, its behavior, and its effect on users or maintainers.\n\n- Consolidate a disagreement into one focused exchange with the relevant\n  context and reasoning.\n- Use proportionate language that directs attention to the required change.\n- Respect repository tooling and established formatting conventions.\n- Close a thread when its outcome satisfies the applicable review judgment.\n\n## Responding to Feedback\n\nStart with the substance of the feedback. Clarify the code, its tests, or its\ndocumentation when that gives future readers the needed context.\n\nAsk for clarification when the requested outcome remains unclear. Reply with\nthe trade-off, evidence, and proposed resolution when an alternative approach\nbetter serves the stated goal.\n\n## Resolving Pushback\n\nReassess a disputed finding against the repository rubric and the change's\nevidence. Keep advocating for a material improvement when the rationale remains\nsound, and accept an evidence-backed alternative that meets the same quality\ngoal.\n\nEscalate to a maintainer or lead when product direction or code ownership is\nneeded. Record the resulting decision in the pull request thread.\n\n## Related Guides\n\n- Use [reviews](..\u002Freviews\u002FSKILL.md#review-workflow) for substantive code\n  assessment.\n- Use [pr-small-cl](..\u002F..\u002Fskills\u002Fpr-small-cl\u002FSKILL.md#responding-to-review) for author-side\n  review responses and focused follow-up work.\n- Use [emergencies](..\u002Femergencies\u002FSKILL.md#while-the-incident-is-active) for\n  urgent production-change communication.\n",{"name":5,"description":7},"main","974284b42eeb4609e94d4ebc1f6e36df400d54ca","packages\u002Fclaude-dev-env\u002F.agents\u002Fskills-archived\u002Fcomments",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":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add jl-cmd-projects\u002Fclaude-dev-env --skill comments",{"tool":36,"command":37},"bunx","bunx skills add jl-cmd-projects\u002Fclaude-dev-env --skill comments",{"tool":39,"command":40},"pnpm","pnpm dlx skills add jl-cmd-projects\u002Fclaude-dev-env --skill comments","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjl-cmd-projects\u002Fclaude-dev-env\u002Fblob\u002Fmain\u002Fpackages\u002Fclaude-dev-env\u002F.agents\u002Fskills-archived\u002Fcomments\u002FSKILL.md",true,[],[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",[],[]]