[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MD09HJKHNRBDVVEE08GS8C":3,"skill-same:01M6MD09HJKHNRBDVVEE08GS8C":74},{"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":23,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6MD09HJKHNRBDVVEE08GS8C","unslop-review",null,"Rewrites code review comments so they read like a human teammate wrote them. Cuts corporate-AI throat-clearing (\"I noticed...\", \"I was wondering if perhaps...\", \"It might be worth considering...\"). Each comment is direct: location, the issue, a concrete fix. Use when user says \"humanize review\", \"de-slop PR comment\", \"make this feedback sound human\", \"review this PR\", \"code review\", \"\u002Freview\", \"\u002Funslop-review\". Auto-triggers when reviewing PRs.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FMohamedAbdallah-14\u002Funslop\u002Fskills\u002Funslop-review\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"review","unslop","unslop review","when","code review","prs","slop","make","de","triggers","human","humanize","issue","auto","use","fix","read","feedback","direct","code","pr","2026-11-10 10:12:30",false,"---\nname: unslop-review\ndescription: >\n  Rewrites code review comments so they read like a human teammate wrote them.\n  Cuts corporate-AI throat-clearing (\"I noticed...\", \"I was wondering if perhaps...\",\n  \"It might be worth considering...\"). Each comment is direct: location, the issue, a concrete fix.\n  Use when user says \"humanize review\", \"de-slop PR comment\", \"make this feedback sound human\",\n  \"review this PR\", \"code review\", \"\u002Freview\", \"\u002Funslop-review\". Auto-triggers when reviewing PRs.\n---\n\n# Unslop Review\n\n## Purpose\n\nRewrite or generate PR review comments that sound like a teammate, not a politeness engine. Direct on the issue, concrete on the fix, kind on the human.\n\n## Trigger\n\n`\u002Funslop-review`, `\u002Freview`, \"review this PR\", \"code review\", \"humanize review\", \"de-slop this comment\", \"make this feedback sound human\". Auto-trigger when reviewing pull requests.\n\n## Format\n\nDefault shape: `L\u003Cline>: \u003Cseverity prefix> \u003Cobservation>. \u003Cfix>.`\n\nSeverity prefixes (optional but use them when severity matters):\n- `bug:` — code is broken or will break\n- `risk:` — works today, fragile tomorrow (perf, race, missing test)\n- `nit:` — style, naming, dead code, \"while you're here\"\n- `q:` — genuine question, not a hidden complaint\n\nMulti-file: `\u003Cfile>:L\u003Cline>: \u003Cseverity> \u003Cobservation>. \u003Cfix>.`\n\nRange: `L88-140: ...` when the issue spans lines.\n\n## Rules\n\n### Drop\n\n- Throat-clearing: \"I noticed that...\", \"It seems like...\", \"It looks like to me...\"\n- Stacked hedging: \"I was wondering if perhaps we might want to potentially...\"\n- Polite-padding: \"I would kindly suggest...\", \"just a small suggestion...\"\n- Per-comment praise: \"Nice work on this function but...\", \"Great pattern, however...\"\n- Restating the diff: \"Here on line 42 you have a function called `getUser` which returns...\"\n- Bare opinion without a fix: \"This is bad\" with no suggestion\n\n### Keep\n\n- Exact line numbers and ranges\n- Identifiers in backticks: `findUser`, `req.body.id`\n- Concrete fix or concrete question\n- \"Why\" only when the fix isn't obvious\n\n### Tone\n\nHuman, not corporate. \"This throws if X\" not \"It may potentially be worth considering that this could throw under certain conditions.\" Calibrated uncertainty is fine (\"I think\", \"probably\") — performative softening is not.\n\n### Auto-clarity (use full prose, not one-liners)\n\n- Security findings (CVE-class, auth, secrets)\n- Architecture disagreements that need a real discussion\n- Onboarding context for a new contributor\n- When the answer is genuinely \"this is fine\"\n\nIn those cases use a short paragraph, then resume terse for the rest.\n\n## Examples\n\n### Bad → good\n\n- Bad: `I would kindly suggest that we might want to potentially consider adding a null check here as it could maybe lead to issues in some scenarios.`\n- Good: `L42: bug: \\`findUser\\` returns undefined when no match. Guard before \\`user.email\\` or early-return 404.`\n\n- Bad: `Great work on this implementation! However, I think we could potentially enhance readability by considering a refactor of this function.`\n- Good: `L88-140: nit: this function does validation, I\u002FO, and mapping. Splitting them would make the happy path easier to follow. Happy to pair on a cut if helpful.`\n\n- Bad: `I noticed that there's no retry logic here which could be problematic.`\n- Good: `L23: risk: no retry on 429. Wrap the call in \\`withBackoff(3)\\` so we don't drop legitimate requests.`\n\n- Bad: `This implementation leverages a robust caching strategy.`\n- Good: (delete — empty praise. If the caching is genuinely interesting, explain why specifically.)\n\n### Approval\n\nIf the change is solid and you have nothing concrete: `LGTM` on its own line. No boilerplate.\n\n## Boundaries\n\n- Comments only. No commits, no `git push`, no auto-approve, no linter runs.\n- Output is paste-ready: one comment per line, or a clearly separated list.\n- Severity must be honest. Don't downgrade a `bug` to a `nit` to soften the message.\n","# Unslop Review\n\n## Purpose\n\nRewrite or generate PR review comments that sound like a teammate, not a politeness engine. Direct on the issue, concrete on the fix, kind on the human.\n\n## Trigger\n\n`\u002Funslop-review`, `\u002Freview`, \"review this PR\", \"code review\", \"humanize review\", \"de-slop this comment\", \"make this feedback sound human\". Auto-trigger when reviewing pull requests.\n\n## Format\n\nDefault shape: `L\u003Cline>: \u003Cseverity prefix> \u003Cobservation>. \u003Cfix>.`\n\nSeverity prefixes (optional but use them when severity matters):\n- `bug:` — code is broken or will break\n- `risk:` — works today, fragile tomorrow (perf, race, missing test)\n- `nit:` — style, naming, dead code, \"while you're here\"\n- `q:` — genuine question, not a hidden complaint\n\nMulti-file: `\u003Cfile>:L\u003Cline>: \u003Cseverity> \u003Cobservation>. \u003Cfix>.`\n\nRange: `L88-140: ...` when the issue spans lines.\n\n## Rules\n\n### Drop\n\n- Throat-clearing: \"I noticed that...\", \"It seems like...\", \"It looks like to me...\"\n- Stacked hedging: \"I was wondering if perhaps we might want to potentially...\"\n- Polite-padding: \"I would kindly suggest...\", \"just a small suggestion...\"\n- Per-comment praise: \"Nice work on this function but...\", \"Great pattern, however...\"\n- Restating the diff: \"Here on line 42 you have a function called `getUser` which returns...\"\n- Bare opinion without a fix: \"This is bad\" with no suggestion\n\n### Keep\n\n- Exact line numbers and ranges\n- Identifiers in backticks: `findUser`, `req.body.id`\n- Concrete fix or concrete question\n- \"Why\" only when the fix isn't obvious\n\n### Tone\n\nHuman, not corporate. \"This throws if X\" not \"It may potentially be worth considering that this could throw under certain conditions.\" Calibrated uncertainty is fine (\"I think\", \"probably\") — performative softening is not.\n\n### Auto-clarity (use full prose, not one-liners)\n\n- Security findings (CVE-class, auth, secrets)\n- Architecture disagreements that need a real discussion\n- Onboarding context for a new contributor\n- When the answer is genuinely \"this is fine\"\n\nIn those cases use a short paragraph, then resume terse for the rest.\n\n## Examples\n\n### Bad → good\n\n- Bad: `I would kindly suggest that we might want to potentially consider adding a null check here as it could maybe lead to issues in some scenarios.`\n- Good: `L42: bug: \\`findUser\\` returns undefined when no match. Guard before \\`user.email\\` or early-return 404.`\n\n- Bad: `Great work on this implementation! However, I think we could potentially enhance readability by considering a refactor of this function.`\n- Good: `L88-140: nit: this function does validation, I\u002FO, and mapping. Splitting them would make the happy path easier to follow. Happy to pair on a cut if helpful.`\n\n- Bad: `I noticed that there's no retry logic here which could be problematic.`\n- Good: `L23: risk: no retry on 429. Wrap the call in \\`withBackoff(3)\\` so we don't drop legitimate requests.`\n\n- Bad: `This implementation leverages a robust caching strategy.`\n- Good: (delete — empty praise. If the caching is genuinely interesting, explain why specifically.)\n\n### Approval\n\nIf the change is solid and you have nothing concrete: `LGTM` on its own line. No boilerplate.\n\n## Boundaries\n\n- Comments only. No commits, no `git push`, no auto-approve, no linter runs.\n- Output is paste-ready: one comment per line, or a clearly separated list.\n- Severity must be honest. Don't downgrade a `bug` to a `nit` to soften the message.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FMohamedAbdallah-14\u002Funslop\u002Fskills\u002Funslop-review",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill unslop-review",{"tool":66,"command":67},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill unslop-review",{"tool":69,"command":70},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill unslop-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FMohamedAbdallah-14\u002Funslop\u002Fskills\u002Funslop-review\u002FSKILL.md",true,[],[75,85,93,101,109,117],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":84},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":84},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":84},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":84},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":84},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":84},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]