[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71FDW81J20CZ0B9TKMDJAZY":3,"skill-same:01M71FDW81J20CZ0B9TKMDJAZY":77},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":14,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M71FDW81J20CZ0B9TKMDJAZY","inline-review",null,"Find and address inline code-review comments left in the code, marked with the `rev:` prefix (e.g. `\u002F\u002F rev:`, `# rev:`, `-- rev:`). These are a manual code review done inline instead of on GitHub — each comment is a question, suggestion, concern, or change request about the nearby code. Use this skill whenever the user asks you to address, handle, resolve, go through, or respond to their inline review comments, rev comments, or `rev:` comments — even when phrased tersely, like \"address my rev comments\", \"handle the reviews\", \"go through the rev: notes\", \"I left some inline comments\", \"respond to my review\", or just \"address these\" right after leaving such comments. Trigger whenever the request references `rev:` comments in the code.","esond\u002Fskills","esond","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4650644?v=4","01M71FCJGKDH30JSHK6XJZXN8Y","Eric Sondergard","01M71FCJHP4WCJVP4HVMEW1KB2",0,"MIT","https:\u002F\u002Fgithub.com\u002Fesond\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Feng\u002Fskills\u002Finline-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],"review","inline","inline review","notes","with","code-review","code","comments","done","you","when","use","question","rev","respond","trigger","manual","code review","just","reviews","2026-11-10 10:12:30",false,"---\nname: inline-review\ndescription: >-\n  Find and address inline code-review comments left in the code, marked with\n  the `rev:` prefix (e.g. `\u002F\u002F rev:`, `# rev:`, `-- rev:`). These are a manual\n  code review done inline instead of on GitHub — each comment is a question,\n  suggestion, concern, or change request about the nearby code. Use this skill\n  whenever the user asks you to address, handle, resolve, go through, or\n  respond to their inline review comments, rev comments, or `rev:` comments —\n  even when phrased tersely, like \"address my rev comments\", \"handle the\n  reviews\", \"go through the rev: notes\", \"I left some inline comments\",\n  \"respond to my review\", or just \"address these\" right after leaving such\n  comments. Trigger whenever the request references `rev:` comments in the\n  code.\n---\n\n# inline-review\n\nThe user has left inline review comments in the code, each prefixed with `rev:`\nafter the language's comment delimiter (`\u002F\u002F rev:`, `# rev:`, `-- rev:`,\n`\u002F* rev: ... *\u002F`, etc.). Treat them like a GitHub code review that happened\ninline: each one is a question, suggestion, concern, or change request about the\ncode near it.\n\n## Step 1 — Find every `rev:` comment\n\nSearch the codebase (or the files\u002Fpaths the user pointed at) for the `rev:` marker.\nUse a delimiter-agnostic search so no comment style is missed:\n\n```\nrg -n \"rev:\" --glob '!**\u002Fnode_modules\u002F**'\n```\n\nCollect every hit with its file, line, and full comment text. If none are found,\nsay so and stop — don't invent work.\n\n## Step 2 — Address each comment\n\nRead the surrounding code so you understand what each comment is really asking,\nthen handle it on its own terms:\n\n- **A question** → answer it. If the answer implies a code change, make it.\n- **A suggestion or change request** → make the change.\n- **A concern** → investigate; fix it if real, or explain why it's fine.\n- **Ambiguous or you disagree** → don't silently comply or silently skip. Say\n  what you'd do and why, and ask if it's a real judgment call.\n\nMake the changes surgically — only what each comment asks for, matching the\nsurrounding style. Don't address adjacent code that has no `rev:` comment.\n\n## Step 3 — Remove the comments you've addressed\n\nDelete each `rev:` comment once its point is handled, so the marker means\n\"outstanding\" and the code isn't left littered with them. Leave a `rev:` comment\nin place only if you're explicitly deferring it or waiting on the user's answer\n— and call out which ones you left and why.\n\n## Step 4 — Report back\n\nGive a short per-comment rundown: what each one asked and how you handled it\n(changed X, answered Y, deferred Z). Keep it tight — one line per comment is\nusually enough.\n\n## Things not to do\n\n- Don't run tests, commit, or open a PR unless asked — this skill just addresses\n  the comments.\n- Don't refactor or \"improve\" code that no `rev:` comment mentions.\n- Don't remove a `rev:` comment you haven't actually addressed.\n","# inline-review\n\nThe user has left inline review comments in the code, each prefixed with `rev:`\nafter the language's comment delimiter (`\u002F\u002F rev:`, `# rev:`, `-- rev:`,\n`\u002F* rev: ... *\u002F`, etc.). Treat them like a GitHub code review that happened\ninline: each one is a question, suggestion, concern, or change request about the\ncode near it.\n\n## Step 1 — Find every `rev:` comment\n\nSearch the codebase (or the files\u002Fpaths the user pointed at) for the `rev:` marker.\nUse a delimiter-agnostic search so no comment style is missed:\n\n```\nrg -n \"rev:\" --glob '!**\u002Fnode_modules\u002F**'\n```\n\nCollect every hit with its file, line, and full comment text. If none are found,\nsay so and stop — don't invent work.\n\n## Step 2 — Address each comment\n\nRead the surrounding code so you understand what each comment is really asking,\nthen handle it on its own terms:\n\n- **A question** → answer it. If the answer implies a code change, make it.\n- **A suggestion or change request** → make the change.\n- **A concern** → investigate; fix it if real, or explain why it's fine.\n- **Ambiguous or you disagree** → don't silently comply or silently skip. Say\n  what you'd do and why, and ask if it's a real judgment call.\n\nMake the changes surgically — only what each comment asks for, matching the\nsurrounding style. Don't address adjacent code that has no `rev:` comment.\n\n## Step 3 — Remove the comments you've addressed\n\nDelete each `rev:` comment once its point is handled, so the marker means\n\"outstanding\" and the code isn't left littered with them. Leave a `rev:` comment\nin place only if you're explicitly deferring it or waiting on the user's answer\n— and call out which ones you left and why.\n\n## Step 4 — Report back\n\nGive a short per-comment rundown: what each one asked and how you handled it\n(changed X, answered Y, deferred Z). Keep it tight — one line per comment is\nusually enough.\n\n## Things not to do\n\n- Don't run tests, commit, or open a PR unless asked — this skill just addresses\n  the comments.\n- Don't refactor or \"improve\" code that no `rev:` comment mentions.\n- Don't remove a `rev:` comment you haven't actually addressed.\n",{"name":5,"description":7},"main","029bf6d49f3d270442ace55a01cccb40113f7efa","plugins\u002Feng\u002Fskills\u002Finline-review","https:\u002F\u002Fgithub.com\u002Fesond\u002Fskills","https:\u002F\u002Fgithub.com\u002Fesond","https:\u002F\u002Flinktr.ee\u002Fesond0","Serial pragmatist.\r\n\r\nCheck out my other repos at @hexagram-solutions! ","2026-11-07 00:00:12",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add esond\u002Fskills --skill inline-review",{"tool":63,"command":64},"bunx","bunx skills add esond\u002Fskills --skill inline-review",{"tool":66,"command":67},"pnpm","pnpm dlx skills add esond\u002Fskills --skill inline-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fesond\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Feng\u002Fskills\u002Finline-review\u002FSKILL.md",true,[71],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"agents\u002Fopenai.yaml","REFERENCE","参考文档",112,"https:\u002F\u002Fgithub.com\u002Fesond\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Feng\u002Fskills\u002Finline-review\u002Fagents\u002Fopenai.yaml",[78,104,126,153,165,201],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":44},"01M71FF0KCP66CRNT9AT1T18Z9","work-item-voice","Write or edit the user's issues in their own voice, in any work tracker — Jira, Linear, GitHub Issues, Azure DevOps. Covers features (new behavior), tasks (work that needs doing), and bugs (behavior that does not match expectation). Load this whenever the deliverable is an issue body, whether they say \"file a bug\", \"write a ticket\", \"draft a story\", \"create an issue for this\", \"turn this into a Jira\", \"write this up in Linear\", or paste a thread and ask for an issue out of it. Load it too whenever text goes into an issue that already exists — \"record this in the issue\", \"add what we found to the ticket\", \"note this on the card\", \"update the one about refunds\", or naming an issue by its key and asking for a fact to go in it — and when writing or updating one is a step inside a larger task. Features get behavior-driven framing with no implementation prescribed, and bugs get expected versus actual. Not for a comment on an issue, which is a conversation turn.","https:\u002F\u002Fgithub.com\u002Fesond\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fesond\u002Fskills\u002Fwork-item-voice\u002FSKILL.md",[],[85,86,87,88,89,90,91,92,93,94,95,96,97,98,34,99,100,101,102,103],"work","work item voice","work item","voice","conversation","which","get","card","ticket","up","issues","new","writing","azure devops","ask","tasks","text","create","tracker",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":113,"publishedAt":44},"01M71FETV1H7JPCTSKMW3XZV1T","conversational-voice","Write the user's side of a conversation with another person, in the user's own voice: Slack messages and replies, DMs, email, PR and code-review comments, Linear or Jira comments, and any other turn in an exchange that goes out under the user's name. Load this whenever the deliverable is a message a human will read as written by the user, whether they say \"draft a Slack message\", \"reply to this\", \"how should I word this\", \"tell the team\", \"ask them about X\", \"send a note to\", or just paste a thread and ask what to say back. Load it too when tightening, shortening, or sanity-checking a message they already wrote, and when a message is one step of a larger task. The register is direct and informal, the way they'd talk to a friend or acquaintance, with the answer up front for a reader who skims. Not for something the user authors rather than sends — an issue body, a PR description, a commit message — even though a person reads those too.","https:\u002F\u002Fgithub.com\u002Fesond\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fesond\u002Fskills\u002Fconversational-voice\u002FSKILL.md",[110],{"categoryNo":111,"categoryName":112,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通",[114,88,115,89,116,117,94,118,34,99,30,119,120,29,24,121,122,123,124,125],"conversational voice","back","messages","send","slack messages","commit","team","sanity","message","slack","human","how",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":137,"publishedAt":44},"01M71FEN36NS9Y4RVX6KQ704TB","sync-core-repo-docs","Create or audit a repo's three core doc files — README.md, the agent instructions file (AGENTS.md or CLAUDE.md), and REVIEW.md — in that dependency order. If a file is missing, generate it from the codebase; if it exists, audit it against the current code and apply targeted fixes after confirmation. README.md gets a developer from clone to running the project; AGENTS.md captures coding guidance for the agent (delegating to \u002Finit or claude-md-improver); REVIEW.md holds guidance for code reviewers, human or automated, without duplicating AGENTS.md. Target files with --readme, --claude, and --review, or run all three. Use whenever the user wants to set up, bootstrap, scaffold, refresh, audit, update, or sync a repo's docs, or says things like \"create a README\", \"is my README still accurate\", \"write a CLAUDE.md\", \"write an AGENTS.md\", \"audit our docs\", or \"get this repo ready for contributors\" — even when only one file is named. Prefer it over claude-md-improver when README or REVIEW are also in scope.","https:\u002F\u002Fgithub.com\u002Fesond\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Feng\u002Fskills\u002Fsync-core-repo-docs\u002FSKILL.md",[132],{"categoryNo":133,"categoryName":134,"taxonomyType":135,"taxonomyTypeDesc":136},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[138,139,140,141,142,143,144,145,146,91,147,148,94,149,150,151,152,34,30,24],"sync","sync core repo docs","repo docs","core","repo","docs","agent instructions","SET","ready","scope","project","init","only","files","confirmation",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":44},"01M71FEKJQ2G2NQ4NCXRR9SD63","sync-core-docs","Create or audit a repo's README.md, AGENTS.md\u002FCLAUDE.md, and REVIEW.md docs.","https:\u002F\u002Fgithub.com\u002Fesond\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Feng\u002Fskills\u002Fsync-core-docs\u002FSKILL.md",[],[160,143,141,138,102,161,162,163,164,142,24],"sync core docs","true","md docs","audit","README",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":180,"publishedAt":44},"01M71FEAWPC8BM27EE0A90VT8T","righting-software-system-design","Opt-in, collaborative system-design workflow based on Juval Löwy's iDesign methodology in *Righting Software*. Conducts a multi-phase interview (framing → use cases → volatility analysis → components → call-chain validation → report) that surfaces unknown-unknowns and produces a written recommendation at `decompositions\u002F{system-name}\u002Freport.md`. **Run only when the user explicitly invites this workflow** — not for general architecture questions, lightweight design conversations, or quick \"where should X live?\" questions. Valid triggers: the user names the skill directly, references *Righting Software* \u002F Juval Löwy \u002F iDesign \u002F \"The Method\" \u002F volatility-based decomposition and asks to run a full session, asks for a \"deep\" or \"structured\" or \"Löwy-style\" system design session, or accepts a prior suggestion to run it. Wait for an explicit yes before entering Phase 0. The skill is interrogative — a back-and-forth interview that challenges each volatility candidate and proposes ones the user hasn't considered.","https:\u002F\u002Fgithub.com\u002Fesond\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Feng\u002Fskills\u002Frighting-software-system-design\u002FSKILL.md",[171,174,177],{"categoryNo":172,"categoryName":173,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":175,"categoryName":176,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":178,"categoryName":179,"taxonomyType":135,"taxonomyTypeDesc":136},"01JBSEEDCAT000000000000032","设计师",[181,182,183,184,185,186,187,188,189,190,191,192,193,194,195,196,197,198,199,200],"system design","design","software","system","righting software","righting software system design","deep","quick","wait for","unknown","components","candidate","architecture","phase","valid","run","at","wait","live","full",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":207,"publishedAt":44},"01M71FE4QYB436ZS8H3SWWHA4F","reorganize-branch-commits","Reorganize the commits on a non-default git branch into a clean, logical history by rewriting the branch — `git reset` + re-commit by default, `git rebase -i` when commit boundaries already align. Propose groupings based on the actual work done (features, refactors, tests, fixes, docs), get explicit user approval, back the branch up, then rewrite history. Use this skill whenever the user wants to tidy up, clean up, reorganize, restructure, squash, or curate commits on a feature branch — even if they phrase it as \"my branch is a mess\", \"squash this down\", \"combine these commits\", \"fix up the commit log before I open a PR\", or \"make the commits presentable for review\". Trigger proactively when the user is about to open or push a PR and the branch has scrappy\u002FWIP\u002F\"fix\" commits to collapse. Refuses to operate on default or release-shaped branches (main, master, develop, trunk, production, release, or the repo default) — a feature-branch-only tool.","https:\u002F\u002Fgithub.com\u002Fesond\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Feng\u002Fskills\u002Freorganize-branch-commits\u002FSKILL.md",[],[208,209,210,115,211,91,212,213,214,94,215,216,217,218,150,219,49,34,32,119],"branch","reorganize branch commits","commits","operate","align","re","default","fix","clean","branches","open","tidy"]